scap-security-guide/SOURCES/scap-security-guide-0.1.61-update_RHEL_08_STIG-PR_8139.patch

13375 lines
1.8 MiB
Diff
Raw Normal View History

diff --git a/docs/manual/developer/05_tools_and_utilities.md b/docs/manual/developer/05_tools_and_utilities.md
index 6a37ca35207..b38e3b0f0a5 100644
--- a/docs/manual/developer/05_tools_and_utilities.md
+++ b/docs/manual/developer/05_tools_and_utilities.md
@@ -64,7 +64,7 @@ options:
Example
- $ ./utils/build_stig_control.py -p rhel8 -m shared/references/disa-stig-rhel8-v1r4-xccdf-manual.xml
+ $ ./utils/build_stig_control.py -p rhel8 -m shared/references/disa-stig-rhel8-v1r5-xccdf-manual.xml
## Generating login banner regular expressions
diff --git a/products/rhel8/profiles/stig.profile b/products/rhel8/profiles/stig.profile
index cb72403e81a..d5f0c07cbc5 100644
--- a/products/rhel8/profiles/stig.profile
+++ b/products/rhel8/profiles/stig.profile
@@ -1,7 +1,7 @@
documentation_complete: true
metadata:
- version: V1R4
+ version: V1R5
SMEs:
- mab879
- ggbecker
@@ -12,7 +12,7 @@ title: 'DISA STIG for Red Hat Enterprise Linux 8'
description: |-
This profile contains configuration checks that align to the
- DISA STIG for Red Hat Enterprise Linux 8 V1R4.
+ DISA STIG for Red Hat Enterprise Linux 8 V1R5.
In addition to being applicable to Red Hat Enterprise Linux 8, DISA recognizes this
configuration baseline as applicable to the operating system tier of
diff --git a/products/rhel8/profiles/stig_gui.profile b/products/rhel8/profiles/stig_gui.profile
index 1f87acf264a..d1577215b07 100644
--- a/products/rhel8/profiles/stig_gui.profile
+++ b/products/rhel8/profiles/stig_gui.profile
@@ -1,7 +1,7 @@
documentation_complete: true
metadata:
- version: V1R4
+ version: V1R5
SMEs:
- mab879
- ggbecker
@@ -12,7 +12,7 @@ title: 'DISA STIG with GUI for Red Hat Enterprise Linux 8'
description: |-
This profile contains configuration checks that align to the
- DISA STIG with GUI for Red Hat Enterprise Linux 8 V1R4.
+ DISA STIG with GUI for Red Hat Enterprise Linux 8 V1R5.
In addition to being applicable to Red Hat Enterprise Linux 8, DISA recognizes this
configuration baseline as applicable to the operating system tier of
diff --git a/shared/references/disa-stig-rhel8-v1r3-xccdf-scap.xml b/shared/references/disa-stig-rhel8-v1r4-xccdf-scap.xml
similarity index 89%
rename from shared/references/disa-stig-rhel8-v1r3-xccdf-scap.xml
rename to shared/references/disa-stig-rhel8-v1r4-xccdf-scap.xml
index 3af966c9a02..24c8f3e51a8 100644
--- a/shared/references/disa-stig-rhel8-v1r3-xccdf-scap.xml
+++ b/shared/references/disa-stig-rhel8-v1r4-xccdf-scap.xml
@@ -1,36 +1,36 @@
<?xml version="1.0" encoding="UTF-8"?>
-<data-stream-collection xmlns="http://scap.nist.gov/schema/scap/source/1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="scap_mil.disa.stig_collection_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark" schematron-version="1.2" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.2 http://scap.nist.gov/schema/xccdf/1.2/xccdf_1.2.xsd http://cpe.mitre.org/dictionary/2.0 http://scap.nist.gov/schema/cpe/2.3/cpe-dictionary_2.3.xsd http://oval.mitre.org/XMLSchema/oval-common-5 http://oval.mitre.org/language/download/schema/version5.10.1/ovaldefinition/complete/oval-common-schema.xsd http://oval.mitre.org/XMLSchema/oval-definitions-5 http://oval.mitre.org/language/download/schema/version5.10.1/ovaldefinition/complete/oval-definitions-schema.xsd http://oval.mitre.org/XMLSchema/oval-definitions-5#independent http://oval.mitre.org/language/download/schema/version5.10.1/ovaldefinition/complete/independent-definitions-schema.xsd http://oval.mitre.org/XMLSchema/oval-definitions-5#linux http://oval.mitre.org/language/download/schema/version5.10.1/ovaldefinition/complete/linux-definitions-schema.xsd http://oval.mitre.org/XMLSchema/oval-definitions-5#unix http://oval.mitre.org/language/download/schema/version5.10.1/ovaldefinition/complete/unix-definitions-schema.xsd http://scap.nist.gov/schema/scap/source/1.2 http://scap.nist.gov/schema/scap/1.2/scap-source-data-stream_1.2.xsd">
- <data-stream id="scap_mil.disa.stig_datastream_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark" use-case="CONFIGURATION" scap-version="1.2" timestamp="2021-10-04T21:38:10">
+<data-stream-collection xmlns="http://scap.nist.gov/schema/scap/source/1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="scap_mil.disa.stig_collection_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark" schematron-version="1.2" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.2 http://scap.nist.gov/schema/xccdf/1.2/xccdf_1.2.xsd http://cpe.mitre.org/dictionary/2.0 http://scap.nist.gov/schema/cpe/2.3/cpe-dictionary_2.3.xsd http://oval.mitre.org/XMLSchema/oval-common-5 http://oval.mitre.org/language/download/schema/version5.10.1/ovaldefinition/complete/oval-common-schema.xsd http://oval.mitre.org/XMLSchema/oval-definitions-5 http://oval.mitre.org/language/download/schema/version5.10.1/ovaldefinition/complete/oval-definitions-schema.xsd http://oval.mitre.org/XMLSchema/oval-definitions-5#independent http://oval.mitre.org/language/download/schema/version5.10.1/ovaldefinition/complete/independent-definitions-schema.xsd http://oval.mitre.org/XMLSchema/oval-definitions-5#linux http://oval.mitre.org/language/download/schema/version5.10.1/ovaldefinition/complete/linux-definitions-schema.xsd http://oval.mitre.org/XMLSchema/oval-definitions-5#unix http://oval.mitre.org/language/download/schema/version5.10.1/ovaldefinition/complete/unix-definitions-schema.xsd http://scap.nist.gov/schema/scap/source/1.2 http://scap.nist.gov/schema/scap/1.2/scap-source-data-stream_1.2.xsd">
+ <data-stream id="scap_mil.disa.stig_datastream_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark" use-case="CONFIGURATION" scap-version="1.2" timestamp="2022-01-03T11:44:34">
<dictionaries>
- <component-ref xmlns:xlink="http://www.w3.org/1999/xlink" id="scap_mil.disa.stig_cref_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-cpe-dictionary.xml" xlink:href="#scap_mil.disa.stig_comp_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-cpe-dictionary.xml">
+ <component-ref xmlns:xlink="http://www.w3.org/1999/xlink" id="scap_mil.disa.stig_cref_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-cpe-dictionary.xml" xlink:href="#scap_mil.disa.stig_comp_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-cpe-dictionary.xml">
<cat:catalog xmlns:cat="urn:oasis:names:tc:entity:xmlns:xml:catalog">
- <cat:uri name="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-cpe-oval.xml" uri="#scap_mil.disa.stig_cref_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-cpe-oval.xml" />
+ <cat:uri name="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-cpe-oval.xml" uri="#scap_mil.disa.stig_cref_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-cpe-oval.xml" />
</cat:catalog>
</component-ref>
</dictionaries>
<checklists>
- <component-ref xmlns:xlink="http://www.w3.org/1999/xlink" id="scap_mil.disa.stig_cref_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-xccdf.xml" xlink:href="#scap_mil.disa.stig_comp_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-xccdf.xml">
+ <component-ref xmlns:xlink="http://www.w3.org/1999/xlink" id="scap_mil.disa.stig_cref_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-xccdf.xml" xlink:href="#scap_mil.disa.stig_comp_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-xccdf.xml">
<cat:catalog xmlns:cat="urn:oasis:names:tc:entity:xmlns:xml:catalog">
- <cat:uri name="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" uri="#scap_mil.disa.stig_cref_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <cat:uri name="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" uri="#scap_mil.disa.stig_cref_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</cat:catalog>
</component-ref>
</checklists>
<checks>
- <component-ref xmlns:xlink="http://www.w3.org/1999/xlink" id="scap_mil.disa.stig_cref_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" xlink:href="#scap_mil.disa.stig_comp_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- <component-ref xmlns:xlink="http://www.w3.org/1999/xlink" id="scap_mil.disa.stig_cref_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-cpe-oval.xml" xlink:href="#scap_mil.disa.stig_comp_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-cpe-oval.xml" />
+ <component-ref xmlns:xlink="http://www.w3.org/1999/xlink" id="scap_mil.disa.stig_cref_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" xlink:href="#scap_mil.disa.stig_comp_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <component-ref xmlns:xlink="http://www.w3.org/1999/xlink" id="scap_mil.disa.stig_cref_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-cpe-oval.xml" xlink:href="#scap_mil.disa.stig_comp_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-cpe-oval.xml" />
</checks>
</data-stream>
- <component id="scap_mil.disa.stig_comp_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-cpe-dictionary.xml" timestamp="2021-10-04T21:38:10">
+ <component id="scap_mil.disa.stig_comp_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-cpe-dictionary.xml" timestamp="2022-01-03T11:44:34">
<cpe-list xmlns="http://cpe.mitre.org/dictionary/2.0">
<cpe-item name="cpe:/o:redhat:enterprise_linux:8">
<title xml:lang="en-us">Red Hat Enterprise Linux 8</title>
- <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-cpe-oval.xml">oval:mil.disa.stig.rhel8:def:1</check>
+ <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-cpe-oval.xml">oval:mil.disa.stig.rhel8:def:1</check>
</cpe-item>
</cpe-list>
</component>
- <component id="scap_mil.disa.stig_comp_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-xccdf.xml" timestamp="2021-10-04T21:38:10">
+ <component id="scap_mil.disa.stig_comp_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-xccdf.xml" timestamp="2022-01-03T11:44:34">
<xccdf:Benchmark xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2" xmlns:cpe="http://cpe.mitre.org/language/2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns:xhtml="http://www.w3.org/1999/xhtml" id="xccdf_mil.disa.stig_benchmark_RHEL_8_STIG" xml:lang="en" style="SCAP_1.2">
- <xccdf:status date="2021-08-18">accepted</xccdf:status>
+ <xccdf:status date="2021-12-03">accepted</xccdf:status>
<xccdf:title>Red Hat Enterprise Linux 8 Security Technical Implementation Guide</xccdf:title>
<xccdf:description>This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.</xccdf:description>
<xccdf:notice id="terms-of-use" xml:lang="en" />
@@ -40,11 +40,11 @@
<dc:publisher>DISA</dc:publisher>
<dc:source>STIG.DOD.MIL</dc:source>
</xccdf:reference>
- <xccdf:plain-text id="release-info">Release: 1.3 Benchmark Date: 27 Oct 2021</xccdf:plain-text>
+ <xccdf:plain-text id="release-info">Release: 1.4 Benchmark Date: 27 Jan 2022</xccdf:plain-text>
<xccdf:plain-text id="generator">3.2.2.36079</xccdf:plain-text>
<xccdf:plain-text id="conventionsVersion">1.10.0</xccdf:plain-text>
<xccdf:platform idref="cpe:/o:redhat:enterprise_linux:8" />
- <xccdf:version update="http://iase.disa.mil/stigs">001.003</xccdf:version>
+ <xccdf:version update="http://iase.disa.mil/stigs">001.004</xccdf:version>
<xccdf:metadata>
<dc:creator>DISA</dc:creator>
<dc:publisher>DISA</dc:publisher>
@@ -103,7 +103,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230294" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230295" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230296" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230297" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230298" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230300" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230301" selected="true" />
@@ -157,7 +156,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230386" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230388" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230390" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230391" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230392" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230393" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230394" selected="true" />
@@ -180,13 +178,8 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230411" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230412" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230413" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230414" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230415" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230416" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230417" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230418" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230419" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230420" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230421" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230422" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230423" selected="true" />
@@ -206,28 +199,13 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230437" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230438" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230439" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230440" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230441" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230442" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230443" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230444" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230445" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230446" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230447" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230448" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230449" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230450" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230451" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230452" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230453" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230454" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230455" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230456" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230457" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230458" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230459" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230460" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230461" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230462" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230463" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230464" selected="true" />
@@ -355,7 +333,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230294" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230295" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230296" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230297" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230298" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230300" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230301" selected="true" />
@@ -409,7 +386,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230386" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230388" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230390" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230391" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230392" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230393" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230394" selected="true" />
@@ -432,13 +408,8 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230411" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230412" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230413" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230414" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230415" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230416" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230417" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230418" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230419" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230420" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230421" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230422" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230423" selected="true" />
@@ -458,28 +429,13 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230437" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230438" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230439" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230440" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230441" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230442" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230443" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230444" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230445" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230446" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230447" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230448" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230449" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230450" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230451" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230452" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230453" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230454" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230455" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230456" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230457" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230458" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230459" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230460" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230461" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230462" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230463" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230464" selected="true" />
@@ -607,7 +563,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230294" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230295" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230296" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230297" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230298" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230300" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230301" selected="true" />
@@ -661,7 +616,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230386" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230388" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230390" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230391" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230392" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230393" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230394" selected="true" />
@@ -684,13 +638,8 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230411" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230412" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230413" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230414" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230415" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230416" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230417" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230418" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230419" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230420" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230421" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230422" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230423" selected="true" />
@@ -710,28 +659,13 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230437" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230438" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230439" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230440" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230441" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230442" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230443" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230444" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230445" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230446" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230447" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230448" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230449" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230450" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230451" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230452" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230453" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230454" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230455" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230456" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230457" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230458" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230459" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230460" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230461" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230462" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230463" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230464" selected="true" />
@@ -859,7 +793,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230294" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230295" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230296" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230297" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230298" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230300" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230301" selected="true" />
@@ -913,7 +846,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230386" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230388" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230390" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230391" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230392" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230393" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230394" selected="true" />
@@ -936,13 +868,8 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230411" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230412" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230413" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230414" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230415" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230416" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230417" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230418" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230419" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230420" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230421" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230422" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230423" selected="true" />
@@ -962,28 +889,13 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230437" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230438" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230439" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230440" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230441" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230442" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230443" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230444" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230445" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230446" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230447" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230448" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230449" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230450" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230451" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230452" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230453" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230454" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230455" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230456" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230457" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230458" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230459" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230460" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230461" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230462" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230463" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230464" selected="true" />
@@ -1111,7 +1023,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230294" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230295" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230296" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230297" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230298" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230300" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230301" selected="true" />
@@ -1165,7 +1076,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230386" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230388" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230390" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230391" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230392" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230393" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230394" selected="true" />
@@ -1188,13 +1098,8 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230411" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230412" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230413" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230414" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230415" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230416" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230417" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230418" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230419" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230420" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230421" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230422" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230423" selected="true" />
@@ -1214,28 +1119,13 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230437" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230438" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230439" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230440" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230441" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230442" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230443" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230444" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230445" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230446" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230447" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230448" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230449" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230450" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230451" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230452" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230453" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230454" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230455" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230456" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230457" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230458" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230459" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230460" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230461" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230462" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230463" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230464" selected="true" />
@@ -1363,7 +1253,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230294" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230295" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230296" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230297" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230298" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230300" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230301" selected="true" />
@@ -1417,7 +1306,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230386" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230388" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230390" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230391" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230392" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230393" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230394" selected="true" />
@@ -1440,13 +1328,8 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230411" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230412" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230413" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230414" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230415" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230416" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230417" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230418" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230419" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230420" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230421" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230422" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230423" selected="true" />
@@ -1466,28 +1349,13 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230437" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230438" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230439" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230440" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230441" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230442" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230443" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230444" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230445" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230446" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230447" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230448" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230449" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230450" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230451" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230452" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230453" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230454" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230455" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230456" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230457" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230458" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230459" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230460" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230461" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230462" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230463" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230464" selected="true" />
@@ -1615,7 +1483,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230294" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230295" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230296" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230297" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230298" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230300" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230301" selected="true" />
@@ -1669,7 +1536,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230386" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230388" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230390" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230391" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230392" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230393" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230394" selected="true" />
@@ -1692,13 +1558,8 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230411" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230412" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230413" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230414" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230415" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230416" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230417" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230418" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230419" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230420" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230421" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230422" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230423" selected="true" />
@@ -1718,28 +1579,13 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230437" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230438" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230439" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230440" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230441" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230442" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230443" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230444" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230445" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230446" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230447" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230448" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230449" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230450" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230451" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230452" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230453" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230454" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230455" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230456" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230457" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230458" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230459" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230460" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230461" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230462" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230463" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230464" selected="true" />
@@ -1867,7 +1713,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230294" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230295" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230296" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230297" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230298" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230300" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230301" selected="true" />
@@ -1921,7 +1766,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230386" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230388" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230390" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230391" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230392" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230393" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230394" selected="true" />
@@ -1944,13 +1788,8 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230411" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230412" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230413" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230414" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230415" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230416" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230417" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230418" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230419" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230420" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230421" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230422" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230423" selected="true" />
@@ -1970,28 +1809,13 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230437" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230438" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230439" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230440" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230441" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230442" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230443" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230444" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230445" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230446" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230447" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230448" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230449" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230450" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230451" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230452" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230453" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230454" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230455" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230456" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230457" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230458" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230459" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230460" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230461" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230462" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230463" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230464" selected="true" />
@@ -2119,7 +1943,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230294" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230295" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230296" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230297" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230298" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230300" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230301" selected="true" />
@@ -2173,7 +1996,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230386" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230388" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230390" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230391" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230392" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230393" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230394" selected="true" />
@@ -2196,13 +2018,8 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230411" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230412" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230413" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230414" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230415" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230416" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230417" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230418" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230419" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230420" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230421" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230422" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230423" selected="true" />
@@ -2222,28 +2039,13 @@
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230437" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230438" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230439" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230440" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230441" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230442" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230443" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230444" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230445" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230446" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230447" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230448" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230449" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230450" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230451" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230452" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230453" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230454" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230455" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230456" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230457" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230458" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230459" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230460" selected="true" />
- <xccdf:select idref="xccdf_mil.disa.stig_group_V-230461" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230462" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230463" selected="true" />
<xccdf:select idref="xccdf_mil.disa.stig_group_V-230464" selected="true" />
@@ -2324,9 +2126,9 @@
<xccdf:description>This profile only includes rules that are Severity Category I.</xccdf:description>
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230231r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230232r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230233r743919_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230233r809273_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230236r743928_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230237r743931_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230237r809276_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230238r646862_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230239r646864_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230241r627750_rule" selected="false" />
@@ -2338,7 +2140,7 @@
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230249r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230250r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230253r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230255r627750_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230255r809382_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230257r792862_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230258r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230259r792864_rule" selected="false" />
@@ -2363,7 +2165,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230294r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230295r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230296r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230297r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230298r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230300r743959_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230301r627750_rule" selected="false" />
@@ -2390,13 +2191,13 @@
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230345r743984_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230346r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230348r743987_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230349r627750_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230349r810020_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230350r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230356r627750_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230356r809379_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230357r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230358r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230359r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230360r627750_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230360r809289_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230361r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230362r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230363r627750_rule" selected="false" />
@@ -2404,7 +2205,7 @@
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230365r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230366r646878_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230367r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230368r627750_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230368r810414_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230369r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230370r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230373r627750_rule" selected="false" />
@@ -2416,7 +2217,6 @@
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230386r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230388r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230390r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230391r743998_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230392r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230393r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230394r627750_rule" selected="false" />
@@ -2438,14 +2238,9 @@
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230410r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230411r744000_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230412r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230413r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230414r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230415r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230416r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230417r627750_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230413r810463_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230418r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230419r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230420r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230421r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230422r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230423r627750_rule" selected="false" />
@@ -2463,30 +2258,15 @@
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230435r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230436r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230437r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230438r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230439r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230440r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230441r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230442r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230443r627750_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230438r810464_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230439r810465_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230444r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230445r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230446r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230447r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230448r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230449r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230450r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230451r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230452r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230453r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230454r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230455r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230456r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230457r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230458r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230459r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230460r627750_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230461r627750_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230449r810455_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230455r810459_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230456r810462_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230462r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230463r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230464r627750_rule" selected="false" />
@@ -2510,7 +2290,7 @@
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230497r792920_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230498r792922_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230499r792924_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230503r627750_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230503r809319_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230507r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230508r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230509r627750_rule" selected="false" />
@@ -2553,8 +2333,8 @@
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-230561r627750_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-237640r646890_rule" selected="false" />
<xccdf:select idref="xccdf_mil.disa.stig_rule_SV-237641r646893_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-237642r646896_rule" selected="false" />
- <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-237643r792980_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-237642r809326_rule" selected="false" />
+ <xccdf:select idref="xccdf_mil.disa.stig_rule_SV-237643r809328_rule" selected="false" />
</xccdf:Profile>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-230221">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
@@ -2576,7 +2356,7 @@ Red Hat offers the Extended Update Support (EUS) ad-on to a Red Hat Enterprise L
<xccdf:fixtext fixref="F-32865r567410_fix">Upgrade to a supported version of RHEL 8.</xccdf:fixtext>
<xccdf:fix id="F-32865r567410_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:100" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:100" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -2612,7 +2392,7 @@ $ sudo fips-mode-setup --enable
Reboot the system for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-32867r567416_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:101" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:101" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -2642,7 +2422,7 @@ Edit/Modify the following line in the "/etc/login.defs" file and set "[ENCRYPT_M
ENCRYPT_METHOD SHA512</xccdf:fixtext>
<xccdf:fix id="F-32875r567440_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:103" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:103" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -2666,16 +2446,16 @@ Passwords need to be protected at all times, and encryption is the standard meth
<xccdf:fixtext fixref="F-32876r567443_fix">Lock all interactive user accounts not using SHA-512 hashing until the passwords can be regenerated with SHA-512.</xccdf:fixtext>
<xccdf:fix id="F-32876r567443_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:104" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:104" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-230233">
<xccdf:title>SRG-OS-000073-GPOS-00041</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230233r743919_rule" weight="10.0" severity="medium">
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230233r809273_rule" weight="10.0" severity="medium">
<xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-010130</xccdf:version>
- <xccdf:title>The RHEL 8 password-auth file must be configured to use a sufficient number of hashing rounds.</xccdf:title>
+ <xccdf:title>The RHEL 8 shadow password suite must be configured to use a sufficient number of hashing rounds.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required level of entropy.
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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
@@ -2687,14 +2467,14 @@ Passwords need to be protected at all times, and encryption is the standard meth
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000196</xccdf:ident>
- <xccdf:fixtext fixref="F-32877r743918_fix">Configure RHEL 8 to encrypt all stored passwords with a strong cryptographic hash.
+ <xccdf:fixtext fixref="F-32877r809272_fix">Configure RHEL 8 to encrypt all stored passwords with a strong cryptographic hash.
-Edit/modify the following line in the "/etc/pam.d/password-auth" file and set "rounds" to a value no lower than "5000":
+Edit/modify the following line in the "/etc/login.defs" file and set "SHA_CRYPT_MIN_ROUNDS" to a value no lower than "5000":
-password sufficient pam_unix.so sha512 rounds=5000</xccdf:fixtext>
- <xccdf:fix id="F-32877r743918_fix" />
+SHA_CRYPT_MIN_ROUNDS 5000</xccdf:fixtext>
+ <xccdf:fix id="F-32877r809272_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:105" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:105" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -2722,7 +2502,7 @@ Enter password:
Confirm password:</xccdf:fixtext>
<xccdf:fix id="F-32878r743921_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:106" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:106" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -2750,7 +2530,7 @@ Enter password:
Confirm password:</xccdf:fixtext>
<xccdf:fix id="F-32879r743924_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:107" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:107" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -2774,14 +2554,14 @@ Confirm password:</xccdf:fixtext>
ExecStart=-/usr/lib/systemd/systemd-sulogin-shell rescue</xccdf:fixtext>
<xccdf:fix id="F-32880r743927_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:108" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:108" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-230237">
<xccdf:title>SRG-OS-000120-GPOS-00061</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230237r743931_rule" weight="10.0" severity="medium">
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230237r809276_rule" weight="10.0" severity="medium">
<xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-010160</xccdf:version>
<xccdf:title>The RHEL 8 pam_unix.so module must be configured in the password-auth file to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;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.
@@ -2797,14 +2577,14 @@ FIPS 140-2 is the current standard for validating that mechanisms used to access
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000803</xccdf:ident>
- <xccdf:fixtext fixref="F-32881r743930_fix">Configure RHEL 8 to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.
+ <xccdf:fixtext fixref="F-32881r809275_fix">Configure RHEL 8 to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.
Edit/modify the following line in the "/etc/pam.d/password-auth" file to include the sha512 option for pam_unix.so:
-password sufficient pam_unix.so sha512 rounds=5000</xccdf:fixtext>
- <xccdf:fix id="F-32881r743930_fix" />
+password sufficient pam_unix.so sha512</xccdf:fixtext>
+ <xccdf:fix id="F-32881r809275_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:109" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:109" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -2834,7 +2614,7 @@ FIPS 140-2 is the current standard for validating that mechanisms used to access
Remove any files with the .keytab extension from the operating system.</xccdf:fixtext>
<xccdf:fix id="F-32882r567461_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:110" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:110" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -2864,7 +2644,7 @@ FIPS 140-2 is the current standard for validating that mechanisms used to access
$ sudo yum remove krb5-workstation</xccdf:fixtext>
<xccdf:fix id="F-32883r567464_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:111" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:111" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -2890,7 +2670,7 @@ Policycoreutils contains the policy core utilities that are required for basic o
$ sudo yum install policycoreutils</xccdf:fixtext>
<xccdf:fix id="F-32885r567470_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:112" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:112" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -2926,7 +2706,7 @@ In order for the changes to take effect, the SSH daemon must be restarted.
$ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fix id="F-32888r743933_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:115" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:115" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -2952,7 +2732,7 @@ The structure and content of error messages must be carefully considered by the
$ sudo chmod 0640 /var/log/messages</xccdf:fixtext>
<xccdf:fix id="F-32889r567482_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:116" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:116" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -2978,7 +2758,7 @@ The structure and content of error messages must be carefully considered by the
$ sudo chown root /var/log/messages</xccdf:fixtext>
<xccdf:fix id="F-32890r567485_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:117" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:117" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3004,7 +2784,7 @@ The structure and content of error messages must be carefully considered by the
$ sudo chgrp root /var/log/messages</xccdf:fixtext>
<xccdf:fix id="F-32891r567488_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:118" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:118" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3030,7 +2810,7 @@ The structure and content of error messages must be carefully considered by the
$ sudo chmod 0755 /var/log</xccdf:fixtext>
<xccdf:fix id="F-32892r567491_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:119" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:119" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3056,7 +2836,7 @@ The structure and content of error messages must be carefully considered by the
$ sudo chown root /var/log</xccdf:fixtext>
<xccdf:fix id="F-32893r567494_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:120" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:120" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3082,7 +2862,7 @@ The structure and content of error messages must be carefully considered by the
$ sudo chgrp root /var/log</xccdf:fixtext>
<xccdf:fix id="F-32894r567497_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:121" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:121" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3112,14 +2892,14 @@ SSH_USE_STRONG_RNG=32
The SSH service must be restarted for changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-32897r567506_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:122" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:122" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-230255">
<xccdf:title>SRG-OS-000250-GPOS-00093</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230255r627750_rule" weight="10.0" severity="medium">
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230255r809382_rule" weight="10.0" severity="medium">
<xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-010294</xccdf:version>
<xccdf:title>The RHEL 8 operating system must implement DoD-approved TLS encryption in the OpenSSL package.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
@@ -3139,14 +2919,18 @@ Satisfies: SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-001453</xccdf:ident>
- <xccdf:fixtext fixref="F-32899r567512_fix">Configure the RHEL 8 OpenSSL library to use only DoD-approved TLS encryption by editing the following line in the "/etc/crypto-policies/back-ends/opensslcnf.config" file:
+ <xccdf:fixtext fixref="F-32899r809381_fix">Configure the RHEL 8 OpenSSL library to use only DoD-approved TLS encryption by editing the following line in the "/etc/crypto-policies/back-ends/opensslcnf.config" file:
+For versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch:
MinProtocol = TLSv1.2
+For version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer:
+TLS.MinProtocol = TLSv1.2
+DTLS.MinProtocol = DTLSv1.2
A reboot is required for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-32899r567512_fix" />
+ <xccdf:fix id="F-32899r809381_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:123" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:123" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3174,7 +2958,7 @@ Run the following command, replacing "[FILE]" with any system command with a mod
$ sudo chmod 755 [FILE]</xccdf:fixtext>
<xccdf:fix id="F-32901r792861_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:124" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:124" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3202,7 +2986,7 @@ Run the following command, replacing "[FILE]" with any system command file not o
$ sudo chown root [FILE]</xccdf:fixtext>
<xccdf:fix id="F-32902r567521_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:125" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:125" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3230,7 +3014,7 @@ Run the following command, replacing "[FILE]" with any system command file not g
$ sudo chgrp root [FILE]</xccdf:fixtext>
<xccdf:fix id="F-32903r567524_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:126" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:126" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3258,7 +3042,7 @@ Verifying the authenticity of the software prior to installation validates the i
gpgcheck=1</xccdf:fixtext>
<xccdf:fix id="F-32908r567539_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:130" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:130" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3288,7 +3072,7 @@ Set the "localpkg_gpgcheck" option to "True" in the "/etc/dnf/dnf.conf" file:
localpkg_gpgcheck=True</xccdf:fixtext>
<xccdf:fix id="F-32909r567542_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:131" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:131" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3329,7 +3113,7 @@ Load settings from all system configuration files with the following command:
$ sudo sysctl --system</xccdf:fixtext>
<xccdf:fix id="F-32910r792869_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:132" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:132" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3375,7 +3159,7 @@ Load settings from all system configuration files with the following command:
$ sudo sysctl --system</xccdf:fixtext>
<xccdf:fix id="F-32911r792872_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:133" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:133" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3421,7 +3205,7 @@ Load settings from all system configuration files with the following command:
$ sudo sysctl --system</xccdf:fixtext>
<xccdf:fix id="F-32912r792875_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:134" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:134" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3467,7 +3251,7 @@ Load settings from all system configuration files with the following command:
$ sudo sysctl --system</xccdf:fixtext>
<xccdf:fix id="F-32913r792878_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:135" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:135" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3513,7 +3297,7 @@ Load settings from all system configuration files with the following command:
$ sudo sysctl --system</xccdf:fixtext>
<xccdf:fix id="F-32914r792881_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:136" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:136" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3539,7 +3323,7 @@ Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPO
<xccdf:fixtext fixref="F-32915r567560_fix">Remove any occurrence of "NOPASSWD" found in "/etc/sudoers" file or files in the "/etc/sudoers.d" directory.</xccdf:fixtext>
<xccdf:fix id="F-32915r567560_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:137" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:137" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3565,7 +3349,7 @@ Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPO
<xccdf:fixtext fixref="F-32916r567563_fix">Remove any occurrence of "!authenticate" found in "/etc/sudoers" file or files in the "/etc/sudoers.d" directory.</xccdf:fixtext>
<xccdf:fix id="F-32916r567563_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:138" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:138" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3597,7 +3381,7 @@ This requirement only applies to components where this is specific to the functi
$ sudo yum install openssl-pkcs11</xccdf:fixtext>
<xccdf:fix id="F-32917r743942_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:139" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:139" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3623,7 +3407,7 @@ Set the "clean_requirements_on_remove" option to "True" in the "/etc/dnf/dnf.con
clean_requirements_on_remove=True</xccdf:fixtext>
<xccdf:fix id="F-32925r567590_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:145" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:145" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3653,7 +3437,7 @@ SELINUXTYPE=targeted
A reboot is required for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-32926r567593_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:146" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:146" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3677,7 +3461,7 @@ A reboot is required for the changes to take effect.</xccdf:fixtext>
$ sudo rm /etc/ssh/shosts.equiv</xccdf:fixtext>
<xccdf:fix id="F-32927r567596_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:147" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:147" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3701,7 +3485,7 @@ $ sudo rm /etc/ssh/shosts.equiv</xccdf:fixtext>
$ sudo rm /[path]/[to]/[file]/.shosts</xccdf:fixtext>
<xccdf:fix id="F-32928r567599_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:148" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:148" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3729,7 +3513,7 @@ The SSH daemon must be restarted for the changes to take effect. To restart the
$ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fix id="F-32930r567605_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:149" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:149" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3757,7 +3541,7 @@ The SSH daemon must be restarted for the changes to take effect. To restart the
$ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fix id="F-32931r743950_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:150" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:150" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3785,7 +3569,7 @@ The SSH daemon must be restarted for the changes to take effect. To restart the
$ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fix id="F-32932r567611_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:151" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:151" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3811,7 +3595,7 @@ Compression no
The SSH service must be restarted for changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-32933r743953_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:152" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:152" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3841,7 +3625,7 @@ The SSH daemon must be restarted for the changes to take effect. To restart the
$ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fix id="F-32934r567617_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:153" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:153" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3871,7 +3655,7 @@ The SSH daemon must be restarted for the changes to take effect. To restart the
$ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fix id="F-32935r743956_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:154" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:154" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3893,7 +3677,7 @@ $ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fixtext fixref="F-32936r567623_fix">Migrate the "/var" path onto a separate file system.</xccdf:fixtext>
<xccdf:fix id="F-32936r567623_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:155" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:155" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3915,7 +3699,7 @@ $ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fixtext fixref="F-32937r567626_fix">Migrate the "/var/log" path onto a separate file system.</xccdf:fixtext>
<xccdf:fix id="F-32937r567626_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:156" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:156" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3937,7 +3721,7 @@ $ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fixtext fixref="F-32938r567629_fix">Migrate the system audit data path onto a separate file system.</xccdf:fixtext>
<xccdf:fix id="F-32938r567629_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:157" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:157" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3959,7 +3743,7 @@ $ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fixtext fixref="F-32939r567632_fix">Migrate the "/tmp" directory onto a separate file system/partition.</xccdf:fixtext>
<xccdf:fix id="F-32939r567632_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:158" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:158" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -3989,35 +3773,7 @@ The SSH daemon must be restarted for the changes to take effect. To restart the
$ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fix id="F-32940r567635_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:159" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230297">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230297r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-010560</xccdf:version>
- <xccdf:title>The auditd service must be running in RHEL 8.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Configuring RHEL 8 to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across the 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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-32941r567638_fix">Start the auditd service, and enable the auditd service with the following commands:
-
-$ sudo systemctl start auditd.service
-
-$ sudo systemctl enable auditd.service</xccdf:fixtext>
- <xccdf:fix id="F-32941r567638_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:160" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:159" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4045,7 +3801,7 @@ $ sudo systemctl start rsyslog.service
$ sudo systemctl enable rsyslog.service</xccdf:fixtext>
<xccdf:fix id="F-32942r567641_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:161" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:161" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4067,7 +3823,7 @@ $ sudo systemctl enable rsyslog.service</xccdf:fixtext>
<xccdf:fixtext fixref="F-32944r567647_fix">Configure the "/etc/fstab" to use the "nosuid" option on the /boot directory.</xccdf:fixtext>
<xccdf:fix id="F-32944r567647_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:162" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:162" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4089,7 +3845,7 @@ $ sudo systemctl enable rsyslog.service</xccdf:fixtext>
<xccdf:fixtext fixref="F-32945r567650_fix">Configure the "/etc/fstab" to use the "nodev" option on all non-root local partitions.</xccdf:fixtext>
<xccdf:fix id="F-32945r567650_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:163" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:163" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4111,7 +3867,7 @@ $ sudo systemctl enable rsyslog.service</xccdf:fixtext>
<xccdf:fixtext fixref="F-32950r567665_fix">Configure the "/etc/fstab" to use the "noexec" option on file systems that are being imported via NFS.</xccdf:fixtext>
<xccdf:fix id="F-32950r567665_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:165" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:165" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4133,7 +3889,7 @@ $ sudo systemctl enable rsyslog.service</xccdf:fixtext>
<xccdf:fixtext fixref="F-32951r567668_fix">Configure the "/etc/fstab" to use the "nodev" option on file systems that are being imported via NFS.</xccdf:fixtext>
<xccdf:fix id="F-32951r567668_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:166" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:166" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4155,7 +3911,7 @@ $ sudo systemctl enable rsyslog.service</xccdf:fixtext>
<xccdf:fixtext fixref="F-32952r567671_fix">Configure the "/etc/fstab" to use the "nosuid" option on file systems that are being imported via NFS.</xccdf:fixtext>
<xccdf:fix id="F-32952r567671_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:167" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:167" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4195,7 +3951,7 @@ The system configuration files need to be reloaded for the changes to take effec
$ sudo sysctl --system</xccdf:fixtext>
<xccdf:fix id="F-32955r792893_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:168" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:168" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4223,7 +3979,7 @@ Add the following line to the top of the /etc/security/limits.conf or in a ".con
* hard core 0</xccdf:fixtext>
<xccdf:fix id="F-32957r619861_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:169" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:169" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4251,7 +4007,7 @@ Add or modify the following line in /etc/systemd/coredump.conf:
Storage=none</xccdf:fixtext>
<xccdf:fix id="F-32958r567689_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:170" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:170" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4279,7 +4035,7 @@ Add or modify the following line in /etc/systemd/coredump.conf:
ProcessSizeMax=0</xccdf:fixtext>
<xccdf:fix id="F-32959r567692_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:171" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:171" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4303,7 +4059,7 @@ ProcessSizeMax=0</xccdf:fixtext>
CREATE_HOME yes</xccdf:fixtext>
<xccdf:fix id="F-32968r567719_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:177" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:177" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4333,7 +4089,7 @@ The SSH daemon must be restarted for the changes to take effect. To restart the
$ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fix id="F-32974r567737_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:179" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:179" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4371,7 +4127,7 @@ The "sssd" service must be restarted for the changes to take effect. To restart
$ sudo systemctl restart sssd.service</xccdf:fixtext>
<xccdf:fix id="F-32976r567743_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:180" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:180" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4403,7 +4159,7 @@ Add/Modify the "/etc/security/faillock.conf" file to match the following line:
deny = 3</xccdf:fixtext>
<xccdf:fix id="F-32977r743965_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:181" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:181" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4441,7 +4197,7 @@ The "sssd" service must be restarted for the changes to take effect. To restart
$ sudo systemctl restart sssd.service</xccdf:fixtext>
<xccdf:fix id="F-32978r567749_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:182" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:182" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4473,7 +4229,7 @@ Add/Modify the "/etc/security/faillock.conf" file to match the following line:
fail_interval = 900</xccdf:fixtext>
<xccdf:fix id="F-32979r743968_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:183" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:183" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4511,7 +4267,7 @@ The "sssd" service must be restarted for the changes to take effect. To restart
$ sudo systemctl restart sssd.service</xccdf:fixtext>
<xccdf:fix id="F-32980r567755_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:184" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:184" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4543,7 +4299,7 @@ Add/Modify the "/etc/security/faillock.conf" file to match the following line:
unlock_time = 0</xccdf:fixtext>
<xccdf:fix id="F-32981r743971_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:185" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:185" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4581,7 +4337,7 @@ The "sssd" service must be restarted for the changes to take effect. To restart
$ sudo systemctl restart sssd.service</xccdf:fixtext>
<xccdf:fix id="F-32984r567767_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:186" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:186" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4613,7 +4369,7 @@ Add/Modify the "/etc/security/faillock.conf" file to match the following line:
silent</xccdf:fixtext>
<xccdf:fix id="F-32985r743977_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:187" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:187" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4653,7 +4409,7 @@ The "sssd" service must be restarted for the changes to take effect. To restart
$ sudo systemctl restart sssd.service</xccdf:fixtext>
<xccdf:fix id="F-32986r567773_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:188" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:188" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4685,7 +4441,7 @@ Add/Modify the "/etc/security/faillock.conf" file to match the following line:
audit</xccdf:fixtext>
<xccdf:fix id="F-32987r743980_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:189" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:189" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4725,7 +4481,7 @@ The "sssd" service must be restarted for the changes to take effect. To restart
$ sudo systemctl restart sssd.service</xccdf:fixtext>
<xccdf:fix id="F-32988r567779_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:190" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:190" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4757,7 +4513,7 @@ Add/Modify the "/etc/security/faillock.conf" file to match the following line:
even_deny_root</xccdf:fixtext>
<xccdf:fix id="F-32989r743983_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:191" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:191" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4785,7 +4541,7 @@ Add the following line to the top of the /etc/security/limits.conf or in a ".con
* hard maxlogins 10</xccdf:fixtext>
<xccdf:fix id="F-32990r619863_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:192" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:192" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4817,14 +4573,14 @@ Create a global configuration file "/etc/tmux.conf" and add the following line:
set -g lock-command vlock</xccdf:fixtext>
<xccdf:fix id="F-32992r743986_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:193" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:193" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-230349">
<xccdf:title>SRG-OS-000028-GPOS-00009</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230349r627750_rule" weight="10.0" severity="medium">
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230349r810020_rule" weight="10.0" severity="medium">
<xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-020041</xccdf:version>
<xccdf:title>RHEL 8 must ensure session control is automatically started at shell initialization.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;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.
@@ -4842,14 +4598,18 @@ Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011&lt;/VulnDiscussion
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000056</xccdf:ident>
- <xccdf:fixtext fixref="F-32993r567794_fix">Configure the operating system to initialize the tmux terminal multiplexer as each shell is called by adding the following line to the end of the "/etc/bashrc" configuration file:
+ <xccdf:fixtext fixref="F-32993r809283_fix">Configure the operating system to initialize the tmux terminal multiplexer as each shell is called by adding the following lines to a custom.sh shell script in the /etc/profile.d/ directory:
-[ -n "$PS1" -a -z "$TMUX" ] &amp;&amp; exec tmux
+If [ "$PS1" ]; then
+parent=$(ps -o ppid= -p $$)
+name=$(ps -o comm= -p $parent)
+case "$name" in (sshd|login) exec tmux ;; esac
+fi
This setting will take effect at next logon.</xccdf:fixtext>
- <xccdf:fix id="F-32993r567794_fix" />
+ <xccdf:fix id="F-32993r809283_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:194" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:194" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4877,23 +4637,21 @@ Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011&lt;/VulnDiscussion
<xccdf:fixtext fixref="F-32994r567797_fix">Configure the operating system to prevent users from disabling the tmux terminal multiplexer by editing the "/etc/shells" configuration file to remove any instances of tmux.</xccdf:fixtext>
<xccdf:fix id="F-32994r567797_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:195" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:195" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-230356">
<xccdf:title>SRG-OS-000069-GPOS-00037</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230356r627750_rule" weight="10.0" severity="medium">
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230356r809379_rule" weight="10.0" severity="medium">
<xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-020100</xccdf:version>
- <xccdf:title>RHEL 8 must ensure a password complexity module is enabled.</xccdf:title>
+ <xccdf:title>RHEL 8 must ensure the password complexity module is enabled in the password-auth file.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;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. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.
RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. This is set in both:
/etc/pam.d/password-auth
-/etc/pam.d/system-auth
-
-Note the value of "retry" set in these configuration files should be between "1" and "3". Manual changes to the listed files may be overwritten by the "authselect" program.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+/etc/pam.d/system-auth&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -4901,15 +4659,15 @@ Note the value of "retry" set in these configuration files should be between "1"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000192</xccdf:ident>
- <xccdf:fixtext fixref="F-33000r567815_fix">Configure the operating system to use "pwquality" to enforce password complexity rules.
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33000r809286_fix">Configure the operating system to use "pwquality" to enforce password complexity rules.
-Add the following line to both "/etc/pam.d/password-auth" and "/etc/pam.d/system-auth" (or modify the line to have the required value):
+Add the following line to the "/etc/pam.d/password-auth" file (or modify the line to have the required value):
-password required pam_pwquality.so retry=3</xccdf:fixtext>
- <xccdf:fix id="F-33000r567815_fix" />
+password required pam_pwquality.so</xccdf:fixtext>
+ <xccdf:fix id="F-33000r809286_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:196" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:196" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4939,7 +4697,7 @@ Add the following line to /etc/security/pwquality.conf (or modify the line to ha
ucredit = -1</xccdf:fixtext>
<xccdf:fix id="F-33001r567818_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:197" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:197" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4969,7 +4727,7 @@ Add the following line to /etc/security/pwquality.conf (or modify the line to ha
lcredit = -1</xccdf:fixtext>
<xccdf:fix id="F-33002r567821_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:198" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:198" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -4999,14 +4757,14 @@ Add the following line to /etc/security/pwquality.conf (or modify the line to ha
dcredit = -1</xccdf:fixtext>
<xccdf:fix id="F-33003r567824_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:199" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:199" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-230360">
<xccdf:title>SRG-OS-000072-GPOS-00040</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230360r627750_rule" weight="10.0" severity="medium">
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230360r809289_rule" weight="10.0" severity="medium">
<xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-020140</xccdf:version>
<xccdf:title>RHEL 8 must require the maximum number of repeating characters of the same character class be limited to four when passwords are changed.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;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.
@@ -5029,7 +4787,7 @@ Add the following line to "/etc/security/pwquality.conf" conf (or modify the lin
maxclassrepeat = 4</xccdf:fixtext>
<xccdf:fix id="F-33004r567827_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:200" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:200" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5059,7 +4817,7 @@ Add the following line to "/etc/security/pwquality.conf conf" (or modify the lin
maxrepeat = 3</xccdf:fixtext>
<xccdf:fix id="F-33005r567830_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:201" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:201" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5089,7 +4847,7 @@ Add the following line to "/etc/security/pwquality.conf conf" (or modify the lin
minclass = 4</xccdf:fixtext>
<xccdf:fix id="F-33006r567833_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:202" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:202" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5119,7 +4877,7 @@ Add the following line to "/etc/security/pwquality.conf" (or modify the line to
difok = 8</xccdf:fixtext>
<xccdf:fix id="F-33007r567836_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:203" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:203" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5143,7 +4901,7 @@ difok = 8</xccdf:fixtext>
$ sudo chage -m 1 [user]</xccdf:fixtext>
<xccdf:fix id="F-33008r567839_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:204" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:204" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5169,7 +4927,7 @@ Add the following line in "/etc/login.defs" (or modify the line to have the requ
PASS_MIN_DAYS 1</xccdf:fixtext>
<xccdf:fix id="F-33009r567842_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:205" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:205" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5195,7 +4953,7 @@ Add, or modify the following line in the "/etc/login.defs" file:
PASS_MAX_DAYS 60</xccdf:fixtext>
<xccdf:fix id="F-33010r567845_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:206" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:206" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5219,19 +4977,19 @@ PASS_MAX_DAYS 60</xccdf:fixtext>
$ sudo chage -M 60 [user]</xccdf:fixtext>
<xccdf:fix id="F-33011r567848_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:207" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:207" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-230368">
<xccdf:title>SRG-OS-000077-GPOS-00045</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230368r627750_rule" weight="10.0" severity="medium">
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230368r810414_rule" weight="10.0" severity="medium">
<xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-020220</xccdf:version>
- <xccdf:title>RHEL 8 passwords must be prohibited from reuse for a minimum of five generations.</xccdf:title>
+ <xccdf:title>RHEL 8 must be configured in the password-auth file to prohibit password reuse for a minimum of five generations.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;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 reuse their password consecutively when that password has exceeded its defined lifetime, the end result is a password that is not changed per policy requirements.
-RHEL 8 utilizes "pwquality" consecutively as a mechanism to enforce password complexity. This is set in both:
+RHEL 8 uses "pwhistory" consecutively as a mechanism to prohibit password reuse. This is set in both:
/etc/pam.d/password-auth
/etc/pam.d/system-auth.
@@ -5244,14 +5002,14 @@ Note that manual changes to the listed files may be overwritten by the "authsele
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000200</xccdf:ident>
- <xccdf:fixtext fixref="F-33012r567851_fix">Configure the operating system to prohibit password reuse for a minimum of five generations.
+ <xccdf:fixtext fixref="F-33012r809291_fix">Configure the operating system in the password-auth file to prohibit password reuse for a minimum of five generations.
-Add the following line in "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" (or modify the line to have the required value):
+Add the following line in "/etc/pam.d/password-auth" (or modify the line to have the required value):
password required pam_pwhistory.so use_authtok remember=5 retry=3</xccdf:fixtext>
- <xccdf:fix id="F-33012r567851_fix" />
+ <xccdf:fix id="F-33012r809291_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:208" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:208" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5285,7 +5043,7 @@ Add the following line to "/etc/security/pwquality.conf" (or modify the line to
minlen = 15</xccdf:fixtext>
<xccdf:fix id="F-33013r567854_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:209" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:209" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5315,7 +5073,7 @@ Add, or modify the following line in the "/etc/login.defs" file:
PASS_MIN_LEN 15</xccdf:fixtext>
<xccdf:fix id="F-33014r567857_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:210" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:210" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5345,7 +5103,7 @@ $ sudo useradd -D -f 35
DoD recommendation is 35 days, but a lower value is acceptable. The value "-1" will disable this feature, and "0" will disable the account immediately after the password expires.</xccdf:fixtext>
<xccdf:fix id="F-33017r567866_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:211" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:211" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5375,7 +5133,7 @@ Add the following line to /etc/security/pwquality.conf (or modify the line to ha
ocredit = -1</xccdf:fixtext>
<xccdf:fix id="F-33019r567872_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:212" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:212" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5401,7 +5159,7 @@ Add or update the following line in the "/etc/security/pwquality.conf" file or a
dictcheck=1</xccdf:fixtext>
<xccdf:fix id="F-33021r567878_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:214" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:214" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5429,7 +5187,7 @@ Modify the "/etc/login.defs" file to set the "FAIL_DELAY" parameter to "4" or gr
FAIL_DELAY 4</xccdf:fixtext>
<xccdf:fix id="F-33022r567881_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:215" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:215" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5457,7 +5215,7 @@ The SSH daemon must be restarted for the changes to take effect. To restart the
$ sudo systemctl restart sshd.service</xccdf:fixtext>
<xccdf:fix id="F-33024r743992_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:216" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:216" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5485,7 +5243,7 @@ PrintLastLog yes
The SSH service must be restarted for changes to "sshd_config" to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33026r567893_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:218" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:218" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5511,7 +5269,7 @@ Add or edit the line for the "UMASK" parameter in "/etc/login.defs" file to "077
UMASK 077</xccdf:fixtext>
<xccdf:fix id="F-33027r567896_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:219" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:219" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5545,7 +5303,7 @@ Add or update the following file system rules to "/etc/audit/rules.d/audit.rules
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33030r567905_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:220" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:220" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5575,7 +5333,7 @@ Edit the following line in "/etc/audit/auditd.conf" to ensure that administrator
action_mail_acct = root</xccdf:fixtext>
<xccdf:fix id="F-33032r567911_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:222" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:222" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5607,37 +5365,7 @@ disk_error_action = HALT
If availability has been determined to be more important, and this decision is documented with the ISSO, configure the operating system to notify system administration staff and ISSO staff in the event of an audit processing failure by setting the "disk_error_action" to "SYSLOG".</xccdf:fixtext>
<xccdf:fix id="F-33034r567917_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:223" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230391">
- <xccdf:title>SRG-OS-000047-GPOS-00023</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230391r743998_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030050</xccdf:version>
- <xccdf:title>The RHEL 8 System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) must be alerted when the audit storage volume is full.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;It is critical that when RHEL 8 is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.
-
-When availability is an overriding concern, other approved actions in response to an audit failure are as follows:
-
-1) If the failure was caused by the lack of audit record storage capacity, RHEL 8 must continue generating audit records if possible (automatically restarting the audit service if necessary) and overwriting the oldest audit records in a first-in-first-out manner.
-
-2) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, RHEL 8 must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000140</xccdf:ident>
- <xccdf:fixtext fixref="F-33035r743997_fix">Configure RHEL 8 to notify the System Administrator (SA) and Information System Security Officer (ISSO) when the audit storage volume is full by configuring the "max_log_file_action" parameter in the "/etc/audit/auditd.conf" file with the a value of "syslog" or "keep_logs":
-
-max_log_file_action = syslog</xccdf:fixtext>
- <xccdf:fix id="F-33035r743997_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:224" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:223" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5671,7 +5399,7 @@ disk_full_action = HALT
If availability has been determined to be more important, and this decision is documented with the ISSO, configure the operating system to notify system administration staff and ISSO staff in the event of an audit processing failure by setting the "disk_full_action" to "SYSLOG".</xccdf:fixtext>
<xccdf:fix id="F-33036r567923_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:225" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:225" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5699,7 +5427,7 @@ Add or update the following line in "/etc/audit/auditd.conf" file:
local_events = yes</xccdf:fixtext>
<xccdf:fix id="F-33037r567926_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:226" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:226" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5731,7 +5459,7 @@ name_format = hostname
The audit daemon must be restarted for changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33038r567929_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:227" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:227" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5761,7 +5489,7 @@ log_format = ENRICHED
The audit daemon must be restarted for changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33039r567932_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:228" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:228" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5789,7 +5517,7 @@ Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPO
log_group = root</xccdf:fixtext>
<xccdf:fix id="F-33040r567935_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:229" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:229" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5819,7 +5547,7 @@ $ sudo chown root [audit_log_file]
Replace "[audit_log_file]" to the correct audit log path, by default this location is "/var/log/audit/audit.log".</xccdf:fixtext>
<xccdf:fix id="F-33041r567938_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:230" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:230" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5847,7 +5575,7 @@ Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPO
log_group = root</xccdf:fixtext>
<xccdf:fix id="F-33042r567941_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:231" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:231" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5877,7 +5605,7 @@ $ sudo chown root [audit_log_directory]
Replace "[audit_log_directory]" with the correct audit log directory path, by default this location is usually "/var/log/audit".</xccdf:fixtext>
<xccdf:fix id="F-33043r567944_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:232" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:232" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5907,7 +5635,7 @@ $ sudo chgrp root [audit_log_directory]
Replace "[audit_log_directory]" with the correct audit log directory path, by default this location is usually "/var/log/audit".</xccdf:fixtext>
<xccdf:fix id="F-33044r567947_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:233" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:233" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5937,7 +5665,7 @@ $ sudo chmod 0700 [audit_log_directory]
Replace "[audit_log_directory]" to the correct audit log directory path, by default this location is "/var/log/audit".</xccdf:fixtext>
<xccdf:fix id="F-33045r567950_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:234" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:234" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5969,7 +5697,7 @@ Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPO
Note: Once set, the system must be rebooted for auditing to be changed. It is recommended to add this option as the last step in securing the system.</xccdf:fixtext>
<xccdf:fix id="F-33046r567953_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:235" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:235" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -5999,7 +5727,7 @@ Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPO
--loginuid-immutable</xccdf:fixtext>
<xccdf:fix id="F-33047r567956_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:236" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:236" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6031,7 +5759,7 @@ Add or update the following file system rule to "/etc/audit/rules.d/audit.rules"
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33048r567959_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:237" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:237" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6063,7 +5791,7 @@ Add or update the following file system rule to "/etc/audit/rules.d/audit.rules"
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33049r567962_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:238" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:238" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6095,7 +5823,7 @@ Add or update the following file system rule to "/etc/audit/rules.d/audit.rules"
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33050r567965_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:239" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:239" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6127,7 +5855,7 @@ Add or update the following file system rule to "/etc/audit/rules.d/audit.rules"
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33051r567968_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:240" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:240" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6159,7 +5887,7 @@ Add or update the following file system rule to "/etc/audit/rules.d/audit.rules"
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33052r567971_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:241" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:241" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6191,7 +5919,7 @@ Add or update the following file system rule to "/etc/audit/rules.d/audit.rules"
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33053r567974_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:242" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:242" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6223,7 +5951,7 @@ Add or update the following file system rule to "/etc/audit/rules.d/audit.rules"
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33054r567977_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:243" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:243" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6255,7 +5983,7 @@ Install the audit service (if the audit service is not already installed) with t
$ sudo yum install audit</xccdf:fixtext>
<xccdf:fix id="F-33055r646880_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:244" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:244" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6287,167 +6015,32 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33056r567983_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:245" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:245" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-230413">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230413r627750_rule" weight="10.0" severity="medium">
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230413r810463_rule" weight="10.0" severity="medium">
<xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030200</xccdf:version>
- <xccdf:title>The RHEL 8 audit system must be configured to audit any usage of the lremovexattr system call.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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). "Lremovexattr" is a system call that removes extended attributes. This is used for removal of extended attributes from symbolic links.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33057r567986_fix">Configure RHEL 8 to audit the execution of the "lremovexattr" system call, by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S lremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33057r567986_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:246" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230414">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230414r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030210</xccdf:version>
- <xccdf:title>The RHEL 8 audit system must be configured to audit any usage of the removexattr system call.</xccdf:title>
+ <xccdf:title>The RHEL 8 audit system must be configured to audit any usage of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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). "Removexattr" is a system call that removes extended attributes.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33058r567989_fix">Configure RHEL 8 to audit the execution of the "removexattr" system call, by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S removexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S removexattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33058r567989_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:247" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230415">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230415r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030220</xccdf:version>
- <xccdf:title>The RHEL 8 audit system must be configured to audit any usage of the lsetxattr system call.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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).
-Audit records can be generated from various components within the information system (e.g., module or policy filter). "Lsetxattr" is a system call used to set an extended attribute value. This is used to set extended attributes on a symbolic link.
+"Setxattr" is a system call used to set an extended attribute value.
+"Fsetxattr" is a system call used to set an extended attribute value. This is used to set extended attributes on a file.
+"Lsetxattr" is a system call used to set an extended attribute value. This is used to set extended attributes on a symbolic link.
+"Removexattr" is a system call that removes extended attributes.
+"Fremovexattr" is a system call that removes extended attributes. This is used for removal of extended attributes from a file.
+"Lremovexattr" is a system call that removes extended attributes. This is used for removal of extended attributes from symbolic links.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33059r567992_fix">Configure RHEL 8 to audit the execution of the "lsetxattr" system call, by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S lsetxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33059r567992_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:248" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230416">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230416r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030230</xccdf:version>
- <xccdf:title>The RHEL 8 audit system must be configured to audit any usage of the fsetxattr system call.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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). "Fsetxattr" is a system call used to set an extended attribute value. This is used to set extended attributes on a file.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The auid representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33060r567995_fix">Configure RHEL 8 to audit the execution of the "fsetxattr" system call, by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S fsetxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33060r567995_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:249" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230417">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230417r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030240</xccdf:version>
- <xccdf:title>The RHEL 8 audit system must be configured to audit any usage of the fremovexattr system call.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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). "Fremovexattr" is a system call that removes extended attributes. This is used for removal of extended attributes from a file.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -6456,18 +6049,18 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33061r567998_fix">Configure RHEL 8 to audit the execution of the "fremovexattr" system call by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
+ <xccdf:fixtext fixref="F-33057r809294_fix">Configure RHEL 8 to audit the execution of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
--a always,exit -F arch=b32 -S fremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -k perm_mod
+-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod
+-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33061r567998_fix" />
+ <xccdf:fix id="F-33057r809294_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:250" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:246" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6499,7 +6092,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33062r568001_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:251" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:251" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6531,43 +6124,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33063r568004_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:252" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230420">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230420r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030270</xccdf:version>
- <xccdf:title>The RHEL 8 audit system must be configured to audit any usage of the setxattr system call.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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). "Setxattr" is a system call used to set an extended attribute value.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33064r568007_fix">Configure RHEL 8 to audit the execution of the "setxattr" system call, by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S setxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S setxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S setxattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S setxattr -F auid=0 -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33064r568007_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:253" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:252" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6599,7 +6156,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33065r568010_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:254" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:254" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6631,7 +6188,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33066r568013_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:255" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:255" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6663,7 +6220,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33067r568016_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:256" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:256" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6695,7 +6252,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33068r568019_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:257" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:257" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6728,7 +6285,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33069r568022_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:258" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:258" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6760,7 +6317,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33070r568025_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:259" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:259" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6792,7 +6349,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33071r568028_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:260" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:260" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6824,7 +6381,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33072r568031_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:261" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:261" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6856,7 +6413,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33073r568034_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:262" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:262" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6888,7 +6445,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33074r568037_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:263" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:263" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6920,7 +6477,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33075r568040_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:264" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:264" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6952,7 +6509,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33076r568043_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:265" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:265" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -6984,7 +6541,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33077r568046_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:266" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:266" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -7016,7 +6573,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33078r744001_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:267" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:267" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -7048,7 +6605,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33079r568052_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:268" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:268" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -7080,7 +6637,7 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33080r568055_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:269" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:269" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -7112,23 +6669,25 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
<xccdf:fix id="F-33081r568058_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:270" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:270" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-230438">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230438r627750_rule" weight="10.0" severity="medium">
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230438r810464_rule" weight="10.0" severity="medium">
<xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030360</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the init_module command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:title>Successful/unsuccessful uses of the init_module and finit_module system calls in RHEL 8 must generate an audit record.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "init_module" command is used to load a kernel module.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "init_module" and "finit_module" system calls are used to load a kernel module.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7137,31 +6696,38 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33082r568061_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "init_module" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
+ <xccdf:fixtext fixref="F-33082r810448_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "init_module" and "finit_module" system calls by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
--a always,exit -F arch=b32 -S init_module -F auid&gt;=1000 -F auid!=unset -k module_chng
--a always,exit -F arch=b64 -S init_module -F auid&gt;=1000 -F auid!=unset -k module_chng
+-a always,exit -F arch=b32 -S init_module,finit_module -F auid&gt;=1000 -F auid!=unset -k module_chng
+-a always,exit -F arch=b64 -S init_module,finit_module -F auid&gt;=1000 -F auid!=unset -k module_chng
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33082r568061_fix" />
+ <xccdf:fix id="F-33082r810448_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:271" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:271" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-230439">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230439r627750_rule" weight="10.0" severity="medium">
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230439r810465_rule" weight="10.0" severity="medium">
<xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030361</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the rename command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:title>Successful/unsuccessful uses of the rename, unlink, rmdir, renameat, and unlinkat system calls in RHEL 8 must generate an audit record.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "rename" command will rename the specified files by replacing the first occurrence of expression in their name by replacement.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "rename" system call will rename the specified files by replacing the first occurrence of expression in their name by replacement.
+
+The "unlink" system call deletes a name from the filesystem. If that name was the last link to a file and no processes have the file open, the file is deleted and the space it was using is made available for reuse.
+The "rmdir" system call removes empty directories.
+The "renameat" system call renames a file, moving it between directories if required.
+The "unlinkat" system call operates in exactly the same way as either "unlink" or "rmdir" except for the differences described in the manual page.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. Performance can be helped, however, by combining syscalls into one rule whenever possible.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7170,27 +6736,27 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33083r568064_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "rename" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
+ <xccdf:fixtext fixref="F-33083r809301_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "rename", "unlink", "rmdir", "renameat", and "unlinkat" system calls by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
--a always,exit -F arch=b32 -S rename -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S rename -F auid&gt;=1000 -F auid!=unset -k delete
+-a always,exit -F arch=b32 -S rename,unlink,rmdir,renameat,unlinkat -F auid&gt;=1000 -F auid!=unset -k delete
+-a always,exit -F arch=b64 -S rename,unlink,rmdir,renameat,unlinkat -F auid&gt;=1000 -F auid!=unset -k delete
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33083r568064_fix" />
+ <xccdf:fix id="F-33083r809301_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:272" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:272" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230440">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230444">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230440r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030362</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the renameat command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230444r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030370</xccdf:version>
+ <xccdf:title>Successful/unsuccessful uses of the gpasswd command in RHEL 8 must generate an audit record.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "renameat" command renames a file, moving it between directories if required.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "gpasswd" command is used to administer /etc/group and /etc/gshadow. Every group can have administrators, members and a password.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
@@ -7203,27 +6769,26 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33084r568067_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "renameat" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
+ <xccdf:fixtext fixref="F-33088r568079_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "gpasswd" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
--a always,exit -F arch=b32 -S renameat -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S renameat -F auid&gt;=1000 -F auid!=unset -k delete
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-gpasswd
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33084r568067_fix" />
+ <xccdf:fix id="F-33088r568079_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:273" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:277" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230441">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230446">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230441r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030363</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the rmdir command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230446r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030390</xccdf:version>
+ <xccdf:title>Successful/unsuccessful uses of the delete_module command in RHEL 8 must generate an audit record.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "rmdir" command removes empty directories.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "delete_module" command is used to unload a kernel module.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
@@ -7236,27 +6801,27 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33085r568070_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "rmdir" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
+ <xccdf:fixtext fixref="F-33090r568085_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "delete_module" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
--a always,exit -F arch=b32 -S rmdir -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S rmdir -F auid&gt;=1000 -F auid!=unset -k delete
+-a always,exit -F arch=b32 -S delete_module -F auid&gt;=1000 -F auid!=unset -k module_chng
+-a always,exit -F arch=b64 -S delete_module -F auid&gt;=1000 -F auid!=unset -k module_chng
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33085r568070_fix" />
+ <xccdf:fix id="F-33090r568085_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:274" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:279" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230442">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230447">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230442r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030364</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the unlink command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230447r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030400</xccdf:version>
+ <xccdf:title>Successful/unsuccessful uses of the crontab command in RHEL 8 must generate an audit record.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "unlink" command deletes a name from the filesystem. If that name was the last link to a file and no processes have the file open, the file is deleted and the space it was using is made available for reuse.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "crontab" command is used to maintain crontab files for individual users. Crontab is the program used to install, remove, or list the tables used to drive the cron daemon. This is similar to the task scheduler used in other operating systems.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
@@ -7269,27 +6834,26 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33086r568073_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "unlink" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
+ <xccdf:fixtext fixref="F-33091r568088_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "crontab" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
--a always,exit -F arch=b32 -S unlink -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S unlink -F auid&gt;=1000 -F auid!=unset -k delete
+-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-crontab
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33086r568073_fix" />
+ <xccdf:fix id="F-33091r568088_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:275" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:280" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230443">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230448">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230443r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030365</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the unlinkat command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230448r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030410</xccdf:version>
+ <xccdf:title>Successful/unsuccessful uses of the chsh command in RHEL 8 must generate an audit record.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "unlinkat" system call operates in exactly the same way as either "unlink" or "rmdir" except for the differences described in the manual page.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "chsh" command is used to change the login shell.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
@@ -7302,31 +6866,37 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33087r568076_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "unlinkat" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
+ <xccdf:fixtext fixref="F-33092r568091_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chsh" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
--a always,exit -F arch=b32 -S unlinkat -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S unlinkat -F auid&gt;=1000 -F auid!=unset -k delete
+-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid&gt;=1000 -F auid!=unset -k priv_cmd
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33087r568076_fix" />
+ <xccdf:fix id="F-33092r568091_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:276" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:281" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230444">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230449">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230444r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030370</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the gpasswd command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230449r810455_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030420</xccdf:version>
+ <xccdf:title>Successful/unsuccessful uses of the truncate, ftruncate, creat, open, openat, and open_by_handle_at system calls in RHEL 8 must generate an audit record.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "gpasswd" command is used to administer /etc/group and /etc/gshadow. Every group can have administrators, members and a password.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "truncate" and "ftruncate" functions are used to truncate a file to a specified length.
+
+The "creat" system call is used to open and possibly create a file or device.
+The "open" system call opens a file specified by a pathname. If the specified file does not exist, it may optionally be created by "open".
+The "openat" system call opens a file specified by a relative pathname.
+The "name_to_handle_at" and "open_by_handle_at" system calls split the functionality of "openat" into two parts: "name_to_handle_at" returns an opaque handle that corresponds to a specified file; "open_by_handle_at" opens the file corresponding to a handle returned by a previous call to "name_to_handle_at" and returns an open file descriptor.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7335,30 +6905,40 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33088r568079_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "gpasswd" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
+ <xccdf:fixtext fixref="F-33093r809304_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" system calls by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
--a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-gpasswd
+-a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
+-a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
+
+-a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
+-a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33088r568079_fix" />
+ <xccdf:fix id="F-33093r809304_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:277" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:282" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230445">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230455">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230445r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030380</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the finit_module command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230455r810459_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030480</xccdf:version>
+ <xccdf:title>Successful/unsuccessful uses of the chown, fchown, fchownat, and lchown system calls in RHEL 8 must generate an audit record.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "finit_module" command is used to load a kernel module.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "chown" command is used to change file owner and group.
+
+The "fchown" system call is used to change the ownership of a file referred to by the open file descriptor.
+The "fchownat" system call is used to change ownership of a file relative to a directory file descriptor.
+The "lchown" system call is used to change the ownership of the file specified by a path, which does not dereference symbolic links.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7367,31 +6947,36 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33089r568082_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "finit_module" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
+ <xccdf:fixtext fixref="F-33099r809307_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chown", "fchown", "fchownat", and "lchown" system calls by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
--a always,exit -F arch=b32 -S finit_module -F auid&gt;=1000 -F auid!=unset -k module_chng
--a always,exit -F arch=b64 -S finit_module -F auid&gt;=1000 -F auid!=unset -k module_chng
+-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33089r568082_fix" />
+ <xccdf:fix id="F-33099r809307_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:278" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:288" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230446">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230456">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230446r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030390</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the delete_module command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230456r810462_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030490</xccdf:version>
+ <xccdf:title>Successful/unsuccessful uses of the chmod, fchmod, and fchmodat system calls in RHEL 8 must generate an audit record.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "delete_module" command is used to unload a kernel module.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "chmod" system call changes the file mode bits of each given file according to mode, which can be either a symbolic representation of changes to make, or an octal number representing the bit pattern for the new mode bits.
+
+The "fchmod" system call is used to change permissions of a file.
+The "fchmodat" system call is used to change permissions of a file relative to a directory file descriptor.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. Performance can be helped, however, by combining syscalls into one rule whenever possible.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7400,31 +6985,31 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33090r568085_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "delete_module" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
+ <xccdf:fixtext fixref="F-33100r809310_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chmod", "fchmod", and "fchmodat" syscalls by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
--a always,exit -F arch=b32 -S delete_module -F auid&gt;=1000 -F auid!=unset -k module_chng
--a always,exit -F arch=b64 -S delete_module -F auid&gt;=1000 -F auid!=unset -k module_chng
+-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_mod
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33090r568085_fix" />
+ <xccdf:fix id="F-33100r809310_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:279" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:289" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230447">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230462">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230447r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030400</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the crontab command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230462r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030550</xccdf:version>
+ <xccdf:title>Successful/unsuccessful uses of the sudo command in RHEL 8 must generate an audit record.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "crontab" command is used to maintain crontab files for individual users. Crontab is the program used to install, remove, or list the tables used to drive the cron daemon. This is similar to the task scheduler used in other operating systems.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "sudo" command allows a permitted user to execute a command as the superuser or another user, as specified by the security policy.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7433,30 +7018,30 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33091r568088_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "crontab" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
+ <xccdf:fixtext fixref="F-33106r568133_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "sudo" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
--a always,exit -F path=/usr/bin/crontab -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-crontab
+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid&gt;=1000 -F auid!=unset -k priv_cmd
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33091r568088_fix" />
+ <xccdf:fix id="F-33106r568133_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:280" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:295" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230448">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230463">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230448r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030410</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the chsh command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230463r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030560</xccdf:version>
+ <xccdf:title>Successful/unsuccessful uses of the usermod command in RHEL 8 must generate an audit record.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "chsh" command is used to change the login shell.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "usermod" command modifies the system account files to reflect the changes that are specified on the command line.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7465,30 +7050,30 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33092r568091_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chsh" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
+ <xccdf:fixtext fixref="F-33107r568136_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "usermod" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
--a always,exit -F path=/usr/bin/chsh -F perm=x -F auid&gt;=1000 -F auid!=unset -k priv_cmd
+-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-usermod
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33092r568091_fix" />
+ <xccdf:fix id="F-33107r568136_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:281" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:296" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230449">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230464">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230449r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030420</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the truncate command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230464r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030570</xccdf:version>
+ <xccdf:title>Successful/unsuccessful uses of the chacl command in RHEL 8 must generate an audit record.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "truncate" and "ftruncate" functions are used to truncate a file to a specified length.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "chacl" command is used to change the access control list of a file or directory.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7497,34 +7082,40 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33093r568094_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "truncate" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
+ <xccdf:fixtext fixref="F-33108r568139_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chacl" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
+-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid&gt;=1000 -F auid!=unset -k perm_mod
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33093r568094_fix" />
+ <xccdf:fix id="F-33108r568139_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:282" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:297" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230450">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230465">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230450r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030430</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the openat system call in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230465r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030580</xccdf:version>
+ <xccdf:title>Successful/unsuccessful uses of the kmod command in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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 "openat" system call opens a file specified by a relative pathname.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "kmod" command is used to control Linux Kernel modules.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+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.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+DoD has defined the list of events for which RHEL 8 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.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7533,34 +7124,40 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33094r568097_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "openat" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
+ <xccdf:fixtext fixref="F-33109r568142_fix">Configure RHEL 8 to audit the execution of the module management program "kmod" by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
+-a always,exit -F path=/usr/bin/kmod -F perm=x -F auid&gt;=1000 -F auid!=unset -k modules
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33094r568097_fix" />
+ <xccdf:fix id="F-33109r568142_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:283" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:298" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230451">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230467">
<xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230451r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030440</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the open system call in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230467r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030600</xccdf:version>
+ <xccdf:title>Successful/unsuccessful modifications to the lastlog file in RHEL 8 must generate an audit record.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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 "open system" call opens a file specified by a pathname. If the specified file does not exist, it may optionally be created by "open".
+Audit records can be generated from various components within the information system (e.g., module or policy filter).
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+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 RHEL 8 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
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+4) All kernel module load, unload, and restart actions.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000473-GPOS-00218&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7569,34 +7166,24 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33095r568100_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "open" system call by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
+ <xccdf:fixtext fixref="F-33111r568148_fix">Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the "lastlog" file by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
+-w /var/log/lastlog -p wa -k logins
The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33095r568100_fix" />
+ <xccdf:fix id="F-33111r568148_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:284" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:299" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230452">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230471">
+ <xccdf:title>SRG-OS-000063-GPOS-00032</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230452r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030450</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the open_by_handle_at system call in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "name_to_handle_at" and "open_by_handle_at" system calls split the functionality of openat into two parts: "name_to_handle_at" returns an opaque handle that corresponds to a specified file; "open_by_handle_at" opens the file corresponding to a handle returned by a previous call to "name_to_handle_at" and returns an open file descriptor.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230471r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030610</xccdf:version>
+ <xccdf:title>RHEL 8 must allow only the Information System Security Manager (ISSM) (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Without the capability to restrict the roles and individuals that can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7604,35 +7191,29 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33096r568103_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "open_by_handle_at" system call by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000171</xccdf:ident>
+ <xccdf:fixtext fixref="F-33115r568160_fix">Configure the files in directory "/etc/audit/rules.d/" and the "/etc/audit/auditd.conf" file to have a mode of "0640" with the following commands:
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33096r568103_fix" />
+$ sudo chmod 0640 /etc/audit/rules.d/audit.rules
+$ sudo chmod 0640 /etc/audit/rules.d/[customrulesfile].rules
+$ sudo chmod 0640 /etc/audit/auditd.conf</xccdf:fixtext>
+ <xccdf:fix id="F-33115r568160_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:285" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:303" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230453">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230472">
+ <xccdf:title>SRG-OS-000256-GPOS-00097</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230453r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030460</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the ftruncate command in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "truncate" and "ftruncate" functions are used to truncate a file to a specified length.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230472r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030620</xccdf:version>
+ <xccdf:title>RHEL 8 audit tools must have a mode of 0755 or less permissive.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+RHEL 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.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7640,35 +7221,31 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33097r568106_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "ftruncate" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001493</xccdf:ident>
+ <xccdf:fixtext fixref="F-33116r568163_fix">Configure the audit tools to be protected from unauthorized access by setting the correct permissive mode using the following command:
--a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
+$ sudo chmod 0755 [audit_tool]
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33097r568106_fix" />
+Replace "[audit_tool]" with the audit tool that does not have the correct permissive mode.</xccdf:fixtext>
+ <xccdf:fix id="F-33116r568163_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:286" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:304" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230454">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230473">
+ <xccdf:title>SRG-OS-000256-GPOS-00097</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230454r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030470</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the creat system call in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230473r744008_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030630</xccdf:version>
+ <xccdf:title>RHEL 8 audit tools must be owned by root.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "creat" system call is used to open and possibly create a file or device.
+RHEL 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.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+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.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7676,35 +7253,31 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33098r568109_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "creat" system call by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001493</xccdf:ident>
+ <xccdf:fixtext fixref="F-33117r568166_fix">Configure the audit tools to be owned by "root", by running the following command:
--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
+$ sudo chown root [audit_tool]
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33098r568109_fix" />
+Replace "[audit_tool]" with each audit tool not owned by "root".</xccdf:fixtext>
+ <xccdf:fix id="F-33117r568166_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:287" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:305" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230455">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230474">
+ <xccdf:title>SRG-OS-000256-GPOS-00097</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230455r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030480</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the chown command in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230474r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030640</xccdf:version>
+ <xccdf:title>RHEL 8 audit tools must be group-owned by root.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "chown" command is used to change file owner and group.
+RHEL 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.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+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.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7712,32 +7285,36 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33099r568112_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chown" command by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001493</xccdf:ident>
+ <xccdf:fixtext fixref="F-33118r568169_fix">Configure the audit tools to be group-owned by "root", by running the following command:
--a always,exit -F arch=b32 -S chown -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S chown -F auid&gt;=1000 -F auid!=unset -k perm_mod
+$ sudo chgrp root [audit_tool]
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33099r568112_fix" />
+Replace "[audit_tool]" with each audit tool not group-owned by "root".</xccdf:fixtext>
+ <xccdf:fix id="F-33118r568169_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:288" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:306" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230456">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230477">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230456r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030490</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the chmod command in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230477r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030670</xccdf:version>
+ <xccdf:title>RHEL 8 must have the packages required for offloading audit logs installed.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "chmod" command changes the file mode bits of each given file according to mode, which can be either a symbolic representation of changes to make, or an octal number representing the bit pattern for the new mode bits.
+Off-loading is a common process in information systems with limited audit storage capacity.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+RHEL 8 installation media provides "rsyslogd". "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.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Rsyslog provides three ways to forward message: the traditional UDP transport, which is extremely lossy but standard; the plain TCP based transport, which loses messages only during certain situations but is widely available; and the RELP transport, which does not lose messages but is currently available only as part of the rsyslogd 3.15.0 and above.
+Examples of each configuration:
+UDP *.* @remotesystemname
+TCP *.* @@remotesystemname
+RELP *.* :omrelp:remotesystemname:2514
+Note that a port number was given as there is no standard port for RELP.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7745,32 +7322,34 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33100r568115_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chmod" command by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S chmod -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S chmod -F auid&gt;=1000 -F auid!=unset -k perm_mod
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33121r568178_fix">Configure the operating system to offload audit logs by installing the required packages with the following command:
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33100r568115_fix" />
+$ sudo yum install rsyslog</xccdf:fixtext>
+ <xccdf:fix id="F-33121r568178_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:289" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:412" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230457">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230478">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230457r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030500</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the lchown system call in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230478r744011_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030680</xccdf:version>
+ <xccdf:title>RHEL 8 must have the packages required for encrypting offloaded audit logs installed.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "lchown" system call is used to change the ownership of the file specified by a path, which does not dereference symbolic links.
+Off-loading is a common process in information systems with limited audit storage capacity.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+RHEL 8 installation media provides "rsyslogd". "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 "rsyslog-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.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Rsyslog provides three ways to forward message: the traditional UDP transport, which is extremely lossy but standard; the plain TCP based transport, which loses messages only during certain situations but is widely available; and the RELP transport, which does not lose messages but is currently available only as part of the rsyslogd 3.15.0 and above.
+Examples of each configuration:
+UDP *.* @remotesystemname
+TCP *.* @@remotesystemname
+RELP *.* :omrelp:remotesystemname:2514
+Note that a port number was given as there is no standard port for RELP.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7778,32 +7357,29 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33101r568118_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "lchown" system call by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S lchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S lchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33122r744010_fix">Configure the operating system to encrypt offloaded audit logs by installing the required packages with the following command:
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33101r568118_fix" />
+$ sudo yum install rsyslog-gnutls</xccdf:fixtext>
+ <xccdf:fix id="F-33122r744010_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:290" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:307" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230458">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230480">
+ <xccdf:title>SRG-OS-000342-GPOS-00133</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230458r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030510</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the fchownat system call in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230480r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030700</xccdf:version>
+ <xccdf:title>RHEL 8 must take appropriate action when the internal event queue is full.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "fchownat" system call is used to change ownership of a file relative to a directory file descriptor.
+Off-loading is a common process in information systems with limited audit storage capacity.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+RHEL 8 installation media provides "rsyslogd". "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.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7811,32 +7387,25 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33102r568121_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "fchownat" system call by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001851</xccdf:ident>
+ <xccdf:fixtext fixref="F-33124r568187_fix">Edit the /etc/audit/auditd.conf file and add or update the "overflow_action" option:
--a always,exit -F arch=b32 -S fchownat -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fchownat -F auid&gt;=1000 -F auid!=unset -k perm_mod
+overflow_action = syslog
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33102r568121_fix" />
+The audit daemon must be restarted for changes to take effect.</xccdf:fixtext>
+ <xccdf:fix id="F-33124r568187_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:291" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:308" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230459">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230483">
+ <xccdf:title>SRG-OS-000343-GPOS-00134</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230459r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030520</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the fchown system call in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "fchown" system call is used to change the ownership of a file referred to by the open file descriptor.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230483r744014_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030730</xccdf:version>
+ <xccdf:title>RHEL 8 must take action when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storage capacity expansion.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7844,32 +7413,31 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33103r568124_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "fchown" system call by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001855</xccdf:ident>
+ <xccdf:fixtext fixref="F-33127r744013_fix">Configure the operating system to initiate an action to notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity by adding/modifying the following line in the /etc/audit/auditd.conf file.
--a always,exit -F arch=b32 -S fchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
+space_left = 25%
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33103r568124_fix" />
+Note: Option names and values in the auditd.conf file are case insensitive.</xccdf:fixtext>
+ <xccdf:fix id="F-33127r744013_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:292" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:309" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230460">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230485">
+ <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230460r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030530</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the fchmodat system call in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230485r627750_rule" weight="10.0" severity="low">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030741</xccdf:version>
+ <xccdf:title>RHEL 8 must disable the chrony daemon from acting as a server.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "fchmodat" system call is used to change permissions of a file relative to a directory file descriptor.
+Minimizing the exposure of the server functionality of the chrony daemon diminishes the attack surface.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+RHEL 8 utilizes the "timedatectl" command to view the status of the "systemd-timesyncd.service". The "timedatectl" status will display the local time, UTC, and the offset from UTC.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Note that USNO offers authenticated NTP service to DoD and U.S. Government agencies operating on the NIPR and SIPR networks. Visit https://www.usno.navy.mil/USNO/time/ntp/dod-customers for more information.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7877,32 +7445,29 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33104r568127_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "fchmodat" system call by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_mod
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33129r568202_fix">Configure the operating system to disable the chrony daemon from acting as a server by adding/modifying the following line in the /etc/chrony.conf file.
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33104r568127_fix" />
+port 0</xccdf:fixtext>
+ <xccdf:fix id="F-33129r568202_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:293" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:310" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230461">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230486">
+ <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230461r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030540</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the fchmod system call in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230486r627750_rule" weight="10.0" severity="low">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030742</xccdf:version>
+ <xccdf:title>RHEL 8 must disable network management of the chrony daemon.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "fchmod" system call is used to change permissions of a file.
+Not exposing the management interface of the chrony daemon on the network diminishes the attack space.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+RHEL 8 utilizes the "timedatectl" command to view the status of the "systemd-timesyncd.service". The "timedatectl" status will display the local time, UTC, and the offset from UTC.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Note that USNO offers authenticated NTP service to DoD and U.S. Government agencies operating on the NIPR and SIPR networks. Visit https://www.usno.navy.mil/USNO/time/ntp/dod-customers for more information.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7910,32 +7475,33 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33105r568130_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "fchmod" system call by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S fchmod -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fchmod -F auid&gt;=1000 -F auid!=unset -k perm_mod
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33130r568205_fix">Configure the operating system disable network management of the chrony daemon by adding/modifying the following line in the /etc/chrony.conf file.
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33105r568130_fix" />
+cmdport 0</xccdf:fixtext>
+ <xccdf:fix id="F-33130r568205_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:294" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:311" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230462">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230487">
+ <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230462r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030550</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the sudo command in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230487r627750_rule" weight="10.0" severity="high">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040000</xccdf:version>
+ <xccdf:title>RHEL 8 must not have the telnet-server package installed.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "sudo" command allows a permitted user to execute a command as the superuser or another user, as specified by the security policy.
+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).
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+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.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Verify the operating system is configured to disable non-essential capabilities. The most secure way of ensuring a non-essential capability is disabled is to not have the capability installed.
+
+The telnet service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session.
+
+If a privileged user were to log on using this service, the privileged user password could be compromised.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7943,31 +7509,29 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33106r568133_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "sudo" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F path=/usr/bin/sudo -F perm=x -F auid&gt;=1000 -F auid!=unset -k priv_cmd
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33131r568208_fix">Configure the operating system to disable non-essential capabilities by removing the telnet-server package from the system with the following command:
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33106r568133_fix" />
+$ sudo yum remove telnet-server</xccdf:fixtext>
+ <xccdf:fix id="F-33131r568208_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:295" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:312" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230463">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230488">
+ <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230463r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030560</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the usermod command in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230488r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040001</xccdf:version>
+ <xccdf:title>RHEL 8 must not have any automated bug reporting tools installed.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "usermod" command modifies the system account files to reflect the changes that are specified on the command line.
+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).
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+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.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Verify the operating system is configured to disable non-essential capabilities. The most secure way of ensuring a non-essential capability is disabled is to not have the capability installed.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -7975,31 +7539,29 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33107r568136_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "usermod" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-usermod
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33132r568211_fix">Configure the operating system to disable non-essential capabilities by removing automated bug reporting packages from the system with the following command:
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33107r568136_fix" />
+$ sudo yum remove abrt*</xccdf:fixtext>
+ <xccdf:fix id="F-33132r568211_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:296" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:313" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230464">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230489">
+ <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230464r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030570</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the chacl command in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230489r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040002</xccdf:version>
+ <xccdf:title>RHEL 8 must not have the sendmail package installed.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "chacl" command is used to change the access control list of a file or directory.
+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).
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+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.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Verify the operating system is configured to disable non-essential capabilities. The most secure way of ensuring a non-essential capability is disabled is to not have the capability installed.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8007,41 +7569,31 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33108r568139_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chacl" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F path=/usr/bin/chacl -F perm=x -F auid&gt;=1000 -F auid!=unset -k perm_mod
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33133r568214_fix">Configure the operating system to disable non-essential capabilities by removing the sendmail package from the system with the following command:
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33108r568139_fix" />
+$ sudo yum remove sendmail</xccdf:fixtext>
+ <xccdf:fix id="F-33133r568214_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:297" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:314" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230465">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230492">
+ <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230465r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030580</xccdf:version>
- <xccdf:title>Successful/unsuccessful uses of the kmod command in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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 "kmod" command is used to control Linux Kernel modules.
-
-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 RHEL 8 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);
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230492r627750_rule" weight="10.0" severity="high">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040010</xccdf:version>
+ <xccdf:title>RHEL 8 must not have the rsh-server package installed.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-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;
+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).
-3) All account creations, modifications, disabling, and terminations; and
+The rsh-server service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session and has very weak authentication.
-4) All kernel module load, unload, and restart actions.
+If a privileged user were to log on using this service, the privileged user password could be compromised.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Satisfies: SRG-OS-000095-GPOS-00049, SRG-OS-000074-GPOS-00042&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8049,41 +7601,27 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33109r568142_fix">Configure RHEL 8 to audit the execution of the module management program "kmod" by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F path=/usr/bin/kmod -F perm=x -F auid&gt;=1000 -F auid!=unset -k modules
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33136r568223_fix">Configure the operating system to disable non-essential capabilities by removing the rsh-server package from the system with the following command:
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33109r568142_fix" />
+$ sudo yum remove rsh-server</xccdf:fixtext>
+ <xccdf:fix id="F-33136r568223_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:298" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:317" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230467">
- <xccdf:title>SRG-OS-000062-GPOS-00031</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230494">
+ <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230467r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030600</xccdf:version>
- <xccdf:title>Successful/unsuccessful modifications to the lastlog file in RHEL 8 must generate an audit record.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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 RHEL 8 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
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230494r792911_rule" weight="10.0" severity="low">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040021</xccdf:version>
+ <xccdf:title>RHEL 8 must disable the asynchronous transfer mode (ATM) protocol.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-4) All kernel module load, unload, and restart actions.
+Failing to disconnect unused protocols can result in a system compromise.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000473-GPOS-00218&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The Asynchronous Transfer Mode (ATM) is a protocol operating on network, data link, and physical layers, based on virtual circuits and virtual paths. Disabling ATM protects the system against exploitation of any laws in its implementation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8091,25 +7629,32 @@ Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000169</xccdf:ident>
- <xccdf:fixtext fixref="F-33111r568148_fix">Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the "lastlog" file by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33138r792910_fix">Configure the operating system to disable the ability to use the ATM protocol kernel module.
--w /var/log/lastlog -p wa -k logins
+Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
-The audit daemon must be restarted for the changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33111r568148_fix" />
+install atm /bin/true
+blacklist atm
+
+Reboot the system for the settings to take effect.</xccdf:fixtext>
+ <xccdf:fix id="F-33138r792910_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:299" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:318" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230471">
- <xccdf:title>SRG-OS-000063-GPOS-00032</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230495">
+ <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230471r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030610</xccdf:version>
- <xccdf:title>RHEL 8 must allow only the Information System Security Manager (ISSM) (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without the capability to restrict the roles and individuals that can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230495r792914_rule" weight="10.0" severity="low">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040022</xccdf:version>
+ <xccdf:title>RHEL 8 must disable the controller area network (CAN) protocol.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
+
+Failing to disconnect unused protocols can result in a system compromise.
+
+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. Disabling CAN protects the system against exploitation of any flaws in its implementation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8117,29 +7662,32 @@ The audit daemon must be restarted for the changes to take effect.</xccdf:fixtex
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000171</xccdf:ident>
- <xccdf:fixtext fixref="F-33115r568160_fix">Configure the files in directory "/etc/audit/rules.d/" and the "/etc/audit/auditd.conf" file to have a mode of "0640" with the following commands:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33139r792913_fix">Configure the operating system to disable the ability to use the CAN protocol kernel module.
-$ sudo chmod 0640 /etc/audit/rules.d/audit.rules
-$ sudo chmod 0640 /etc/audit/rules.d/[customrulesfile].rules
-$ sudo chmod 0640 /etc/audit/auditd.conf</xccdf:fixtext>
- <xccdf:fix id="F-33115r568160_fix" />
+Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
+
+install can /bin/true
+blacklist can
+
+Reboot the system for the settings to take effect.</xccdf:fixtext>
+ <xccdf:fix id="F-33139r792913_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:303" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:319" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230472">
- <xccdf:title>SRG-OS-000256-GPOS-00097</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230496">
+ <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230472r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030620</xccdf:version>
- <xccdf:title>RHEL 8 audit tools must have a mode of 0755 or less permissive.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230496r792917_rule" weight="10.0" severity="low">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040023</xccdf:version>
+ <xccdf:title>RHEL 8 must disable the stream control transmission protocol (SCTP).</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-RHEL 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.
+Failing to disconnect unused protocols can result in a system compromise.
-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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+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. Disabling SCTP protects the system against exploitation of any flaws in its implementation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8147,31 +7695,32 @@ Audit tools include, but are not limited to, vendor-provided and open source aud
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001493</xccdf:ident>
- <xccdf:fixtext fixref="F-33116r568163_fix">Configure the audit tools to be protected from unauthorized access by setting the correct permissive mode using the following command:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33140r792916_fix">Configure the operating system to disable the ability to use the SCTP kernel module.
-$ sudo chmod 0755 [audit_tool]
+Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
-Replace "[audit_tool]" with the audit tool that does not have the correct permissive mode.</xccdf:fixtext>
- <xccdf:fix id="F-33116r568163_fix" />
+install sctp /bin/true
+blacklist sctp
+
+Reboot the system for the settings to take effect.</xccdf:fixtext>
+ <xccdf:fix id="F-33140r792916_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:304" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:320" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230473">
- <xccdf:title>SRG-OS-000256-GPOS-00097</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230473r744008_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030630</xccdf:version>
- <xccdf:title>RHEL 8 audit tools must be owned by root.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-RHEL 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.
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230497">
+ <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230497r792920_rule" weight="10.0" severity="low">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040024</xccdf:version>
+ <xccdf:title>RHEL 8 must disable the transparent inter-process communication (TIPC) protocol.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-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.
+Failing to disconnect unused protocols can result in a system compromise.
-Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The Transparent Inter-Process Communication (TIPC) protocol is designed to provide communications between nodes in a cluster. Disabling TIPC protects the system against exploitation of any flaws in its implementation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8179,31 +7728,32 @@ Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001493</xccdf:ident>
- <xccdf:fixtext fixref="F-33117r568166_fix">Configure the audit tools to be owned by "root", by running the following command:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33141r792919_fix">Configure the operating system to disable the ability to use the TIPC protocol kernel module.
-$ sudo chown root [audit_tool]
+Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
-Replace "[audit_tool]" with each audit tool not owned by "root".</xccdf:fixtext>
- <xccdf:fix id="F-33117r568166_fix" />
+install tipc /bin/true
+blacklist tipc
+
+Reboot the system for the settings to take effect.</xccdf:fixtext>
+ <xccdf:fix id="F-33141r792919_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:305" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:321" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230474">
- <xccdf:title>SRG-OS-000256-GPOS-00097</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230498">
+ <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230474r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030640</xccdf:version>
- <xccdf:title>RHEL 8 audit tools must be group-owned by root.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-RHEL 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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230498r792922_rule" weight="10.0" severity="low">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040025</xccdf:version>
+ <xccdf:title>RHEL 8 must disable mounting of cramfs.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-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.
+Removing support for unneeded filesystem types reduces the local attack surface of the server.
-Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Compressed ROM/RAM file system (or cramfs) is a read-only file system designed for simplicity and space-efficiency. It is mainly used in embedded and small-footprint systems.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8211,36 +7761,30 @@ Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPO
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001493</xccdf:ident>
- <xccdf:fixtext fixref="F-33118r568169_fix">Configure the audit tools to be group-owned by "root", by running the following command:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33142r568241_fix">Configure the operating system to disable the ability to use the cramfs kernel module.
-$ sudo chgrp root [audit_tool]
+Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
-Replace "[audit_tool]" with each audit tool not group-owned by "root".</xccdf:fixtext>
- <xccdf:fix id="F-33118r568169_fix" />
+install cramfs /bin/true
+blacklist cramfs
+
+Reboot the system for the settings to take effect.</xccdf:fixtext>
+ <xccdf:fix id="F-33142r568241_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:306" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:322" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230477">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230499">
+ <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230477r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030670</xccdf:version>
- <xccdf:title>RHEL 8 must have the packages required for offloading audit logs installed.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-RHEL 8 installation media provides "rsyslogd". "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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230499r792924_rule" weight="10.0" severity="low">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040026</xccdf:version>
+ <xccdf:title>RHEL 8 must disable IEEE 1394 (FireWire) Support.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Rsyslog provides three ways to forward message: the traditional UDP transport, which is extremely lossy but standard; the plain TCP based transport, which loses messages only during certain situations but is widely available; and the RELP transport, which does not lose messages but is currently available only as part of the rsyslogd 3.15.0 and above.
-Examples of each configuration:
-UDP *.* @remotesystemname
-TCP *.* @@remotesystemname
-RELP *.* :omrelp:remotesystemname:2514
-Note that a port number was given as there is no standard port for RELP.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The IEEE 1394 (FireWire) is a serial bus standard for high-speed real-time communication. Disabling FireWire protects the system against exploitation of any flaws in its implementation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8248,34 +7792,30 @@ Note that a port number was given as there is no standard port for RELP.&lt;/Vul
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33121r568178_fix">Configure the operating system to offload audit logs by installing the required packages with the following command:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33143r568244_fix">Configure the operating system to disable the ability to use the firewire-core kernel module.
-$ sudo yum install rsyslog</xccdf:fixtext>
- <xccdf:fix id="F-33121r568178_fix" />
+Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
+
+install firewire-core /bin/true
+blacklist firewire-core
+
+Reboot the system for the settings to take effect.</xccdf:fixtext>
+ <xccdf:fix id="F-33143r568244_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:412" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:323" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230478">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230503">
+ <xccdf:title>SRG-OS-000114-GPOS-00059</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230478r744011_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030680</xccdf:version>
- <xccdf:title>RHEL 8 must have the packages required for encrypting offloaded audit logs installed.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-RHEL 8 installation media provides "rsyslogd". "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 "rsyslog-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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230503r809319_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040080</xccdf:version>
+ <xccdf:title>RHEL 8 must be configured to disable USB mass storage.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity.
-Rsyslog provides three ways to forward message: the traditional UDP transport, which is extremely lossy but standard; the plain TCP based transport, which loses messages only during certain situations but is widely available; and the RELP transport, which does not lose messages but is currently available only as part of the rsyslogd 3.15.0 and above.
-Examples of each configuration:
-UDP *.* @remotesystemname
-TCP *.* @@remotesystemname
-RELP *.* :omrelp:remotesystemname:2514
-Note that a port number was given as there is no standard port for RELP.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8283,29 +7823,32 @@ Note that a port number was given as there is no standard port for RELP.&lt;/Vul
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33122r744010_fix">Configure the operating system to encrypt offloaded audit logs by installing the required packages with the following command:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000778</xccdf:ident>
+ <xccdf:fixtext fixref="F-33147r809318_fix">Configure the operating system to disable the ability to use the USB Storage kernel module and the ability to use USB mass storage devices.
-$ sudo yum install rsyslog-gnutls</xccdf:fixtext>
- <xccdf:fix id="F-33122r744010_fix" />
+Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
+
+install usb-storage /bin/true
+blacklist usb-storage
+
+Reboot the system for the settings to take effect.</xccdf:fixtext>
+ <xccdf:fix id="F-33147r809318_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:307" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:325" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230480">
- <xccdf:title>SRG-OS-000342-GPOS-00133</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230507">
+ <xccdf:title>SRG-OS-000300-GPOS-00118</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230480r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030700</xccdf:version>
- <xccdf:title>RHEL 8 must take appropriate action when the internal event queue is full.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230507r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040111</xccdf:version>
+ <xccdf:title>RHEL 8 Bluetooth must be disabled.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read, altered, or used to compromise the RHEL 8 operating system.
-RHEL 8 installation media provides "rsyslogd". "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.
+This requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with RHEL 8 systems. Wireless peripherals (e.g., Wi-Fi/Bluetooth/IR Keyboards, Mice, and Pointing Devices and Near Field Communications [NFC]) present a unique challenge by creating an open, unsecured port on a computer. Wireless peripherals must meet DoD requirements for wireless data transmission and be approved for use by the Authorizing Official (AO). Even though some wireless peripherals, such as mice and pointing devices, do not ordinarily carry information that need to be protected, modification of communications with these wireless peripherals may be used to compromise the RHEL 8 operating system. Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification.
-Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Protecting the confidentiality and integrity of communications with wireless peripherals can be accomplished by physical means (e.g., employing physical barriers to wireless radio frequencies) 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. If the wireless peripheral is only passing telemetry data, encryption of the data may not be required.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8313,25 +7856,33 @@ Satisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224&lt;/VulnDiscussion
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001851</xccdf:ident>
- <xccdf:fixtext fixref="F-33124r568187_fix">Edit the /etc/audit/auditd.conf file and add or update the "overflow_action" option:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001443</xccdf:ident>
+ <xccdf:fixtext fixref="F-33151r568268_fix">Configure the operating system to disable the Bluetooth adapter when not in use.
-overflow_action = syslog
+Build or modify the "/etc/modprobe.d/bluetooth.conf" file with the following line:
-The audit daemon must be restarted for changes to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33124r568187_fix" />
+install bluetooth /bin/true
+
+Reboot the system for the settings to take effect.</xccdf:fixtext>
+ <xccdf:fix id="F-33151r568268_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:308" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:326" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230483">
- <xccdf:title>SRG-OS-000343-GPOS-00134</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230508">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230483r744014_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030730</xccdf:version>
- <xccdf:title>RHEL 8 must take action when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storage capacity expansion.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230508r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040120</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /dev/shm with the nodev option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
+
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+
+The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8339,31 +7890,27 @@ The audit daemon must be restarted for changes to take effect.</xccdf:fixtext>
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001855</xccdf:ident>
- <xccdf:fixtext fixref="F-33127r744013_fix">Configure the operating system to initiate an action to notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity by adding/modifying the following line in the /etc/audit/auditd.conf file.
-
-space_left = 25%
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33152r568271_fix">Configure the system so that /dev/shm is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line:
-Note: Option names and values in the auditd.conf file are case insensitive.</xccdf:fixtext>
- <xccdf:fix id="F-33127r744013_fix" />
+tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33152r568271_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:309" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:327" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230485">
- <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230509">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230485r627750_rule" weight="10.0" severity="low">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030741</xccdf:version>
- <xccdf:title>RHEL 8 must disable the chrony daemon from acting as a server.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-Minimizing the exposure of the server functionality of the chrony daemon diminishes the attack surface.
-
-RHEL 8 utilizes the "timedatectl" command to view the status of the "systemd-timesyncd.service". The "timedatectl" status will display the local time, UTC, and the offset from UTC.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230509r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040121</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /dev/shm with the nosuid option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Note that USNO offers authenticated NTP service to DoD and U.S. Government agencies operating on the NIPR and SIPR networks. Visit https://www.usno.navy.mil/USNO/time/ntp/dod-customers for more information.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8371,29 +7918,29 @@ Note that USNO offers authenticated NTP service to DoD and U.S. Government agenc
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33129r568202_fix">Configure the operating system to disable the chrony daemon from acting as a server by adding/modifying the following line in the /etc/chrony.conf file.
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33153r568274_fix">Configure the system so that /dev/shm is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line:
-port 0</xccdf:fixtext>
- <xccdf:fix id="F-33129r568202_fix" />
+tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33153r568274_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:310" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:328" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230486">
- <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230510">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230486r627750_rule" weight="10.0" severity="low">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-030742</xccdf:version>
- <xccdf:title>RHEL 8 must disable network management of the chrony daemon.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230510r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040122</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /dev/shm with the noexec option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Not exposing the management interface of the chrony daemon on the network diminishes the attack space.
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-RHEL 8 utilizes the "timedatectl" command to view the status of the "systemd-timesyncd.service". The "timedatectl" status will display the local time, UTC, and the offset from UTC.
+The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-Note that USNO offers authenticated NTP service to DoD and U.S. Government agencies operating on the NIPR and SIPR networks. Visit https://www.usno.navy.mil/USNO/time/ntp/dod-customers for more information.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8401,33 +7948,29 @@ Note that USNO offers authenticated NTP service to DoD and U.S. Government agenc
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33130r568205_fix">Configure the operating system disable network management of the chrony daemon by adding/modifying the following line in the /etc/chrony.conf file.
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33154r568277_fix">Configure the system so that /dev/shm is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line:
-cmdport 0</xccdf:fixtext>
- <xccdf:fix id="F-33130r568205_fix" />
+tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33154r568277_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:311" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:329" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230487">
- <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230511">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230487r627750_rule" weight="10.0" severity="high">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040000</xccdf:version>
- <xccdf:title>RHEL 8 must not have the telnet-server package installed.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230511r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040123</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /tmp with the nodev option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-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).
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-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.
-
-Verify the operating system is configured to disable non-essential capabilities. The most secure way of ensuring a non-essential capability is disabled is to not have the capability installed.
-
-The telnet service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session.
+The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-If a privileged user were to log on using this service, the privileged user password could be compromised.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8435,29 +7978,27 @@ If a privileged user were to log on using this service, the privileged user pass
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33131r568208_fix">Configure the operating system to disable non-essential capabilities by removing the telnet-server package from the system with the following command:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33155r568280_fix">Configure the system so that /tmp is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line:
-$ sudo yum remove telnet-server</xccdf:fixtext>
- <xccdf:fix id="F-33131r568208_fix" />
+/dev/mapper/rhel-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33155r568280_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:312" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:330" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230488">
- <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230512">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230488r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040001</xccdf:version>
- <xccdf:title>RHEL 8 must not have any automated bug reporting tools installed.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230512r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040124</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /tmp with the nosuid option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Verify the operating system is configured to disable non-essential capabilities. The most secure way of ensuring a non-essential capability is disabled is to not have the capability installed.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8465,29 +8006,29 @@ Verify the operating system is configured to disable non-essential capabilities.
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33132r568211_fix">Configure the operating system to disable non-essential capabilities by removing automated bug reporting packages from the system with the following command:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33156r568283_fix">Configure the system so that /tmp is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line:
-$ sudo yum remove abrt*</xccdf:fixtext>
- <xccdf:fix id="F-33132r568211_fix" />
+/dev/mapper/rhel-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33156r568283_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:313" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:331" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230489">
- <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230513">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230489r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040002</xccdf:version>
- <xccdf:title>RHEL 8 must not have the sendmail package installed.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230513r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040125</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /tmp with the noexec option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-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).
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-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 "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-Verify the operating system is configured to disable non-essential capabilities. The most secure way of ensuring a non-essential capability is disabled is to not have the capability installed.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8495,31 +8036,29 @@ Verify the operating system is configured to disable non-essential capabilities.
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33133r568214_fix">Configure the operating system to disable non-essential capabilities by removing the sendmail package from the system with the following command:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33157r568286_fix">Configure the system so that /tmp is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line:
-$ sudo yum remove sendmail</xccdf:fixtext>
- <xccdf:fix id="F-33133r568214_fix" />
+/dev/mapper/rhel-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33157r568286_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:314" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:332" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230492">
- <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230514">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230492r627750_rule" weight="10.0" severity="high">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040010</xccdf:version>
- <xccdf:title>RHEL 8 must not have the rsh-server package installed.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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).
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230514r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040126</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /var/log with the nodev option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-The rsh-server service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session and has very weak authentication.
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-If a privileged user were to log on using this service, the privileged user password could be compromised.
+The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-Satisfies: SRG-OS-000095-GPOS-00049, SRG-OS-000074-GPOS-00042&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8527,27 +8066,29 @@ Satisfies: SRG-OS-000095-GPOS-00049, SRG-OS-000074-GPOS-00042&lt;/VulnDiscussion
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33136r568223_fix">Configure the operating system to disable non-essential capabilities by removing the rsh-server package from the system with the following command:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33158r568289_fix">Configure the system so that /var/log is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line:
-$ sudo yum remove rsh-server</xccdf:fixtext>
- <xccdf:fix id="F-33136r568223_fix" />
+/dev/mapper/rhel-var-log /var/log xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33158r568289_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:317" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:333" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230494">
- <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230515">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230494r792911_rule" weight="10.0" severity="low">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040021</xccdf:version>
- <xccdf:title>RHEL 8 must disable the asynchronous transfer mode (ATM) protocol.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230515r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040127</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /var/log with the nosuid option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Failing to disconnect unused protocols can result in a system compromise.
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-The Asynchronous Transfer Mode (ATM) is a protocol operating on network, data link, and physical layers, based on virtual circuits and virtual paths. Disabling ATM protects the system against exploitation of any laws in its implementation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8555,32 +8096,29 @@ The Asynchronous Transfer Mode (ATM) is a protocol operating on network, data li
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33138r792910_fix">Configure the operating system to disable the ability to use the ATM protocol kernel module.
-
-Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
-
-install atm /bin/true
-blacklist atm
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33159r568292_fix">Configure the system so that /var/log is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line:
-Reboot the system for the settings to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33138r792910_fix" />
+/dev/mapper/rhel-var-log /var/log xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33159r568292_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:318" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:334" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230495">
- <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230516">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230495r792914_rule" weight="10.0" severity="low">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040022</xccdf:version>
- <xccdf:title>RHEL 8 must disable the controller area network (CAN) protocol.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230516r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040128</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /var/log with the noexec option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Failing to disconnect unused protocols can result in a system compromise.
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-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. Disabling CAN protects the system against exploitation of any flaws in its implementation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8588,32 +8126,29 @@ The Controller Area Network (CAN) is a serial communications protocol, which was
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33139r792913_fix">Configure the operating system to disable the ability to use the CAN protocol kernel module.
-
-Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
-
-install can /bin/true
-blacklist can
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33160r568295_fix">Configure the system so that /var/log is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line:
-Reboot the system for the settings to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33139r792913_fix" />
+/dev/mapper/rhel-var-log /var/log xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33160r568295_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:319" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:335" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230496">
- <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230517">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230496r792917_rule" weight="10.0" severity="low">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040023</xccdf:version>
- <xccdf:title>RHEL 8 must disable the stream control transmission protocol (SCTP).</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230517r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040129</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /var/log/audit with the nodev option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Failing to disconnect unused protocols can result in a system compromise.
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-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. Disabling SCTP protects the system against exploitation of any flaws in its implementation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8621,32 +8156,29 @@ The Stream Control Transmission Protocol (SCTP) is a transport layer protocol, d
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33140r792916_fix">Configure the operating system to disable the ability to use the SCTP kernel module.
-
-Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
-
-install sctp /bin/true
-blacklist sctp
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33161r568298_fix">Configure the system so that /var/log/audit is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line:
-Reboot the system for the settings to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33140r792916_fix" />
+/dev/mapper/rhel-var-log-audit /var/log/audit xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33161r568298_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:320" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:336" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230497">
- <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230518">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230497r792920_rule" weight="10.0" severity="low">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040024</xccdf:version>
- <xccdf:title>RHEL 8 must disable the transparent inter-process communication (TIPC) protocol.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230518r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040130</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /var/log/audit with the nosuid option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Failing to disconnect unused protocols can result in a system compromise.
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-The Transparent Inter-Process Communication (TIPC) protocol is designed to provide communications between nodes in a cluster. Disabling TIPC protects the system against exploitation of any flaws in its implementation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8654,32 +8186,29 @@ The Transparent Inter-Process Communication (TIPC) protocol is designed to provi
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33141r792919_fix">Configure the operating system to disable the ability to use the TIPC protocol kernel module.
-
-Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
-
-install tipc /bin/true
-blacklist tipc
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33162r568301_fix">Configure the system so that /var/log/audit is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line:
-Reboot the system for the settings to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33141r792919_fix" />
+/dev/mapper/rhel-var-log-audit /var/log/audit xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33162r568301_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:321" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:337" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230498">
- <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230519">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230498r792922_rule" weight="10.0" severity="low">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040025</xccdf:version>
- <xccdf:title>RHEL 8 must disable mounting of cramfs.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230519r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040131</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /var/log/audit with the noexec option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-Removing support for unneeded filesystem types reduces the local attack surface of the server.
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-Compressed ROM/RAM file system (or cramfs) is a read-only file system designed for simplicity and space-efficiency. It is mainly used in embedded and small-footprint systems.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8687,103 +8216,29 @@ Compressed ROM/RAM file system (or cramfs) is a read-only file system designed f
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33142r568241_fix">Configure the operating system to disable the ability to use the cramfs kernel module.
-
-Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
-
-install cramfs /bin/true
-blacklist cramfs
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33163r568304_fix">Configure the system so that /var/log/audit is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line:
-Reboot the system for the settings to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33142r568241_fix" />
+/dev/mapper/rhel-var-log-audit /var/log/audit xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33163r568304_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:322" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:338" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230499">
- <xccdf:title>SRG-OS-000095-GPOS-00049</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230520">
+ <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230499r792924_rule" weight="10.0" severity="low">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040026</xccdf:version>
- <xccdf:title>RHEL 8 must disable IEEE 1394 (FireWire) Support.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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 IEEE 1394 (FireWire) is a serial bus standard for high-speed real-time communication. Disabling FireWire protects the system against exploitation of any flaws in its implementation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33143r568244_fix">Configure the operating system to disable the ability to use the firewire-core kernel module.
-
-Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
-
-install firewire-core /bin/true
-blacklist firewire-core
-
-Reboot the system for the settings to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33143r568244_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:323" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230503">
- <xccdf:title>SRG-OS-000114-GPOS-00059</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230503r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040080</xccdf:version>
- <xccdf:title>RHEL 8 must be configured to disable USB mass storage.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity.
-
-Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000778</xccdf:ident>
- <xccdf:fixtext fixref="F-33147r568256_fix">Configure the operating system to disable the ability to use the USB Storage kernel module.
-
-Create a file under "/etc/modprobe.d" with the following command:
-
-$ sudo touch /etc/modprobe.d/usb-storage.conf
-
-Add the following line to the created file:
-
-install usb-storage /bin/true
-
-Configure the operating system to disable the ability to use USB mass storage devices.
-
-$ sudo vi /etc/modprobe.d/blacklist.conf
-
-Add or update the line:
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230520r792927_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040132</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /var/tmp with the nodev option.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-blacklist usb-storage</xccdf:fixtext>
- <xccdf:fix id="F-33147r568256_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:325" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230507">
- <xccdf:title>SRG-OS-000300-GPOS-00118</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230507r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040111</xccdf:version>
- <xccdf:title>RHEL 8 Bluetooth must be disabled.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read, altered, or used to compromise the RHEL 8 operating system.
+The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-This requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with RHEL 8 systems. Wireless peripherals (e.g., Wi-Fi/Bluetooth/IR Keyboards, Mice, and Pointing Devices and Near Field Communications [NFC]) present a unique challenge by creating an open, unsecured port on a computer. Wireless peripherals must meet DoD requirements for wireless data transmission and be approved for use by the Authorizing Official (AO). Even though some wireless peripherals, such as mice and pointing devices, do not ordinarily carry information that need to be protected, modification of communications with these wireless peripherals may be used to compromise the RHEL 8 operating system. Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification.
+The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-Protecting the confidentiality and integrity of communications with wireless peripherals can be accomplished by physical means (e.g., employing physical barriers to wireless radio frequencies) 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. If the wireless peripheral is only passing telemetry data, encryption of the data may not be required.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8791,26 +8246,22 @@ Protecting the confidentiality and integrity of communications with wireless per
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001443</xccdf:ident>
- <xccdf:fixtext fixref="F-33151r568268_fix">Configure the operating system to disable the Bluetooth adapter when not in use.
-
-Build or modify the "/etc/modprobe.d/bluetooth.conf" file with the following line:
-
-install bluetooth /bin/true
+ <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
+ <xccdf:fixtext fixref="F-33164r792926_fix">Configure the system so that /var/tmp is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line:
-Reboot the system for the settings to take effect.</xccdf:fixtext>
- <xccdf:fix id="F-33151r568268_fix" />
+/dev/mapper/rhel-var-tmp /var/tmp xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33164r792926_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:326" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:339" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230508">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230521">
<xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230508r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040120</xccdf:version>
- <xccdf:title>RHEL 8 must mount /dev/shm with the nodev option.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230521r792930_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040133</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /var/tmp with the nosuid option.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;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.
The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
@@ -8826,25 +8277,27 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33152r568271_fix">Configure the system so that /dev/shm is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:fixtext fixref="F-33165r792929_fix">Configure the system so that /var/tmp is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line:
-tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33152r568271_fix" />
+/dev/mapper/rhel-var-tmp /var/tmp xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33165r792929_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:327" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:340" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230509">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230522">
<xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230509r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040121</xccdf:version>
- <xccdf:title>RHEL 8 must mount /dev/shm with the nosuid option.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230522r792933_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040134</xccdf:version>
+ <xccdf:title>RHEL 8 must mount /var/tmp with the noexec option.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;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.
The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+
The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+
The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
@@ -8854,28 +8307,28 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33153r568274_fix">Configure the system so that /dev/shm is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:fixtext fixref="F-33166r792932_fix">Configure the system so that /var/tmp is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line:
-tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33153r568274_fix" />
+/dev/mapper/rhel-var-tmp /var/tmp xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
+ <xccdf:fix id="F-33166r792932_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:328" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:341" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230510">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230526">
+ <xccdf:title>SRG-OS-000423-GPOS-00187</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230510r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040122</xccdf:version>
- <xccdf:title>RHEL 8 must mount /dev/shm with the noexec option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230526r744032_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040160</xccdf:version>
+ <xccdf:title>All RHEL 8 networked systems must have and implement SSH to protect the confidentiality and integrity of transmitted and received information, as well as information during preparation for transmission.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered.
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+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.
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+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 "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8883,29 +8336,31 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33154r568277_fix">Configure the system so that /dev/shm is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-002418</xccdf:ident>
+ <xccdf:fixtext fixref="F-33170r744031_fix">Configure the SSH service to automatically start after reboot with the following command:
-tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33154r568277_fix" />
+$ sudo systemctl enable sshd.service</xccdf:fixtext>
+ <xccdf:fix id="F-33170r744031_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:329" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:342" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230511">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230527">
+ <xccdf:title>SRG-OS-000033-GPOS-00014</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230511r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040123</xccdf:version>
- <xccdf:title>RHEL 8 must mount /tmp with the nodev option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230527r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040161</xccdf:version>
+ <xccdf:title>RHEL 8 must force a frequent session key renegotiation for SSH connections to the server.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered.
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+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.
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+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 "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Session key regeneration limits the chances of a session key becoming compromised.
+
+Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000420-GPOS-00186, SRG-OS-000424-GPOS-00188&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8913,27 +8368,27 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33155r568280_fix">Configure the system so that /tmp is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000068</xccdf:ident>
+ <xccdf:fixtext fixref="F-33171r568328_fix">Configure the system to force a frequent session key renegotiation for SSH connections to the server by add or modifying the following line in the "/etc/ssh/sshd_config" file:
-/dev/mapper/rhel-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33155r568280_fix" />
+RekeyLimit 1G 1h
+
+Restart the SSH daemon for the settings to take effect.
+
+$ sudo systemctl restart sshd.service</xccdf:fixtext>
+ <xccdf:fix id="F-33171r568328_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:330" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:343" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230512">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230531">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230512r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040124</xccdf:version>
- <xccdf:title>RHEL 8 must mount /tmp with the nosuid option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230531r627750_rule" weight="10.0" severity="high">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040172</xccdf:version>
+ <xccdf:title>The systemd Ctrl-Alt-Delete burst key sequence in RHEL 8 must be disabled.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;A locally logged-on user who presses Ctrl-Alt-Delete when at the console can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In a graphical user environment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is reduced because the user will be prompted before any action is taken.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8941,29 +8396,27 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33156r568283_fix">Configure the system so that /tmp is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33175r619890_fix">Configure the system to disable the CtrlAltDelBurstAction by added or modifying the following line in the "/etc/systemd/system.conf" configuration file:
-/dev/mapper/rhel-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33156r568283_fix" />
+CtrlAltDelBurstAction=none
+
+Reload the daemon for this change to take effect.
+
+$ sudo systemctl daemon-reload</xccdf:fixtext>
+ <xccdf:fix id="F-33175r619890_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:331" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:345" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230513">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230533">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230513r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040125</xccdf:version>
- <xccdf:title>RHEL 8 must mount /tmp with the noexec option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-
-The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230533r627750_rule" weight="10.0" severity="high">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040190</xccdf:version>
+ <xccdf:title>The Trivial File Transfer Protocol (TFTP) server package must not be installed if not required for RHEL 8 operational support.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;If TFTP is required for operational support (such as the transmission of router configurations) its use must be documented with the Information System Security Officer (ISSO), restricted to only authorized personnel, and have access control rules established.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -8971,29 +8424,23 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33157r568286_fix">Configure the system so that /tmp is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33177r568346_fix">Remove the TFTP package from the system with the following command:
-/dev/mapper/rhel-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33157r568286_fix" />
+$ sudo yum remove tftp-server</xccdf:fixtext>
+ <xccdf:fix id="F-33177r568346_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:332" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:346" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230514">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230534">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230514r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040126</xccdf:version>
- <xccdf:title>RHEL 8 must mount /var/log with the nodev option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-
-The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230534r627750_rule" weight="10.0" severity="high">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040200</xccdf:version>
+ <xccdf:title>The root account must be the only account having unrestricted access to the RHEL 8 system.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;If an account other than root also has a User Identifier (UID) of "0", it has root authority, giving that account unrestricted access to the entire operating system. Multiple accounts with a UID of "0" afford an opportunity for potential intruders to guess a password for a privileged account.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9001,29 +8448,33 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33158r568289_fix">Configure the system so that /var/log is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33178r568349_fix">Change the UID of any account on the system, other than root, that has a UID of "0".
-/dev/mapper/rhel-var-log /var/log xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33158r568289_fix" />
+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 of greater than "1000" that has not already been assigned.</xccdf:fixtext>
+ <xccdf:fix id="F-33178r568349_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:333" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:347" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230515">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230535">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230515r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040127</xccdf:version>
- <xccdf:title>RHEL 8 must mount /var/log with the nosuid option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230535r792936_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040210</xccdf:version>
+ <xccdf:title>RHEL 8 must prevent IPv6 Internet Control Message Protocol (ICMP) redirect messages from being accepted.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf
+/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
-The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9031,29 +8482,41 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33159r568292_fix">Configure the system so that /var/log is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33179r792935_fix">Configure RHEL 8 to prevent IPv6 ICMP redirect messages from being accepted.
-/dev/mapper/rhel-var-log /var/log xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33159r568292_fix" />
+Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
+
+net.ipv6.conf.default.accept_redirects = 0
+
+Load settings from all system configuration files with the following command:
+
+$ sudo sysctl --system</xccdf:fixtext>
+ <xccdf:fix id="F-33179r792935_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:334" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:348" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230516">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230536">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230516r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040128</xccdf:version>
- <xccdf:title>RHEL 8 must mount /var/log with the noexec option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230536r792939_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040220</xccdf:version>
+ <xccdf:title>RHEL 8 must not send Internet Control Message Protocol (ICMP) redirects.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+There are notable differences between Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). There is only a directive to disable sending of IPv4 redirected packets. Refer to RFC4294 for an explanation of "IPv6 Node Requirements", which resulted in this difference between IPv4 and IPv6.
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf
+/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
-The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9061,29 +8524,40 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33160r568295_fix">Configure the system so that /var/log is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33180r792938_fix">Configure RHEL 8 to not allow interfaces to perform IPv4 ICMP redirects.
-/dev/mapper/rhel-var-log /var/log xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33160r568295_fix" />
+Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
+
+net.ipv4.conf.all.send_redirects=0
+
+Load settings from all system configuration files with the following command:
+
+$ sudo sysctl --system</xccdf:fixtext>
+ <xccdf:fix id="F-33180r792938_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:335" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:349" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230517">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230537">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230517r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040129</xccdf:version>
- <xccdf:title>RHEL 8 must mount /var/log/audit with the nodev option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230537r792942_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040230</xccdf:version>
+ <xccdf:title>RHEL 8 must not respond to Internet Control Message Protocol (ICMP) echoes sent to a broadcast address.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Responding to broadcast ICMP echoes facilitates network mapping and provides a vector for amplification attacks.
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+There are notable differences between Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). IPv6 does not implement the same method of broadcast as IPv4. Instead, IPv6 uses multicast addressing to the all-hosts multicast group. Refer to RFC4294 for an explanation of "IPv6 Node Requirements", which resulted in this difference between IPv4 and IPv6.
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf
+/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
-The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9091,29 +8565,39 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33161r568298_fix">Configure the system so that /var/log/audit is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33181r792941_fix">Configure RHEL 8 to not respond to IPv4 ICMP echoes sent to a broadcast address.
-/dev/mapper/rhel-var-log-audit /var/log/audit xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33161r568298_fix" />
+Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
+
+net.ipv4.icmp_echo_ignore_broadcasts=1
+
+Load settings from all system configuration files with the following command:
+
+$ sudo sysctl --system</xccdf:fixtext>
+ <xccdf:fix id="F-33181r792941_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:336" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:350" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230518">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230538">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230518r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040130</xccdf:version>
- <xccdf:title>RHEL 8 must mount /var/log/audit with the nosuid option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230538r792945_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040240</xccdf:version>
+ <xccdf:title>RHEL 8 must not forward IPv6 source-routed packets.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when forwarding is enabled and the system is functioning as a router.
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf
+/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
-The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9121,29 +8605,39 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33162r568301_fix">Configure the system so that /var/log/audit is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33182r792944_fix">Configure RHEL 8 to not forward IPv6 source-routed packets.
-/dev/mapper/rhel-var-log-audit /var/log/audit xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33162r568301_fix" />
+Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
+
+net.ipv6.conf.all.accept_source_route=0
+
+Load settings from all system configuration files with the following command:
+
+$ sudo sysctl --system</xccdf:fixtext>
+ <xccdf:fix id="F-33182r792944_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:337" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:351" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230519">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230539">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230519r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040131</xccdf:version>
- <xccdf:title>RHEL 8 must mount /var/log/audit with the noexec option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230539r792948_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040250</xccdf:version>
+ <xccdf:title>RHEL 8 must not forward IPv6 source-routed packets by default.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when forwarding is enabled and the system is functioning as a router.
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf
+/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
-The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9151,29 +8645,39 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33163r568304_fix">Configure the system so that /var/log/audit is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33183r792947_fix">Configure RHEL 8 to not forward IPv6 source-routed packets by default.
-/dev/mapper/rhel-var-log-audit /var/log/audit xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33163r568304_fix" />
+Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
+
+net.ipv6.conf.default.accept_source_route=0
+
+Load settings from all system configuration files with the following command:
+
+$ sudo sysctl --system</xccdf:fixtext>
+ <xccdf:fix id="F-33183r792947_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:338" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:352" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230520">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230540">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230520r792927_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040132</xccdf:version>
- <xccdf:title>RHEL 8 must mount /var/tmp with the nodev option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230540r792951_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040260</xccdf:version>
+ <xccdf:title>RHEL 8 must not enable IPv6 packet forwarding unless the system is a router.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf
+/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
-The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9181,29 +8685,41 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33164r792926_fix">Configure the system so that /var/tmp is mounted with the "nodev" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33184r792950_fix">Configure RHEL 8 to not allow IPv6 packet forwarding, unless the system is a router.
-/dev/mapper/rhel-var-tmp /var/tmp xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33164r792926_fix" />
+Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
+
+net.ipv6.conf.all.forwarding=0
+
+Load settings from all system configuration files with the following command:
+
+$ sudo sysctl --system</xccdf:fixtext>
+ <xccdf:fix id="F-33184r792950_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:339" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:353" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230521">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230541">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230521r792930_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040133</xccdf:version>
- <xccdf:title>RHEL 8 must mount /var/tmp with the nosuid option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230541r792954_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040261</xccdf:version>
+ <xccdf:title>RHEL 8 must not accept router advertisements on all IPv6 interfaces.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+An illicit router advertisement message could result in a man-in-the-middle attack.
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf
+/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
-The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9211,119 +8727,41 @@ The "nosuid" mount option causes the system to not execute "setuid" and "setgid"
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33165r792929_fix">Configure the system so that /var/tmp is mounted with the "nosuid" option by adding /modifying the /etc/fstab with the following line:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
+ <xccdf:fixtext fixref="F-33185r792953_fix">Configure RHEL 8 to not accept router advertisements on all IPv6 interfaces unless the system is a router.
-/dev/mapper/rhel-var-tmp /var/tmp xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33165r792929_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:340" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230522">
- <xccdf:title>SRG-OS-000368-GPOS-00154</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230522r792933_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040134</xccdf:version>
- <xccdf:title>RHEL 8 must mount /var/tmp with the noexec option.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-
-The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
-
-The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-001764</xccdf:ident>
- <xccdf:fixtext fixref="F-33166r792932_fix">Configure the system so that /var/tmp is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line:
-
-/dev/mapper/rhel-var-tmp /var/tmp xfs defaults,nodev,nosuid,noexec 0 0</xccdf:fixtext>
- <xccdf:fix id="F-33166r792932_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:341" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230526">
- <xccdf:title>SRG-OS-000423-GPOS-00187</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230526r744032_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040160</xccdf:version>
- <xccdf:title>All RHEL 8 networked systems must have and implement SSH to protect the confidentiality and integrity of transmitted and received information, as well as information during preparation for transmission.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
+Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
-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.
+net.ipv6.conf.all.accept_ra=0
-Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-002418</xccdf:ident>
- <xccdf:fixtext fixref="F-33170r744031_fix">Configure the SSH service to automatically start after reboot with the following command:
+Load settings from all system configuration files with the following command:
-$ sudo systemctl enable sshd.service</xccdf:fixtext>
- <xccdf:fix id="F-33170r744031_fix" />
+$ sudo sysctl --system</xccdf:fixtext>
+ <xccdf:fix id="F-33185r792953_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:342" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:354" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230527">
- <xccdf:title>SRG-OS-000033-GPOS-00014</xccdf:title>
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230542">
+ <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230527r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040161</xccdf:version>
- <xccdf:title>RHEL 8 must force a frequent session key renegotiation for SSH connections to the server.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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.
-
-Session key regeneration limits the chances of a session key becoming compromised.
-
-Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000420-GPOS-00186, SRG-OS-000424-GPOS-00188&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000068</xccdf:ident>
- <xccdf:fixtext fixref="F-33171r568328_fix">Configure the system to force a frequent session key renegotiation for SSH connections to the server by add or modifying the following line in the "/etc/ssh/sshd_config" file:
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230542r792957_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040262</xccdf:version>
+ <xccdf:title>RHEL 8 must not accept router advertisements on all IPv6 interfaces by default.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.
-RekeyLimit 1G 1h
+An illicit router advertisement message could result in a man-in-the-middle attack.
-Restart the SSH daemon for the settings to take effect.
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf
+/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
-$ sudo systemctl restart sshd.service</xccdf:fixtext>
- <xccdf:fix id="F-33171r568328_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:343" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230531">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230531r627750_rule" weight="10.0" severity="high">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040172</xccdf:version>
- <xccdf:title>The systemd Ctrl-Alt-Delete burst key sequence in RHEL 8 must be disabled.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;A locally logged-on user who presses Ctrl-Alt-Delete when at the console can reboot the system. If accidentally pressed, as could happen in the case of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In a graphical user environment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is reduced because the user will be prompted before any action is taken.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9332,74 +8770,30 @@ $ sudo systemctl restart sshd.service</xccdf:fixtext>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33175r619890_fix">Configure the system to disable the CtrlAltDelBurstAction by added or modifying the following line in the "/etc/systemd/system.conf" configuration file:
+ <xccdf:fixtext fixref="F-33186r792956_fix">Configure RHEL 8 to not accept router advertisements on all IPv6 interfaces by default unless the system is a router.
-CtrlAltDelBurstAction=none
+Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
-Reload the daemon for this change to take effect.
+net.ipv6.conf.default.accept_ra=0
-$ sudo systemctl daemon-reload</xccdf:fixtext>
- <xccdf:fix id="F-33175r619890_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:345" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230533">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230533r627750_rule" weight="10.0" severity="high">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040190</xccdf:version>
- <xccdf:title>The Trivial File Transfer Protocol (TFTP) server package must not be installed if not required for RHEL 8 operational support.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;If TFTP is required for operational support (such as the transmission of router configurations) its use must be documented with the Information System Security Officer (ISSO), restricted to only authorized personnel, and have access control rules established.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33177r568346_fix">Remove the TFTP package from the system with the following command:
+Load settings from all system configuration files with the following command:
-$ sudo yum remove tftp-server</xccdf:fixtext>
- <xccdf:fix id="F-33177r568346_fix" />
+$ sudo sysctl --system</xccdf:fixtext>
+ <xccdf:fix id="F-33186r792956_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:346" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:355" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230534">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230543">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230534r627750_rule" weight="10.0" severity="high">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040200</xccdf:version>
- <xccdf:title>The root account must be the only account having unrestricted access to the RHEL 8 system.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;If an account other than root also has a User Identifier (UID) of "0", it has root authority, giving that account unrestricted access to the entire operating system. Multiple accounts with a UID of "0" afford an opportunity for potential intruders to guess a password for a privileged account.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33178r568349_fix">Change the UID of any account on the system, other than root, that has a UID of "0".
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230543r792960_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040270</xccdf:version>
+ <xccdf:title>RHEL 8 must not allow interfaces to perform Internet Control Message Protocol (ICMP) redirects by default.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.
-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 of greater than "1000" that has not already been assigned.</xccdf:fixtext>
- <xccdf:fix id="F-33178r568349_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:347" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230535">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230535r792936_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040210</xccdf:version>
- <xccdf:title>RHEL 8 must prevent IPv6 Internet Control Message Protocol (ICMP) redirect messages from being accepted.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.
+There are notable differences between Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). There is only a directive to disable sending of IPv4 redirected packets. Refer to RFC4294 for an explanation of "IPv6 Node Requirements", which resulted in this difference between IPv4 and IPv6.
The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
/etc/sysctl.d/*.conf
@@ -9418,30 +8812,28 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33179r792935_fix">Configure RHEL 8 to prevent IPv6 ICMP redirect messages from being accepted.
+ <xccdf:fixtext fixref="F-33187r792959_fix">Configure RHEL 8 to not allow interfaces to perform Internet Protocol version 4 (IPv4) ICMP redirects by default.
Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
-net.ipv6.conf.default.accept_redirects = 0
+net.ipv4.conf.default.send_redirects = 0
Load settings from all system configuration files with the following command:
$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33179r792935_fix" />
+ <xccdf:fix id="F-33187r792959_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:348" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:356" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230536">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230544">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230536r792939_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040220</xccdf:version>
- <xccdf:title>RHEL 8 must not send Internet Control Message Protocol (ICMP) redirects.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.
-
-There are notable differences between Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). There is only a directive to disable sending of IPv4 redirected packets. Refer to RFC4294 for an explanation of "IPv6 Node Requirements", which resulted in this difference between IPv4 and IPv6.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230544r792963_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040280</xccdf:version>
+ <xccdf:title>RHEL 8 must ignore IPv6 Internet Control Message Protocol (ICMP) redirect messages.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.
The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
/etc/sysctl.d/*.conf
@@ -9460,30 +8852,29 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33180r792938_fix">Configure RHEL 8 to not allow interfaces to perform IPv4 ICMP redirects.
+ <xccdf:fixtext fixref="F-33188r792962_fix">Configure RHEL 8 to ignore IPv6 ICMP redirect messages.
Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
-net.ipv4.conf.all.send_redirects=0
+net.ipv6.conf.all.accept_redirects = 0
Load settings from all system configuration files with the following command:
$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33180r792938_fix" />
+ <xccdf:fix id="F-33188r792962_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:349" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:357" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230537">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230545">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230537r792942_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040230</xccdf:version>
- <xccdf:title>RHEL 8 must not respond to Internet Control Message Protocol (ICMP) echoes sent to a broadcast address.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Responding to broadcast ICMP echoes facilitates network mapping and provides a vector for amplification attacks.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230545r792966_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040281</xccdf:version>
+ <xccdf:title>RHEL 8 must disable access to network bpf syscall from unprivileged processes.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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.
-There are notable differences between Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). IPv6 does not implement the same method of broadcast as IPv4. Instead, IPv6 uses multicast addressing to the all-hosts multicast group. Refer to RFC4294 for an explanation of "IPv6 Node Requirements", which resulted in this difference between IPv4 and IPv6.
The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
/etc/sysctl.d/*.conf
/run/sysctl.d/*.conf
@@ -9501,28 +8892,26 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33181r792941_fix">Configure RHEL 8 to not respond to IPv4 ICMP echoes sent to a broadcast address.
-
-Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
+ <xccdf:fixtext fixref="F-33189r792965_fix">Configure RHEL 8 to prevent privilege escalation thru the kernel by disabling access to the bpf syscall by adding the following line to a file, which begins with "99-", in the "/etc/sysctl.d" directory:
-net.ipv4.icmp_echo_ignore_broadcasts=1
+kernel.unprivileged_bpf_disabled = 1
-Load settings from all system configuration files with the following command:
+The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command:
$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33181r792941_fix" />
+ <xccdf:fix id="F-33189r792965_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:350" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:358" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230538">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230546">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230538r792945_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040240</xccdf:version>
- <xccdf:title>RHEL 8 must not forward IPv6 source-routed packets.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when forwarding is enabled and the system is functioning as a router.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230546r792969_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040282</xccdf:version>
+ <xccdf:title>RHEL 8 must restrict usage of ptrace to descendant processes.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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 sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
/etc/sysctl.d/*.conf
@@ -9541,28 +8930,26 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33182r792944_fix">Configure RHEL 8 to not forward IPv6 source-routed packets.
-
-Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
+ <xccdf:fixtext fixref="F-33190r792968_fix">Configure RHEL 8 to restrict usage of ptrace to descendant processes by adding the following line to a file, which begins with "99-", in the "/etc/sysctl.d" directory:
-net.ipv6.conf.all.accept_source_route=0
+kernel.yama.ptrace_scope = 1
-Load settings from all system configuration files with the following command:
+The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command:
$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33182r792944_fix" />
+ <xccdf:fix id="F-33190r792968_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:351" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:359" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230539">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230547">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230539r792948_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040250</xccdf:version>
- <xccdf:title>RHEL 8 must not forward IPv6 source-routed packets by default.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when forwarding is enabled and the system is functioning as a router.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230547r792972_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040283</xccdf:version>
+ <xccdf:title>RHEL 8 must restrict exposed kernel pointer addresses access.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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 sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
/etc/sysctl.d/*.conf
@@ -9581,28 +8968,26 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33183r792947_fix">Configure RHEL 8 to not forward IPv6 source-routed packets by default.
+ <xccdf:fixtext fixref="F-33191r792971_fix">Configure RHEL 8 to restrict exposed kernel pointer addresses access by adding the following line to a file, which begins with "99-", in the "/etc/sysctl.d" directory:
-Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
+kernel.kptr_restrict = 1
-net.ipv6.conf.default.accept_source_route=0
-
-Load settings from all system configuration files with the following command:
+The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command:
$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33183r792947_fix" />
+ <xccdf:fix id="F-33191r792971_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:352" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:360" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230540">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230548">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230540r792951_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040260</xccdf:version>
- <xccdf:title>RHEL 8 must not enable IPv6 packet forwarding unless the system is a router.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230548r792975_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040284</xccdf:version>
+ <xccdf:title>RHEL 8 must disable the use of user namespaces.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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 sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
/etc/sysctl.d/*.conf
@@ -9621,30 +9006,28 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33184r792950_fix">Configure RHEL 8 to not allow IPv6 packet forwarding, unless the system is a router.
+ <xccdf:fixtext fixref="F-33192r792974_fix">Configure RHEL 8 to disable the use of user namespaces by adding the following line to a file, which begins with "99-", in the "/etc/sysctl.d" directory:
-Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
+Note: User namespaces are used primarily for Linux containers. If containers are in use, this requirement is not applicable.
-net.ipv6.conf.all.forwarding=0
+user.max_user_namespaces = 0
-Load settings from all system configuration files with the following command:
+The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command:
$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33184r792950_fix" />
+ <xccdf:fix id="F-33192r792974_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:353" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:361" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230541">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230549">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230541r792954_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040261</xccdf:version>
- <xccdf:title>RHEL 8 must not accept router advertisements on all IPv6 interfaces.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.
-
-An illicit router advertisement message could result in a man-in-the-middle attack.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230549r792978_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040285</xccdf:version>
+ <xccdf:title>RHEL 8 must use reverse path filtering on all IPv4 interfaces.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;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 sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
/etc/sysctl.d/*.conf
@@ -9663,40 +9046,26 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33185r792953_fix">Configure RHEL 8 to not accept router advertisements on all IPv6 interfaces unless the system is a router.
-
-Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
+ <xccdf:fixtext fixref="F-33193r792977_fix">Configure RHEL 8 to use reverse path filtering on all IPv4 interfaces by adding the following line to a file, which begins with "99-", in the "/etc/sysctl.d" directory:
-net.ipv6.conf.all.accept_ra=0
+net.ipv4.conf.all.rp_filter = 1
-Load settings from all system configuration files with the following command:
+The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command:
$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33185r792953_fix" />
+ <xccdf:fix id="F-33193r792977_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:354" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:362" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230542">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230550">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230542r792957_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040262</xccdf:version>
- <xccdf:title>RHEL 8 must not accept router advertisements on all IPv6 interfaces by default.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.
-
-An illicit router advertisement message could result in a man-in-the-middle attack.
-
-The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf
-/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
-
-Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230550r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040290</xccdf:version>
+ <xccdf:title>RHEL 8 must be configured to prevent unrestricted mail relaying.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending spam or other unauthorized activity.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9705,40 +9074,26 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33186r792956_fix">Configure RHEL 8 to not accept router advertisements on all IPv6 interfaces by default unless the system is a router.
-
-Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
-
-net.ipv6.conf.default.accept_ra=0
-
-Load settings from all system configuration files with the following command:
+ <xccdf:fixtext fixref="F-33194r568397_fix">If "postfix" is installed, modify the "/etc/postfix/main.cf" file to restrict client connections to the local network with the following command:
-$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33186r792956_fix" />
+$ sudo postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject'</xccdf:fixtext>
+ <xccdf:fix id="F-33194r568397_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:355" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:363" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230543">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230555">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230543r792960_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040270</xccdf:version>
- <xccdf:title>RHEL 8 must not allow interfaces to perform Internet Control Message Protocol (ICMP) redirects by default.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.
-
-There are notable differences between Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). There is only a directive to disable sending of IPv4 redirected packets. Refer to RFC4294 for an explanation of "IPv6 Node Requirements", which resulted in this difference between IPv4 and IPv6.
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230555r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040340</xccdf:version>
+ <xccdf:title>RHEL 8 remote X connections for interactive users must be disabled unless to fulfill documented and validated mission requirements.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;The security risk of using X11 forwarding is that the client's X11 display server may be exposed to attack when the SSH client requests forwarding. A system administrator may have a stance in which they want to protect clients that may expose themselves to attack by unwittingly requesting X11 forwarding, which can warrant a "no" setting.
-The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf
-/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
+X11 forwarding should be enabled with caution. Users with the ability to bypass file permissions on the remote host (for the user's X11 authorization database) can access the local X11 display through the forwarded connection. An attacker may then be able to perform activities such as keystroke monitoring if the ForwardX11Trusted option is also enabled.
-Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+If X11 services are not required for the system's intended function, they should be disabled or restricted as appropriate to the systems needs.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9747,38 +9102,26 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33187r792959_fix">Configure RHEL 8 to not allow interfaces to perform Internet Protocol version 4 (IPv4) ICMP redirects by default.
-
-Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
+ <xccdf:fixtext fixref="F-33199r568412_fix">Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "X11Forwarding" keyword and set its value to "no" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
-net.ipv4.conf.default.send_redirects = 0
+X11Forwarding no
-Load settings from all system configuration files with the following command:
+The SSH service must be restarted for changes to take effect:
-$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33187r792959_fix" />
+$ sudo systemctl restart sshd</xccdf:fixtext>
+ <xccdf:fix id="F-33199r568412_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:356" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:364" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230544">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230556">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230544r792963_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040280</xccdf:version>
- <xccdf:title>RHEL 8 must ignore IPv6 Internet Control Message Protocol (ICMP) redirect messages.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.
-
-The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf
-/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
-
-Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230556r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040341</xccdf:version>
+ <xccdf:title>The RHEL 8 SSH daemon must prevent remote hosts from connecting to the proxy display.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;When X11 forwarding is enabled, there may be additional exposure to the server and client displays if the sshd proxy display is configured to listen on the wildcard address. By default, sshd binds the forwarding server to the loopback address and sets the hostname part of the DIPSLAY environment variable to localhost. This prevents remote hosts from connecting to the proxy display.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9787,38 +9130,24 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33188r792962_fix">Configure RHEL 8 to ignore IPv6 ICMP redirect messages.
-
-Add or edit the following line in a system configuration file, which begins with "99-", in the "/etc/sysctl.d/" directory:
-
-net.ipv6.conf.all.accept_redirects = 0
+ <xccdf:fixtext fixref="F-33200r568415_fix">Configure the SSH daemon to prevent remote hosts from connecting to the proxy display.
-Load settings from all system configuration files with the following command:
+Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "X11UseLocalhost" keyword and set its value to "yes" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
-$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33188r792962_fix" />
+X11UseLocalhost yes</xccdf:fixtext>
+ <xccdf:fix id="F-33200r568415_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:357" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:365" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230545">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230557">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230545r792966_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040281</xccdf:version>
- <xccdf:title>RHEL 8 must disable access to network bpf syscall from unprivileged processes.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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 sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf
-/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
-
-Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230557r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040350</xccdf:version>
+ <xccdf:title>If the Trivial File Transfer Protocol (TFTP) server is required, the RHEL 8 TFTP daemon must be configured to operate in secure mode.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9827,36 +9156,22 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33189r792965_fix">Configure RHEL 8 to prevent privilege escalation thru the kernel by disabling access to the bpf syscall by adding the following line to a file, which begins with "99-", in the "/etc/sysctl.d" directory:
-
-kernel.unprivileged_bpf_disabled = 1
-
-The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command:
+ <xccdf:fixtext fixref="F-33201r568418_fix">Configure the TFTP daemon to operate in secure mode by adding the following line to "/etc/xinetd.d/tftp" (or modify the line to have the required value):
-$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33189r792965_fix" />
+server_args = -s /var/lib/tftpboot</xccdf:fixtext>
+ <xccdf:fix id="F-33201r568418_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:358" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:366" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230546">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230558">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230546r792969_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040282</xccdf:version>
- <xccdf:title>RHEL 8 must restrict usage of ptrace to descendant processes.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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 sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf
-/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
-
-Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230558r627750_rule" weight="10.0" severity="high">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040360</xccdf:version>
+ <xccdf:title>A File Transfer Protocol (FTP) server package must not be installed unless mission essential on RHEL 8.</xccdf:title>
+ <xccdf:description>&lt;VulnDiscussion&gt;The FTP service provides an unencrypted remote access that does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to log on using this service, the privileged user password could be compromised. SSH or other encrypted file transfer methods must be used in place of this service.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9865,36 +9180,26 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
<xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33190r792968_fix">Configure RHEL 8 to restrict usage of ptrace to descendant processes by adding the following line to a file, which begins with "99-", in the "/etc/sysctl.d" directory:
-
-kernel.yama.ptrace_scope = 1
-
-The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command:
+ <xccdf:fixtext fixref="F-33202r568421_fix">Document the FTP server package with the ISSO as an operational requirement or remove it from the system with the following command:
-$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33190r792968_fix" />
+$ sudo yum remove vsftpd</xccdf:fixtext>
+ <xccdf:fix id="F-33202r568421_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:359" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:367" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230547">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230559">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230547r792972_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040283</xccdf:version>
- <xccdf:title>RHEL 8 must restrict exposed kernel pointer addresses access.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230559r646887_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040370</xccdf:version>
+ <xccdf:title>The gssproxy package must not be installed unless mission essential on RHEL 8.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;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 sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf
-/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
+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).
-Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The gssproxy package is a proxy for GSS API credential handling and could expose secrets on some networks. It is not needed for normal function of the OS.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -9902,267 +9207,27 @@ Based on the information above, if a configuration file that begins with "99-" i
<dc:subject>Red Hat Enterprise Linux 8</dc:subject>
<dc:identifier>2921</dc:identifier>
</xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33191r792971_fix">Configure RHEL 8 to restrict exposed kernel pointer addresses access by adding the following line to a file, which begins with "99-", in the "/etc/sysctl.d" directory:
-
-kernel.kptr_restrict = 1
-
-The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command:
+ <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
+ <xccdf:fixtext fixref="F-33203r568424_fix">Document the gssproxy package with the ISSO as an operational requirement or remove it from the system with the following command:
-$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33191r792971_fix" />
+$ sudo yum remove gssproxy</xccdf:fixtext>
+ <xccdf:fix id="F-33203r568424_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:360" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:368" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230548">
+ <xccdf:Group id="xccdf_mil.disa.stig_group_V-230560">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230548r792975_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040284</xccdf:version>
- <xccdf:title>RHEL 8 must disable the use of user namespaces.</xccdf:title>
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230560r627750_rule" weight="10.0" severity="medium">
+ <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040380</xccdf:version>
+ <xccdf:title>The iprutils package must not be installed unless mission essential on RHEL 8.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;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 sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf
-/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
+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).
-Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33192r792974_fix">Configure RHEL 8 to disable the use of user namespaces by adding the following line to a file, which begins with "99-", in the "/etc/sysctl.d" directory:
-
-Note: User namespaces are used primarily for Linux containers. If containers are in use, this requirement is not applicable.
-
-user.max_user_namespaces = 0
-
-The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command:
-
-$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33192r792974_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:361" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230549">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230549r792978_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040285</xccdf:version>
- <xccdf:title>RHEL 8 must use reverse path filtering on all IPv4 interfaces.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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 sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf
-/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
-
-Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33193r792977_fix">Configure RHEL 8 to use reverse path filtering on all IPv4 interfaces by adding the following line to a file, which begins with "99-", in the "/etc/sysctl.d" directory:
-
-net.ipv4.conf.all.rp_filter = 1
-
-The system configuration files need to be reloaded for the changes to take effect. To reload the contents of the files, run the following command:
-
-$ sudo sysctl --system</xccdf:fixtext>
- <xccdf:fix id="F-33193r792977_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:362" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230550">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230550r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040290</xccdf:version>
- <xccdf:title>RHEL 8 must be configured to prevent unrestricted mail relaying.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending spam or other unauthorized activity.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33194r568397_fix">If "postfix" is installed, 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'</xccdf:fixtext>
- <xccdf:fix id="F-33194r568397_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:363" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230555">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230555r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040340</xccdf:version>
- <xccdf:title>RHEL 8 remote X connections for interactive users must be disabled unless to fulfill documented and validated mission requirements.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;The security risk of using X11 forwarding is that the client's X11 display server may be exposed to attack when the SSH client requests forwarding. A system administrator may have a stance in which they want to protect clients that may expose themselves to attack by unwittingly requesting X11 forwarding, which can warrant a "no" setting.
-
-X11 forwarding should be enabled with caution. Users with the ability to bypass file permissions on the remote host (for the user's X11 authorization database) can access the local X11 display through the forwarded connection. An attacker may then be able to perform activities such as keystroke monitoring if the ForwardX11Trusted option is also enabled.
-
-If X11 services are not required for the system's intended function, they should be disabled or restricted as appropriate to the systems needs.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33199r568412_fix">Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "X11Forwarding" keyword and set its value to "no" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
-
-X11Forwarding no
-
-The SSH service must be restarted for changes to take effect:
-
-$ sudo systemctl restart sshd</xccdf:fixtext>
- <xccdf:fix id="F-33199r568412_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:364" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230556">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230556r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040341</xccdf:version>
- <xccdf:title>The RHEL 8 SSH daemon must prevent remote hosts from connecting to the proxy display.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;When X11 forwarding is enabled, there may be additional exposure to the server and client displays if the sshd proxy display is configured to listen on the wildcard address. By default, sshd binds the forwarding server to the loopback address and sets the hostname part of the DIPSLAY environment variable to localhost. This prevents remote hosts from connecting to the proxy display.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33200r568415_fix">Configure the SSH daemon to prevent remote hosts from connecting to the proxy display.
-
-Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "X11UseLocalhost" keyword and set its value to "yes" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
-
-X11UseLocalhost yes</xccdf:fixtext>
- <xccdf:fix id="F-33200r568415_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:365" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230557">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230557r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040350</xccdf:version>
- <xccdf:title>If the Trivial File Transfer Protocol (TFTP) server is required, the RHEL 8 TFTP daemon must be configured to operate in secure mode.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33201r568418_fix">Configure the TFTP daemon to operate in secure mode by adding the following line to "/etc/xinetd.d/tftp" (or modify the line to have the required value):
-
-server_args = -s /var/lib/tftpboot</xccdf:fixtext>
- <xccdf:fix id="F-33201r568418_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:366" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230558">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230558r627750_rule" weight="10.0" severity="high">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040360</xccdf:version>
- <xccdf:title>A File Transfer Protocol (FTP) server package must not be installed unless mission essential on RHEL 8.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;The FTP service provides an unencrypted remote access that does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to log on using this service, the privileged user password could be compromised. SSH or other encrypted file transfer methods must be used in place of this service.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000366</xccdf:ident>
- <xccdf:fixtext fixref="F-33202r568421_fix">Document the FTP server package with the ISSO as an operational requirement or remove it from the system with the following command:
-
-$ sudo yum remove vsftpd</xccdf:fixtext>
- <xccdf:fix id="F-33202r568421_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:367" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230559">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230559r646887_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040370</xccdf:version>
- <xccdf:title>The gssproxy package must not be installed unless mission essential on RHEL 8.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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).
-
-The gssproxy package is a proxy for GSS API credential handling and could expose secrets on some networks. It is not needed for normal function of the OS.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
- <xccdf:reference>
- <dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
- <dc:publisher>DISA</dc:publisher>
- <dc:type>DPMS Target</dc:type>
- <dc:subject>Red Hat Enterprise Linux 8</dc:subject>
- <dc:identifier>2921</dc:identifier>
- </xccdf:reference>
- <xccdf:ident system="http://cyber.mil/cci">CCI-000381</xccdf:ident>
- <xccdf:fixtext fixref="F-33203r568424_fix">Document the gssproxy package with the ISSO as an operational requirement or remove it from the system with the following command:
-
-$ sudo yum remove gssproxy</xccdf:fixtext>
- <xccdf:fix id="F-33203r568424_fix" />
- <xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:368" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
- </xccdf:check>
- </xccdf:Rule>
- </xccdf:Group>
- <xccdf:Group id="xccdf_mil.disa.stig_group_V-230560">
- <xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
- <xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-230560r627750_rule" weight="10.0" severity="medium">
- <xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-040380</xccdf:version>
- <xccdf:title>The iprutils package must not be installed unless mission essential on RHEL 8.</xccdf:title>
- <xccdf:description>&lt;VulnDiscussion&gt;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).
-
-The iprutils package provides a suite of utilities to manage and configure SCSI devices supported by the ipr SCSI storage device driver.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
+The iprutils package provides a suite of utilities to manage and configure SCSI devices supported by the ipr SCSI storage device driver.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</xccdf:description>
<xccdf:reference>
<dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title>
<dc:publisher>DISA</dc:publisher>
@@ -10176,7 +9241,7 @@ The iprutils package provides a suite of utilities to manage and configure SCSI
$ sudo yum remove iprutils</xccdf:fixtext>
<xccdf:fix id="F-33204r568427_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:369" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:369" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -10204,7 +9269,7 @@ The tuned package contains a daemon that tunes the system settings dynamically.
$ sudo yum remove tuned</xccdf:fixtext>
<xccdf:fix id="F-33205r568430_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:370" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:370" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -10234,7 +9299,7 @@ FIPS 140-2 is the current standard for validating that mechanisms used to access
$ sudo yum remove krb5-server</xccdf:fixtext>
<xccdf:fix id="F-40822r646889_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:413" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:413" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
@@ -10258,14 +9323,14 @@ ALL ALL=(ALL) ALL
ALL ALL=(ALL:ALL) ALL</xccdf:fixtext>
<xccdf:fix id="F-40823r646892_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:414" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:414" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-237642">
<xccdf:title>SRG-OS-000480-GPOS-00227</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-237642r646896_rule" weight="10.0" severity="medium">
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-237642r809326_rule" weight="10.0" severity="medium">
<xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-010383</xccdf:version>
<xccdf:title>RHEL 8 must use the invoking user's password for privilege escalation when using "sudo".</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;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. If the rootpw, targetpw, or runaspw flags are defined and not disabled, by default the operating system will prompt the invoking user for the "root" user password.
@@ -10284,14 +9349,14 @@ Defaults !rootpw
Defaults !runaspw</xccdf:fixtext>
<xccdf:fix id="F-40824r646895_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:415" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:415" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
<xccdf:Group id="xccdf_mil.disa.stig_group_V-237643">
<xccdf:title>SRG-OS-000373-GPOS-00156</xccdf:title>
<xccdf:description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</xccdf:description>
- <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-237643r792980_rule" weight="10.0" severity="medium">
+ <xccdf:Rule id="xccdf_mil.disa.stig_rule_SV-237643r809328_rule" weight="10.0" severity="medium">
<xccdf:version update="http://iase.disa.mil/stigs">RHEL-08-010384</xccdf:version>
<xccdf:title>RHEL 8 must require re-authentication when using the "sudo" command.</xccdf:title>
<xccdf:description>&lt;VulnDiscussion&gt;Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
@@ -10316,18 +9381,18 @@ Defaults timestamp_timeout=[value]
Note: The "[value]" must be a number that is greater than or equal to "0".</xccdf:fixtext>
<xccdf:fix id="F-40825r646898_fix" />
<xccdf:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
- <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:416" href="U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" />
+ <xccdf:check-content-ref name="oval:mil.disa.stig.rhel8:def:416" href="U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" />
</xccdf:check>
</xccdf:Rule>
</xccdf:Group>
</xccdf:Benchmark>
</component>
- <component id="scap_mil.disa.stig_comp_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-oval.xml" timestamp="2021-10-04T21:38:10">
+ <component id="scap_mil.disa.stig_comp_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-oval.xml" timestamp="2022-01-03T11:44:34">
<oval_definitions xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5" xmlns:oval="http://oval.mitre.org/XMLSchema/oval-common-5">
<generator>
<oval:product_name>repotool</oval:product_name>
<oval:schema_version>5.10</oval:schema_version>
- <oval:timestamp>2021-10-04T21:38:10</oval:timestamp>
+ <oval:timestamp>2022-01-03T11:44:33</oval:timestamp>
</generator>
<definitions>
<definition class="compliance" id="oval:mil.disa.stig.rhel8:def:98" version="1">
@@ -10358,7 +9423,7 @@ Note: The "[value]" must be a number that is greater than or equal to "0".</xccd
<criterion comment="The openssh package is installed" test_ref="oval:mil.disa.stig.rhel8:tst:9900" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:100" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:100" version="3">
<metadata>
<title>RHEL-08-010000 - RHEL 8 must be a vendor-supported release.</title>
<affected family="unix">
@@ -10369,8 +9434,9 @@ Note: The "[value]" must be a number that is greater than or equal to "0".</xccd
Red Hat offers the Extended Update Support (EUS) ad-on to a Red Hat Enterprise Linux subscription, for a fee, for those customers who wish to standardize on a specific minor release for an extended period. The RHEL 8 minor releases eligible for EUS are 8.1, 8.2, 8.4, 8.6, and 8.8. Each RHEL 8 EUS stream is available for 24 months from the availability of the minor release. RHEL 8.10 will be the final minor release ovaerall. For more details on the Red Hat Enterprise Linux Life Cycle please visit https://access.redhat.com/support/policy/updates/errata.</description>
</metadata>
- <criteria>
+ <criteria operator="OR">
<criterion comment="The RHEL 8 minor version is supported." test_ref="oval:mil.disa.stig.rhel8:tst:10000" />
+ <criterion comment="The RHEL 8 minor version is supported." test_ref="oval:mil.disa.stig.rhel8:tst:10001" />
</criteria>
</definition>
<definition class="compliance" id="oval:mil.disa.stig.rhel8:def:101" version="1">
@@ -10420,9 +9486,9 @@ Passwords need to be protected at all times, and encryption is the standard meth
<criterion comment="No active password hash in /etc/shadow has a prefix other than '$6'." test_ref="oval:mil.disa.stig.rhel8:tst:10400" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:105" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:105" version="3">
<metadata>
- <title>RHEL-08-010130 - The RHEL 8 password-auth file must be configured to use a sufficient number of hashing rounds.</title>
+ <title>RHEL-08-010130 - The RHEL 8 shadow password suite must be configured to use a sufficient number of hashing rounds.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
@@ -10431,7 +9497,8 @@ Passwords need to be protected at all times, and encryption is the standard meth
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.</description>
</metadata>
<criteria>
- <criterion comment="Check the file /etc/pam.d/password-auth to see if the password section for pam_unix.so sets rounds to a value no lower than 5000." test_ref="oval:mil.disa.stig.rhel8:tst:10500" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:10500" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:10501" />
</criteria>
</definition>
<definition class="compliance" id="oval:mil.disa.stig.rhel8:def:106" version="1">
@@ -10506,2717 +9573,2410 @@ RHEL 8 systems utilizing encryption are required to use FIPS-compliant mechanism
The key derivation function (KDF) in Kerberos is not FIPS compatible. Ensuring the system does not have any keytab files present prevents system daemons from using Kerberos for authentication. A keytab is a file containing pairs of Kerberos principals and encrypted keys.
-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.</description>
- </metadata>
- <criteria operator="OR">
- <criterion comment="/etc/*.keytab does not exist." test_ref="oval:mil.disa.stig.rhel8:tst:11000" />
- <criterion comment="krb5-server-1.17-18.el8.x86_64 or newer is installed." test_ref="oval:mil.disa.stig.rhel8:tst:11001" />
- <criterion comment="krb5-workstation-1.17-18.el8.x86_64 or newer is installed." test_ref="oval:mil.disa.stig.rhel8:tst:11002" />
- </criteria>
- </definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:111" version="2">
- <metadata>
- <title>RHEL-08-010162 - The krb5-workstation package must not be installed on RHEL 8.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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.
-
-RHEL 8 systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
-
-Currently, Kerberos does not utilize FIPS 140-2 cryptography.
-
-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.</description>
- </metadata>
- <criteria operator="OR">
- <criterion comment="package krb5-workstation is not installed" test_ref="oval:mil.disa.stig.rhel8:tst:11100" />
- <criterion comment="package krb5-workstation-1.17-18 or newer is installed" test_ref="oval:mil.disa.stig.rhel8:tst:11101" />
- <criterion comment="package krb5-server is installed" test_ref="oval:mil.disa.stig.rhel8:tst:11102" />
- </criteria>
- </definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:112" version="1">
- <metadata>
- <title>RHEL-08-010171 - RHEL 8 must have the policycoreutils package installed.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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.
-
-Policycoreutils contains the policy core utilities that are required for basic operation of an SELinux-enabled system. These utilities include load_policy to load SELinux policies, setfile to label filesystems, newrole to switch roles, and run_init to run /etc/init.d scripts in the proper context.</description>
- </metadata>
- <criteria>
- <criterion comment="package policycoreutils is installed" test_ref="oval:mil.disa.stig.rhel8:tst:11200" />
- </criteria>
- </definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:115" version="3">
- <metadata>
- <title>RHEL-08-010200 - RHEL 8 must be configured so that all network connections associated with SSH traffic are terminated at the end of the session or after 10 minutes of inactivity, except to fulfill documented and validated mission requirements.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>Terminating an idle SSH 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 SSH 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.
-
-RHEL 8 utilizes /etc/ssh/sshd_config for configurations of OpenSSH. Within the sshd_config the product of the values of "ClientAliveInterval" and "ClientAliveCountMax" are used to establish the inactivity threshold. The "ClientAliveInterval" is a timeout interval in seconds after which if no data has been received from the client, sshd will send a message through the encrypted channel to request a response from the client. The "ClientAliveCountMax" is the number of client alive messages that may be sent without sshd receiving any messages back from the client. If this threshold is met, sshd will disconnect the client.</description>
- </metadata>
- <criteria operator="OR" comment="IF openssh is installed, THEN ClientAliveInterval * ClientAliveCountMax is less than or equal to 600.">
- <extend_definition comment="OpenSSH is installed" definition_ref="oval:mil.disa.stig.rhel8:def:99" negate="true" />
- <criterion comment="/etc/ssh/sshd_config:ClientAliveCountMax = 0." test_ref="oval:mil.disa.stig.rhel8:tst:11501" />
- </criteria>
- </definition>
- <definition id="oval:mil.disa.stig.rhel8:def:116" class="compliance" version="1">
- <metadata>
- <title>RHEL-08-010210 - The RHEL 8 /var/log/messages file must have mode 0640 or less permissive.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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 RHEL 8 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.</description>
- </metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:11600" comment="/var/log/messages file has mode 0640 or less permissive" />
- </criteria>
- </definition>
- <definition id="oval:mil.disa.stig.rhel8:def:117" class="compliance" version="1">
- <metadata>
- <title>RHEL-08-010220 - The RHEL 8 /var/log/messages file must be owned by root.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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 RHEL 8 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.</description>
- </metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:11700" comment="/var/log/messages file is owned by root" />
- </criteria>
- </definition>
- <definition id="oval:mil.disa.stig.rhel8:def:118" class="compliance" version="1">
- <metadata>
- <title>RHEL-08-010230 - The RHEL 8 /var/log/messages file must be group-owned by root.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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 RHEL 8 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.</description>
- </metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:11800" comment="/var/log/messages file is group-owned by root" />
- </criteria>
- </definition>
- <definition id="oval:mil.disa.stig.rhel8:def:119" class="compliance" version="1">
- <metadata>
- <title>RHEL-08-010240 - The RHEL 8 /var/log directory must have mode 0755 or less permissive.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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 RHEL 8 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.</description>
- </metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:11900" comment="/var/log directory has mode 0755 or less permissive." />
- </criteria>
- </definition>
- <definition id="oval:mil.disa.stig.rhel8:def:120" class="compliance" version="1">
- <metadata>
- <title>RHEL-08-010250 - The RHEL 8 /var/log directory must be owned by root.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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 RHEL 8 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.</description>
- </metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12000" comment="/var/log directory is owned by root." />
- </criteria>
- </definition>
- <definition id="oval:mil.disa.stig.rhel8:def:121" class="compliance" version="1">
- <metadata>
- <title>RHEL-08-010260 - The RHEL 8 /var/log directory must be group-owned by root.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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 RHEL 8 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.</description>
- </metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12100" comment="/var/log directory is group-owned by root." />
- </criteria>
- </definition>
- <definition id="oval:mil.disa.stig.rhel8:def:122" class="compliance" version="3">
- <metadata>
- <title>RHEL-08-010292 - RHEL 8 must ensure the SSH server uses strong entropy.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>The most important characteristic of a random number generator is its randomness, namely its ability to deliver random numbers that are impossible to predict. Entropy in computer security is associated with the unpredictability of a source of randomness. The random source with high entropy tends to achieve a uniform distribution of random values. Random number generators are one of the most important building blocks of cryptosystems.
-
-The SSH implementation in RHEL8 uses the OPENSSL library, which does not use high-entropy sources by default. By using the SSH_USE_STRONG_RNG environment variable the OPENSSL random generator is reseeded from /dev/random. This setting is not recommended on computers without the hardware random generator because insufficient entropy causes the connection to be blocked until enough entropy is available.</description>
- </metadata>
- <criteria operator="OR">
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:99" negate="true" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:18006" negate="true" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12200" />
- </criteria>
- </definition>
- <definition id="oval:mil.disa.stig.rhel8:def:123" class="compliance" version="1">
- <metadata>
- <title>RHEL-08-010294 - The RHEL 8 operating system must implement DoD-approved TLS encryption in the OpenSSL package.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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.
-
-RHEL 8 incorporates system-wide crypto policies by default. The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/openssl.config file.</description>
- </metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12300" />
- </criteria>
- </definition>
- <definition id="oval:mil.disa.stig.rhel8:def:124" class="compliance" version="2">
- <metadata>
- <title>RHEL-08-010300 - RHEL 8 system commands must have mode 755 or less permissive.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>If RHEL 8 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 RHEL 8 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals will be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</description>
- </metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12400" comment="System command files have mode 755 or less permissive" />
- </criteria>
- </definition>
- <definition id="oval:mil.disa.stig.rhel8:def:125" class="compliance" version="1">
- <metadata>
- <title>RHEL-08-010310 - RHEL 8 system commands must be owned by root.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>If RHEL 8 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 RHEL 8 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals will be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</description>
- </metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12500" comment="System command files are owned by root" />
- </criteria>
- </definition>
- <definition id="oval:mil.disa.stig.rhel8:def:126" class="compliance" version="1">
- <metadata>
- <title>RHEL-08-010320 - RHEL 8 system commands must be group-owned by root or a system account.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>If RHEL 8 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 RHEL 8 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals will be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</description>
- </metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12600" comment="System command files are group-owned by root" />
- </criteria>
- </definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:130" version="1">
- <metadata>
- <title>RHEL-08-010370 - RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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 verifies 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.</description>
- </metadata>
- <criteria>
- <criterion comment="Every /etc/yum.repos.d/*.repo:[{reponame}] has a gpgcheck entry set to 1." test_ref="oval:mil.disa.stig.rhel8:tst:13000" />
- <criterion comment="No /etc/yum.repos.d/*.repo:[{reponame}] has a gpgcheck entry set to 0." test_ref="oval:mil.disa.stig.rhel8:tst:13001" />
- </criteria>
- </definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:131" version="1">
- <metadata>
- <title>RHEL-08-010371 - RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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 verifies 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.</description>
- </metadata>
- <criteria>
- <criterion comment="/etc/dnf/dnf.conf:[main]localpkg_gpgcheck is set to true." test_ref="oval:mil.disa.stig.rhel8:tst:13100" />
- </criteria>
- </definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:132" version="3">
- <metadata>
- <title>RHEL-08-010372 - RHEL 8 must prevent the loading of a new kernel for later execution.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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.
-Disabling kexec_load prevents an unsigned kernel image (that could be a windows kernel or modified vulnerable kernel) from being loaded. Kexec can be used subvert the entire secureboot process and should be avoided at all costs especially since it can load unsigned kernel images.
-The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf
-/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
-Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.</description>
- </metadata>
- <criteria operator="AND">
- <criterion comment="kernel.kexec_load_disabled setting in kernel is 1" test_ref="oval:mil.disa.stig.rhel8:tst:13200" />
- <criterion comment="kernel.kexec_load_disabled setting in sysctl configuration files is set to 1, and nothing else" test_ref="oval:mil.disa.stig.rhel8:tst:13201" />
- </criteria>
- </definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:133" version="2">
- <metadata>
- <title>RHEL-08-010373 - RHEL 8 must enable kernel parameters to enforce discretionary access control on symlinks.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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.
-
-By enabling the fs.protected_symlinks kernel parameter, symbolic links are permitted to be followed only when outside a sticky world-writable directory, or when the UID of the link and follower match, or when the directory owner matches the symlink's owner. Disallowing such symlinks helps mitigate vulnerabilities based on insecure file system accessed by privileged programs, avoiding an exploitation vector exploiting unsafe use of open() or creat().
-
-The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a gien filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
-
-Based on the information above, if a configuration file begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configurationfile on the system.</description>
- </metadata>
- <criteria operator="AND">
- <criterion comment="fs.protected_symlinks setting in kernel is 1" test_ref="oval:mil.disa.stig.rhel8:tst:13300" />
- <criterion comment="fs.protected_symlinks setting in sysctl configuration files is set to 1, and nothing else" test_ref="oval:mil.disa.stig.rhel8:tst:13301" />
- </criteria>
- </definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:134" version="2">
- <metadata>
- <title>RHEL-08-010374 - RHEL 8 must enable kernel parameters to enforce discretionary access control on hardlinks.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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.
-
-By enabling the fs.protected_hardlinks kernel parameter, users can no longer create soft or hard links to files they do not own. Disallowing such hardlinks mitigate vulnerabilities based on insecure file system accessed by privileged programs, avoiding an exploitation vector exploiting unsafe use of open() or creat().
-
-The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf
-/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
-
-Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.</description>
- </metadata>
- <criteria operator="AND">
- <criterion comment="fs.protected_hardlinks setting in kernel is 1" test_ref="oval:mil.disa.stig.rhel8:tst:13400" />
- <criterion comment="fs.protected_hardlinks setting in sysctl configuration files is set to 1, and nothing else" test_ref="oval:mil.disa.stig.rhel8:tst:13401" />
- </criteria>
- </definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:135" version="2">
- <metadata>
- <title>RHEL-08-010375 - RHEL 8 must restrict access to the kernel message buffer.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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.
-
-Restricting access to the kernel message buffer limits access to only root. This prevents attackers from gaining additional system information as a non-privileged user.
-
-The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a gien filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
-
-Based on the information above, if a configuration file begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configurationfile on the system.</description>
- </metadata>
- <criteria operator="AND">
- <criterion comment="kernel.dmesg_restrict setting in kernel is 1" test_ref="oval:mil.disa.stig.rhel8:tst:13500" />
- <criterion comment="kernel.dmesg_restrict setting in sysctl configuration files is set to 1, and nothing else" test_ref="oval:mil.disa.stig.rhel8:tst:13501" />
- </criteria>
- </definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:136" version="2">
- <metadata>
- <title>RHEL-08-010376 - RHEL 8 must prevent kernel profiling by unprivileged users.</title>
- <affected family="unix">
- <platform>Red Hat Enterprise Linux 8</platform>
- </affected>
- <description>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.
-
-Setting the kernel.perf_event_paranoid kernel parameter to "2" prevents attackers from gaining additional system information as a non-privileged user.
-
-The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf
-/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
-
-Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.</description>
- </metadata>
- <criteria operator="AND">
- <criterion comment="kernel.perf_event_paranoid setting in kernel is 2" test_ref="oval:mil.disa.stig.rhel8:tst:13600" />
- <criterion comment="kernel.perf_event_paranoid setting in sysctl configuration files is set to 2, and nothing else" test_ref="oval:mil.disa.stig.rhel8:tst:13601" />
+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.</description>
+ </metadata>
+ <criteria operator="OR">
+ <criterion comment="/etc/*.keytab does not exist." test_ref="oval:mil.disa.stig.rhel8:tst:11000" />
+ <criterion comment="krb5-server-1.17-18.el8.x86_64 or newer is installed." test_ref="oval:mil.disa.stig.rhel8:tst:11001" />
+ <criterion comment="krb5-workstation-1.17-18.el8.x86_64 or newer is installed." test_ref="oval:mil.disa.stig.rhel8:tst:11002" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:137" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:111" version="2">
<metadata>
- <title>RHEL-08-010380 - RHEL 8 must require users to provide a password for privilege escalation.</title>
+ <title>RHEL-08-010162 - The krb5-workstation package must not be installed on RHEL 8.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without reauthentication, users may access resources or perform tasks for which they do not have authorization.
+ <description>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.
-When operating systems provide the capability to escalate a functional capability, it is critical the user reauthenticate.</description>
+RHEL 8 systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
+
+Currently, Kerberos does not utilize FIPS 140-2 cryptography.
+
+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.</description>
</metadata>
- <criteria>
- <criterion comment="'NOPASSWD' does not exist in /etc/sudoers" test_ref="oval:mil.disa.stig.rhel8:tst:13700" />
- <criterion comment="'NOPASSWD' does not exist in /etc/sudoers.d" test_ref="oval:mil.disa.stig.rhel8:tst:13701" />
+ <criteria operator="OR">
+ <criterion comment="package krb5-workstation is not installed" test_ref="oval:mil.disa.stig.rhel8:tst:11100" />
+ <criterion comment="package krb5-workstation-1.17-18 or newer is installed" test_ref="oval:mil.disa.stig.rhel8:tst:11101" />
+ <criterion comment="package krb5-server is installed" test_ref="oval:mil.disa.stig.rhel8:tst:11102" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:138" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:112" version="1">
<metadata>
- <title>RHEL-08-010381 - RHEL 8 must require users to reauthenticate for privilege escalation.</title>
+ <title>RHEL-08-010171 - RHEL 8 must have the policycoreutils package installed.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without reauthentication, users may access resources or perform tasks for which they do not have authorization.
+ <description>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.
-When operating systems provide the capability to escalate a functional capability, it is critical the user reauthenticate.</description>
+Policycoreutils contains the policy core utilities that are required for basic operation of an SELinux-enabled system. These utilities include load_policy to load SELinux policies, setfile to label filesystems, newrole to switch roles, and run_init to run /etc/init.d scripts in the proper context.</description>
</metadata>
<criteria>
- <criterion comment="'!authenticate' does not exist in /etc/sudoers" test_ref="oval:mil.disa.stig.rhel8:tst:13800" />
- <criterion comment="'!authenticate' does not exist in /etc/sudoers.d" test_ref="oval:mil.disa.stig.rhel8:tst:13801" />
+ <criterion comment="package policycoreutils is installed" test_ref="oval:mil.disa.stig.rhel8:tst:11200" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:139" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:115" version="3">
<metadata>
- <title>RHEL-08-010390 - RHEL 8 must have the packages required for multifactor authentication installed.</title>
+ <title>RHEL-08-010200 - RHEL 8 must be configured so that all network connections associated with SSH traffic are terminated at the end of the session or after 10 minutes of inactivity, except to fulfill documented and validated mission requirements.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Using an authentication device, such as a DoD Common Access Card (CAC) or token that is separate from the information system, ensures that even if the information system is compromised, credentials stored on the authentication device will not be affected.
-
-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 (PIV) card and the DoD CAC.
-
-A privileged account is defined as an information system account with authorizations of a privileged user.
+ <description>Terminating an idle SSH 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 SSH session will also free up resources committed by the managed network element.
-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.
+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.
-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).</description>
+RHEL 8 utilizes /etc/ssh/sshd_config for configurations of OpenSSH. Within the sshd_config the product of the values of "ClientAliveInterval" and "ClientAliveCountMax" are used to establish the inactivity threshold. The "ClientAliveInterval" is a timeout interval in seconds after which if no data has been received from the client, sshd will send a message through the encrypted channel to request a response from the client. The "ClientAliveCountMax" is the number of client alive messages that may be sent without sshd receiving any messages back from the client. If this threshold is met, sshd will disconnect the client.</description>
</metadata>
- <criteria>
- <criterion comment="package openssl-pkcs11 is installed" test_ref="oval:mil.disa.stig.rhel8:tst:13901" />
+ <criteria operator="OR" comment="IF openssh is installed, THEN ClientAliveInterval * ClientAliveCountMax is less than or equal to 600.">
+ <extend_definition comment="OpenSSH is installed" definition_ref="oval:mil.disa.stig.rhel8:def:99" negate="true" />
+ <criterion comment="/etc/ssh/sshd_config:ClientAliveCountMax = 0." test_ref="oval:mil.disa.stig.rhel8:tst:11501" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:145" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:116" class="compliance" version="1">
<metadata>
- <title>RHEL-08-010440 - YUM must remove all software components after updated versions have been installed on RHEL 8.</title>
+ <title>RHEL-08-010210 - The RHEL 8 /var/log/messages file must have mode 0640 or less permissive.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the information system.</description>
+ <description>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 RHEL 8 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.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:14500" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:11600" comment="/var/log/messages file has mode 0640 or less permissive" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:146" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:117" class="compliance" version="1">
<metadata>
- <title>RHEL-08-010450 - RHEL 8 must enable the SELinux targeted policy.</title>
+ <title>RHEL-08-010220 - The RHEL 8 /var/log/messages file must be owned by root.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
+ <description>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 RHEL 8 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.
-This requirement applies to operating systems performing security function verification/testing and/or systems and environments that require this functionality.</description>
+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.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:14600" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:11700" comment="/var/log/messages file is owned by root" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:147" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:118" class="compliance" version="1">
<metadata>
- <title>RHEL-08-010460 - There must be no shosts.equiv files on the RHEL 8 operating system.</title>
+ <title>RHEL-08-010230 - The RHEL 8 /var/log/messages file must be group-owned by root.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>The "shosts.equiv" files are used to configure host-based authentication for the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.</description>
+ <description>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 RHEL 8 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.</description>
</metadata>
<criteria>
- <criterion comment="There must be no shosts.equiv files on the system." test_ref="oval:mil.disa.stig.rhel8:tst:14700" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:11800" comment="/var/log/messages file is group-owned by root" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:148" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:119" class="compliance" version="1">
<metadata>
- <title>RHEL-08-010470 - There must be no .shosts files on the RHEL 8 operating system.</title>
+ <title>RHEL-08-010240 - The RHEL 8 /var/log directory must have mode 0755 or less permissive.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>The ".shosts" files are used to configure host-based authentication for individual users or the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.</description>
+ <description>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 RHEL 8 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.</description>
</metadata>
<criteria>
- <criterion comment="There must be no .shosts files on the system." test_ref="oval:mil.disa.stig.rhel8:tst:14800" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:11900" comment="/var/log directory has mode 0755 or less permissive." />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:149" version="5">
+ <definition id="oval:mil.disa.stig.rhel8:def:120" class="compliance" version="1">
<metadata>
- <title>RHEL-08-010480 - The RHEL 8 SSH public host key files must have mode 0644 or less permissive.</title>
+ <title>RHEL-08-010250 - The RHEL 8 /var/log directory must be owned by root.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>If a public host key file is modified by an unauthorized user, the SSH service may be compromised.</description>
+ <description>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 RHEL 8 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.</description>
</metadata>
- <criteria comment="OpenSSH-server is installed and public key files permissions are acceptable">
- <extend_definition comment="OpenSSH is installed" definition_ref="oval:mil.disa.stig.rhel8:def:324" />
- <criterion comment="The SUSE operating system SSH daemon public host key files have mode 0644 or less permissive" test_ref="oval:mil.disa.stig.rhel8:tst:14900" />
+ <criteria>
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12000" comment="/var/log directory is owned by root." />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:150" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:121" class="compliance" version="1">
<metadata>
- <title>RHEL-08-010490 - The RHEL 8 SSH private host key files must have mode 0600 or less permissive.</title>
+ <title>RHEL-08-010260 - The RHEL 8 /var/log directory must be group-owned by root.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>If an unauthorized user obtains the private SSH host key file, the host could be impersonated.</description>
+ <description>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 RHEL 8 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.</description>
</metadata>
- <criteria comment="OpenSSH is installed and check private key files permissions">
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:324" comment="openssh is installed" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:15000" />
+ <criteria>
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12100" comment="/var/log directory is group-owned by root." />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:151" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:122" class="compliance" version="3">
<metadata>
- <title>RHEL-08-010500 - The RHEL 8 SSH daemon must perform strict mode checking of home directory configuration files.</title>
+ <title>RHEL-08-010292 - RHEL 8 must ensure the SSH server uses strong entropy.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>If other users have access to modify user-specific SSH configuration files, they may be able to log on to the system as another user.</description>
+ <description>The most important characteristic of a random number generator is its randomness, namely its ability to deliver random numbers that are impossible to predict. Entropy in computer security is associated with the unpredictability of a source of randomness. The random source with high entropy tends to achieve a uniform distribution of random values. Random number generators are one of the most important building blocks of cryptosystems.
+
+The SSH implementation in RHEL8 uses the OPENSSL library, which does not use high-entropy sources by default. By using the SSH_USE_STRONG_RNG environment variable the OPENSSL random generator is reseeded from /dev/random. This setting is not recommended on computers without the hardware random generator because insufficient entropy causes the connection to be blocked until enough entropy is available.</description>
</metadata>
- <criteria comment="OpenSSH is installed AND StrictModes == yes">
- <extend_definition comment="OpenSSH is installed" definition_ref="oval:mil.disa.stig.rhel8:def:324" />
- <criterion comment="/etc/ssh/sshd_config:StrictModes == yes" test_ref="oval:mil.disa.stig.rhel8:tst:15100" />
+ <criteria operator="OR">
+ <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:99" negate="true" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:18006" negate="true" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12200" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:152" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:123" class="compliance" version="5">
<metadata>
- <title>RHEL-08-010510 - The RHEL 8 SSH daemon must not allow compression or must only allow compression after successful authentication.</title>
+ <title>RHEL-08-010294 - The RHEL 8 operating system must implement DoD-approved TLS encryption in the OpenSSL package.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the system from an unauthenticated connection, potentially with root privileges.</description>
+ <description>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.
+
+RHEL 8 incorporates system-wide crypto policies by default. The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/openssl.config file.</description>
</metadata>
- <criteria comment="IF SSH is installed, THEN verify Compression is set to no in /etc/ssh/sshd_config." operator="OR">
- <extend_definition comment="The openssh-server package is installed." definition_ref="oval:mil.disa.stig.rhel8:def:99" negate="true" />
- <criterion comment="/etc/ssh/sshd_config:Compression == no or Compression == delayed" test_ref="oval:mil.disa.stig.rhel8:tst:15200" />
+ <criteria>
+ <criteria operator="OR" comment="If crypto-policies is older than version 20210617, then MinProtocol = TLSv1.2 or TLSv1.3.">
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12300" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12301" />
+ </criteria>
+ <criteria operator="OR" comment="If crypto-policies is version 20210617 or newer, then TLS.MinProtocol = TLSv1.2 or TLSv1.3 and DTLS.MinProtocol = DLSv1.2 or DTLSv1.3">
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12300" negate="true" />
+ <criteria>
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12302" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12303" />
+ </criteria>
+ </criteria>
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:153" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:124" class="compliance" version="2">
<metadata>
- <title>RHEL-08-010520 - The RHEL 8 SSH daemon must not allow authentication using known hosts authentication.</title>
+ <title>RHEL-08-010300 - RHEL 8 system commands must have mode 755 or less permissive.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.</description>
+ <description>If RHEL 8 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 RHEL 8 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals will be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</description>
</metadata>
- <criteria comment="OpenSSH is installed AND IgnoreUserKnownHosts == yes">
- <extend_definition comment="OpenSSH is installed" definition_ref="oval:mil.disa.stig.rhel8:def:324" />
- <criterion comment="/etc/ssh/sshd_config:IgnoreUserKnownHosts == yes" test_ref="oval:mil.disa.stig.rhel8:tst:15300" />
+ <criteria>
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12400" comment="System command files have mode 755 or less permissive" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:154" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:125" class="compliance" version="1">
<metadata>
- <title>RHEL-08-010521 - The RHEL 8 SSH daemon must not allow Kerberos authentication, except to fulfill documented and validated mission requirements.</title>
+ <title>RHEL-08-010310 - RHEL 8 system commands must be owned by root.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Configuring these settings for the SSH daemon provides additional assurance that remote logon via SSH will not use Kerberos authentication, even in the event of misconfiguration elsewhere.</description>
+ <description>If RHEL 8 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 RHEL 8 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals will be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</description>
</metadata>
- <criteria comment="IF SSH is installed, THEN verify KerberosAuthentication is set to no in /etc/ssh/sshd_config." operator="OR">
- <extend_definition comment="The openssh-server package is installed." definition_ref="oval:mil.disa.stig.rhel8:def:99" negate="true" />
- <criterion comment="/etc/ssh/sshd_config:KerberosAuthentication == no" test_ref="oval:mil.disa.stig.rhel8:tst:15400" />
+ <criteria>
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12500" comment="System command files are owned by root" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:155" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:126" class="compliance" version="1">
<metadata>
- <title>RHEL-08-010540 - RHEL 8 must use a separate file system for /var.</title>
+ <title>RHEL-08-010320 - RHEL 8 system commands must be group-owned by root or a system account.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</description>
+ <description>If RHEL 8 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 RHEL 8 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals will be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.</description>
</metadata>
<criteria>
- <criterion comment="There is a separate file system for /var." test_ref="oval:mil.disa.stig.rhel8:tst:15500" />
- <criterion comment="There is a separate file system configured for /var." test_ref="oval:mil.disa.stig.rhel8:tst:15501" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:12600" comment="System command files are group-owned by root" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:156" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:130" version="1">
<metadata>
- <title>RHEL-08-010541 - RHEL 8 must use a separate file system for /var/log.</title>
+ <title>RHEL-08-010370 - RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</description>
+ <description>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 verifies 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.</description>
</metadata>
<criteria>
- <criterion comment="There is a separate file system for /var/log." test_ref="oval:mil.disa.stig.rhel8:tst:15600" />
- <criterion comment="There is a separate file system configured for /var/log." test_ref="oval:mil.disa.stig.rhel8:tst:15601" />
+ <criterion comment="Every /etc/yum.repos.d/*.repo:[{reponame}] has a gpgcheck entry set to 1." test_ref="oval:mil.disa.stig.rhel8:tst:13000" />
+ <criterion comment="No /etc/yum.repos.d/*.repo:[{reponame}] has a gpgcheck entry set to 0." test_ref="oval:mil.disa.stig.rhel8:tst:13001" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:157" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:131" version="1">
<metadata>
- <title>RHEL-08-010542 - RHEL 8 must use a separate file system for the system audit data path.</title>
+ <title>RHEL-08-010371 - RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</description>
+ <description>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 verifies 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.</description>
</metadata>
<criteria>
- <criterion comment="There is a separate file system for audit data directory." test_ref="oval:mil.disa.stig.rhel8:tst:15700" />
- <criterion comment="There is a separate file system configured for audit data directory." test_ref="oval:mil.disa.stig.rhel8:tst:15701" />
+ <criterion comment="/etc/dnf/dnf.conf:[main]localpkg_gpgcheck is set to true." test_ref="oval:mil.disa.stig.rhel8:tst:13100" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:158" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:132" version="3">
<metadata>
- <title>RHEL-08-010543 - A separate RHEL 8 filesystem must be used for the /tmp directory.</title>
+ <title>RHEL-08-010372 - RHEL 8 must prevent the loading of a new kernel for later execution.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</description>
+ <description>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.
+Disabling kexec_load prevents an unsigned kernel image (that could be a windows kernel or modified vulnerable kernel) from being loaded. Kexec can be used subvert the entire secureboot process and should be avoided at all costs especially since it can load unsigned kernel images.
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf
+/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
+Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.</description>
</metadata>
- <criteria>
- <criterion comment="There is a separate file system for /tmp." test_ref="oval:mil.disa.stig.rhel8:tst:15800" />
- <criterion comment="There is a separate file system configured for /tmp." test_ref="oval:mil.disa.stig.rhel8:tst:15801" />
+ <criteria operator="AND">
+ <criterion comment="kernel.kexec_load_disabled setting in kernel is 1" test_ref="oval:mil.disa.stig.rhel8:tst:13200" />
+ <criterion comment="kernel.kexec_load_disabled setting in sysctl configuration files is set to 1, and nothing else" test_ref="oval:mil.disa.stig.rhel8:tst:13201" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:159" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:133" version="2">
<metadata>
- <title>RHEL-08-010550 - RHEL 8 must not permit direct logons to the root account using remote access via SSH.</title>
+ <title>RHEL-08-010373 - RHEL 8 must enable kernel parameters to enforce discretionary access control on symlinks.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Even though the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging on directly as root. In addition, logging on with a user-specific account provides individual accountability of actions performed on the system.</description>
+ <description>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.
+
+By enabling the fs.protected_symlinks kernel parameter, symbolic links are permitted to be followed only when outside a sticky world-writable directory, or when the UID of the link and follower match, or when the directory owner matches the symlink's owner. Disallowing such symlinks helps mitigate vulnerabilities based on insecure file system accessed by privileged programs, avoiding an exploitation vector exploiting unsafe use of open() or creat().
+
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a gien filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
+
+Based on the information above, if a configuration file begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configurationfile on the system.</description>
</metadata>
- <criteria comment="OpenSSH is installed AND PermitRootLogin == no">
- <extend_definition comment="OpenSSH is installed" definition_ref="oval:mil.disa.stig.rhel8:def:324" />
- <criterion comment="/etc/ssh/sshd_config:PermitRootLogin == no" test_ref="oval:mil.disa.stig.rhel8:tst:15900" />
+ <criteria operator="AND">
+ <criterion comment="fs.protected_symlinks setting in kernel is 1" test_ref="oval:mil.disa.stig.rhel8:tst:13300" />
+ <criterion comment="fs.protected_symlinks setting in sysctl configuration files is set to 1, and nothing else" test_ref="oval:mil.disa.stig.rhel8:tst:13301" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:160" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:134" version="2">
<metadata>
- <title>RHEL-08-010560 - The auditd service must be running in RHEL 8.</title>
+ <title>RHEL-08-010374 - RHEL 8 must enable kernel parameters to enforce discretionary access control on hardlinks.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Configuring RHEL 8 to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across the DoD that reflects the most restrictive security posture consistent with operational requirements.
+ <description>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.
-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.</description>
+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.
+
+By enabling the fs.protected_hardlinks kernel parameter, users can no longer create soft or hard links to files they do not own. Disallowing such hardlinks mitigate vulnerabilities based on insecure file system accessed by privileged programs, avoiding an exploitation vector exploiting unsafe use of open() or creat().
+
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf
+/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
+
+Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.</description>
</metadata>
- <criteria>
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:244" comment="auditd package is installed" />
- <criterion comment="check for running auditd" test_ref="oval:mil.disa.stig.rhel8:tst:16000" />
+ <criteria operator="AND">
+ <criterion comment="fs.protected_hardlinks setting in kernel is 1" test_ref="oval:mil.disa.stig.rhel8:tst:13400" />
+ <criterion comment="fs.protected_hardlinks setting in sysctl configuration files is set to 1, and nothing else" test_ref="oval:mil.disa.stig.rhel8:tst:13401" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:161" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:135" version="2">
<metadata>
- <title>RHEL-08-010561 - The rsyslog service must be running in RHEL 8.</title>
+ <title>RHEL-08-010375 - RHEL 8 must restrict access to the kernel message buffer.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Configuring RHEL 8 to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across the DoD that reflects the most restrictive security posture consistent with operational requirements.
+ <description>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.
-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.</description>
+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.
+
+Restricting access to the kernel message buffer limits access to only root. This prevents attackers from gaining additional system information as a non-privileged user.
+
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a gien filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
+
+Based on the information above, if a configuration file begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configurationfile on the system.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16100" />
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:412" />
+ <criteria operator="AND">
+ <criterion comment="kernel.dmesg_restrict setting in kernel is 1" test_ref="oval:mil.disa.stig.rhel8:tst:13500" />
+ <criterion comment="kernel.dmesg_restrict setting in sysctl configuration files is set to 1, and nothing else" test_ref="oval:mil.disa.stig.rhel8:tst:13501" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:162" class="compliance" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:136" version="2">
<metadata>
- <title>RHEL-08-010571 - RHEL 8 must prevent files with the setuid and setgid bit set from being executed on the /boot directory.</title>
+ <title>RHEL-08-010376 - RHEL 8 must prevent kernel profiling by unprivileged users.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</description>
+ <description>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.
+
+Setting the kernel.perf_event_paranoid kernel parameter to "2" prevents attackers from gaining additional system information as a non-privileged user.
+
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf
+/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
+
+Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.</description>
</metadata>
- <criteria operator="OR" comment="The system is UEFI or /boot is mounted and configured with the nosuid option">
- <criterion comment="/boot/efi/EFI/redhat/grub.cfg exists." test_ref="oval:mil.disa.stig.rhel8:tst:10602" />
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16200" comment="/boot is mounted an configured with the nosuid option." />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16201" comment="If /boot is configured in /etc/fstab it is with the nosuid option." />
- </criteria>
+ <criteria operator="AND">
+ <criterion comment="kernel.perf_event_paranoid setting in kernel is 2" test_ref="oval:mil.disa.stig.rhel8:tst:13600" />
+ <criterion comment="kernel.perf_event_paranoid setting in sysctl configuration files is set to 2, and nothing else" test_ref="oval:mil.disa.stig.rhel8:tst:13601" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:163" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:137" version="1">
<metadata>
- <title>RHEL-08-010580 - RHEL 8 must prevent special devices on non-root local partitions.</title>
+ <title>RHEL-08-010380 - RHEL 8 must require users to provide a password for privilege escalation.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access. The only legitimate location for device files is the /dev directory located on the root partition.</description>
+ <description>Without reauthentication, 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 reauthenticate.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16300" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16301" />
+ <criterion comment="'NOPASSWD' does not exist in /etc/sudoers" test_ref="oval:mil.disa.stig.rhel8:tst:13700" />
+ <criterion comment="'NOPASSWD' does not exist in /etc/sudoers.d" test_ref="oval:mil.disa.stig.rhel8:tst:13701" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:165" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:138" version="1">
<metadata>
- <title>RHEL-08-010630 - RHEL 8 must prevent code from being executed on file systems that are imported via Network File System (NFS).</title>
+ <title>RHEL-08-010381 - RHEL 8 must require users to reauthenticate for privilege escalation.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>The "noexec" mount option causes the system not to execute binary files. This option must be used for mounting any file system not containing approved binary as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</description>
+ <description>Without reauthentication, 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 reauthenticate.</description>
</metadata>
- <criteria operator="AND">
- <criterion comment="remote nfs filesystems in /etc/fstab have noexec" test_ref="oval:mil.disa.stig.rhel8:tst:16500" />
- <criterion comment="actual nfs mounts have noexec" test_ref="oval:mil.disa.stig.rhel8:tst:16501" />
+ <criteria>
+ <criterion comment="'!authenticate' does not exist in /etc/sudoers" test_ref="oval:mil.disa.stig.rhel8:tst:13800" />
+ <criterion comment="'!authenticate' does not exist in /etc/sudoers.d" test_ref="oval:mil.disa.stig.rhel8:tst:13801" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:166" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:139" version="2">
<metadata>
- <title>RHEL-08-010640 - RHEL 8 must prevent special devices on file systems that are imported via Network File System (NFS).</title>
+ <title>RHEL-08-010390 - RHEL 8 must have the packages required for multifactor authentication installed.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</description>
+ <description>Using an authentication device, such as a DoD Common Access Card (CAC) or token that is separate from the information system, ensures that even if the information system is compromised, credentials stored on the authentication device will not be affected.
+
+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 (PIV) card and the DoD CAC.
+
+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).</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16600" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16601" />
+ <criterion comment="package openssl-pkcs11 is installed" test_ref="oval:mil.disa.stig.rhel8:tst:13901" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:167" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:145" class="compliance" version="1">
<metadata>
- <title>RHEL-08-010650 - RHEL 8 must prevent files with the setuid and setgid bit set from being executed on file systems that are imported via Network File System (NFS).</title>
+ <title>RHEL-08-010440 - YUM must remove all software components after updated versions have been installed on RHEL 8.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</description>
+ <description>Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the information system.</description>
</metadata>
- <criteria operator="AND">
- <criterion comment="remote nfs filesystems in /etc/fstab have nosuid" test_ref="oval:mil.disa.stig.rhel8:tst:16700" />
- <criterion comment="actual nfs mounts have nosuid" test_ref="oval:mil.disa.stig.rhel8:tst:16701" />
+ <criteria>
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:14500" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:168" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:146" class="compliance" version="1">
<metadata>
- <title>RHEL-08-010671 - RHEL 8 must disable the kernel.core_pattern.</title>
+ <title>RHEL-08-010450 - RHEL 8 must enable the SELinux targeted policy.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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 sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
-/etc/sysctl.d/*.conf
-/run/sysctl.d/*.conf
-/usr/local/lib/sysctl.d/*.conf
-/usr/lib/sysctl.d/*.conf
-/lib/sysctl.d/*.conf
-/etc/sysctl.conf
+ <description>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.
-Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.</description>
+This requirement applies to operating systems performing security function verification/testing and/or systems and environments that require this functionality.</description>
</metadata>
- <criteria operator="AND">
- <criterion comment="kernel.core_pattern setting in kernel is '|/bin/false'." test_ref="oval:mil.disa.stig.rhel8:tst:16800" />
- <criterion comment="kernel.core_pattern setting in /etc/sysctld./99-sysctl.conf is set to '|/bin/false', and nothing else" test_ref="oval:mil.disa.stig.rhel8:tst:16801" />
+ <criteria>
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:14600" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:169" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:147" version="1">
<metadata>
- <title>RHEL-08-010673 - RHEL 8 must disable core dumps for all users.</title>
+ <title>RHEL-08-010460 - There must be no shosts.equiv files on the RHEL 8 operating system.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers trying to debug problems.</description>
+ <description>The "shosts.equiv" files are used to configure host-based authentication for the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.</description>
</metadata>
- <criteria operator="OR">
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16900" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16901" />
+ <criteria>
+ <criterion comment="There must be no shosts.equiv files on the system." test_ref="oval:mil.disa.stig.rhel8:tst:14700" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:170" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:148" version="1">
<metadata>
- <title>RHEL-08-010674 - RHEL 8 must disable storing core dumps.</title>
+ <title>RHEL-08-010470 - There must be no .shosts files on the RHEL 8 operating system.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers trying to debug problems.</description>
+ <description>The ".shosts" files are used to configure host-based authentication for individual users or the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:17000" />
+ <criterion comment="There must be no .shosts files on the system." test_ref="oval:mil.disa.stig.rhel8:tst:14800" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:171" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:149" version="5">
<metadata>
- <title>RHEL-08-010675 - RHEL 8 must disable core dump backtraces.</title>
+ <title>RHEL-08-010480 - The RHEL 8 SSH public host key files must have mode 0644 or less permissive.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers trying to debug problems.</description>
+ <description>If a public host key file is modified by an unauthorized user, the SSH service may be compromised.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:17100" />
+ <criteria comment="OpenSSH-server is installed and public key files permissions are acceptable">
+ <extend_definition comment="OpenSSH is installed" definition_ref="oval:mil.disa.stig.rhel8:def:324" />
+ <criterion comment="The SUSE operating system SSH daemon public host key files have mode 0644 or less permissive" test_ref="oval:mil.disa.stig.rhel8:tst:14900" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:177" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:150" version="3">
<metadata>
- <title>RHEL-08-010760 - All RHEL 8 local interactive user accounts must be assigned a home directory upon creation</title>
+ <title>RHEL-08-010490 - The RHEL 8 SSH private host key files must have mode 0600 or less permissive.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.</description>
+ <description>If an unauthorized user obtains the private SSH host key file, the host could be impersonated.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:17700" comment="All RHEL 8 local interactive user accounts are assigned a home directory upon creation" />
+ <criteria comment="OpenSSH is installed and check private key files permissions">
+ <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:324" comment="openssh is installed" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:15000" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:179" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:151" version="2">
<metadata>
- <title>RHEL-08-010830 - RHEL 8 must not allow users to override SSH environment variables.</title>
+ <title>RHEL-08-010500 - The RHEL 8 SSH daemon must perform strict mode checking of home directory configuration files.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>SSH environment options potentially allow users to bypass access restriction in some configurations.</description>
+ <description>If other users have access to modify user-specific SSH configuration files, they may be able to log on to the system as another user.</description>
</metadata>
- <criteria comment="IF SSH is installed, THEN verify PermitUserEnvironment is set to no in /etc/ssh/sshd_config." operator="OR">
- <extend_definition comment="The openssh-server package is installed." definition_ref="oval:mil.disa.stig.rhel8:def:99" negate="true" />
- <criterion comment="/etc/ssh/sshd_config:PermitUserEnvironment == no" test_ref="oval:mil.disa.stig.rhel8:tst:17900" />
+ <criteria comment="OpenSSH is installed AND StrictModes == yes">
+ <extend_definition comment="OpenSSH is installed" definition_ref="oval:mil.disa.stig.rhel8:def:324" />
+ <criterion comment="/etc/ssh/sshd_config:StrictModes == yes" test_ref="oval:mil.disa.stig.rhel8:tst:15100" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:180" version="3">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:152" version="3">
<metadata>
- <title>RHEL-08-020010 - RHEL 8 must automatically lock an account when three unsuccessful logon attempts occur.</title>
+ <title>RHEL-08-010510 - The RHEL 8 SSH daemon must not allow compression or must only allow compression after successful authentication.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program.
-
-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 also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
+ <description>If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the system from an unauthenticated connection, potentially with root privileges.</description>
</metadata>
- <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so to lock an account after 3 failed login attempts or RHEL version is 8.2 or greater.">
- <criterion comment="The RHEL 8 version is RHEL 8.2 or newer" test_ref="oval:mil.disa.stig.rhel8:tst:18006" />
- <criteria operator="AND" comment="Check that system-auth and password-auth are configured to lock an account after 3 failed login attempts.">
- <criterion comment="pam_faillock.so authfail line exists in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18000" />
- <criterion comment="pam_faillock.so preauth deny value set in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18002" />
- <criterion comment="account required pam_faillock.so exists in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18004" />
- <criterion comment="pam_faillock.so authfail exists in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18001" />
- <criterion comment="pam_faillock.so preauth deny value set in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18003" />
- <criterion comment="account required pam_faillock.so exists in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18005" />
- </criteria>
+ <criteria comment="IF SSH is installed, THEN verify Compression is set to no in /etc/ssh/sshd_config." operator="OR">
+ <extend_definition comment="The openssh-server package is installed." definition_ref="oval:mil.disa.stig.rhel8:def:99" negate="true" />
+ <criterion comment="/etc/ssh/sshd_config:Compression == no or Compression == delayed" test_ref="oval:mil.disa.stig.rhel8:tst:15200" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:181" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:153" version="2">
<metadata>
- <title>RHEL-08-020011 - RHEL 8 must automatically lock an account when three unsuccessful logon attempts occur.</title>
+ <title>RHEL-08-010520 - The RHEL 8 SSH daemon must not allow authentication using known hosts authentication.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in /etc/passwd and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout.
-
-From "faillock.conf" man pages: Note that the default directory that "pam_faillock" uses is usually cleared on system boot so the access will be also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
+ <description>Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.</description>
</metadata>
- <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so to lock an account after 3 failed login attempts or RHEL version is 8.1 or older.">
- <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18106" />
- <criterion comment="deny is set to 3 or less but not 0 in /etc/security/faillock.conf" test_ref="oval:mil.disa.stig.rhel8:tst:18107" />
+ <criteria comment="OpenSSH is installed AND IgnoreUserKnownHosts == yes">
+ <extend_definition comment="OpenSSH is installed" definition_ref="oval:mil.disa.stig.rhel8:def:324" />
+ <criterion comment="/etc/ssh/sshd_config:IgnoreUserKnownHosts == yes" test_ref="oval:mil.disa.stig.rhel8:tst:15300" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:182" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:154" version="3">
<metadata>
- <title>RHEL-08-020012 - RHEL 8 must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period.</title>
+ <title>RHEL-08-010521 - The RHEL 8 SSH daemon must not allow Kerberos authentication, except to fulfill documented and validated mission requirements.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program.
-
-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.</description>
+ <description>Configuring these settings for the SSH daemon provides additional assurance that remote logon via SSH will not use Kerberos authentication, even in the event of misconfiguration elsewhere.</description>
</metadata>
- <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so to us the fail_interval between 1 and 900 or RHEL version is 8.2 or newer.">
- <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18203" />
- <criteria operator="AND" comment="Check that system-auth and password-auth are configured to use a fail_interval between 1 and 900.">
- <criterion comment="pam_faillock.so peauth fail_interval value set to 900 or less but not 0 in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18200" />
- <criterion comment="pam_faillock.so peauth fail_interval value set to 900 or less but not 0 in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18201" />
- </criteria>
+ <criteria comment="IF SSH is installed, THEN verify KerberosAuthentication is set to no in /etc/ssh/sshd_config." operator="OR">
+ <extend_definition comment="The openssh-server package is installed." definition_ref="oval:mil.disa.stig.rhel8:def:99" negate="true" />
+ <criterion comment="/etc/ssh/sshd_config:KerberosAuthentication == no" test_ref="oval:mil.disa.stig.rhel8:tst:15400" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:183" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:155" version="1">
<metadata>
- <title>RHEL-08-020013 - RHEL 8 must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period.</title>
+ <title>RHEL-08-010540 - RHEL 8 must use a separate file system for /var.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in /etc/passwd and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout.
-
-From "faillock.conf" 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.</description>
+ <description>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</description>
</metadata>
- <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so to fail_interval between 1 and 900 or RHEL version is 8.1 or older.">
- <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18306" />
- <criterion comment="fail_interval is set to 900 or greater in /etc/security/faillock.conf" test_ref="oval:mil.disa.stig.rhel8:tst:18307" />
+ <criteria>
+ <criterion comment="There is a separate file system for /var." test_ref="oval:mil.disa.stig.rhel8:tst:15500" />
+ <criterion comment="There is a separate file system configured for /var." test_ref="oval:mil.disa.stig.rhel8:tst:15501" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:184" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:156" version="1">
<metadata>
- <title>RHEL-08-020014 - RHEL 8 must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.</title>
+ <title>RHEL-08-010541 - RHEL 8 must use a separate file system for /var/log.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program.
-
-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.</description>
+ <description>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</description>
</metadata>
- <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so the unlock_time equals 0 or RHEL version is 8.2 or newer.">
- <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18404" />
- <criteria operator="AND" comment="Check that system-auth and password-auth are configured to use a unlock_time between 1 and 900.">
- <criterion comment="pam_faillock.so preauth unlock_time value set to 0 in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18400" />
- <criterion comment="pam_faillock.so preauth unlock_time value set to 0 in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18401" />
- <criterion comment="pam_faillock.so authfail unlock_time value set to 0 in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18402" />
- <criterion comment="pam_faillock.so authfail unlock_time value set to 0 in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18403" />
- </criteria>
+ <criteria>
+ <criterion comment="There is a separate file system for /var/log." test_ref="oval:mil.disa.stig.rhel8:tst:15600" />
+ <criterion comment="There is a separate file system configured for /var/log." test_ref="oval:mil.disa.stig.rhel8:tst:15601" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:185" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:157" version="1">
<metadata>
- <title>RHEL-08-020015 - RHEL 8 must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.</title>
+ <title>RHEL-08-010542 - RHEL 8 must use a separate file system for the system audit data path.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in /etc/passwd and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout.
-
-From "faillock.conf" 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.</description>
+ <description>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</description>
</metadata>
- <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so to unlock_time between 1 and 900 or RHEL version is 8.1 or older.">
- <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18506" />
- <criterion comment="unlock_time is set to 0 in /etc/security/faillock.conf" test_ref="oval:mil.disa.stig.rhel8:tst:18507" />
+ <criteria>
+ <criterion comment="There is a separate file system for audit data directory." test_ref="oval:mil.disa.stig.rhel8:tst:15700" />
+ <criterion comment="There is a separate file system configured for audit data directory." test_ref="oval:mil.disa.stig.rhel8:tst:15701" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:186" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:158" version="1">
<metadata>
- <title>RHEL-08-020018 - RHEL 8 must prevent system messages from being presented when three unsuccessful logon attempts occur.</title>
+ <title>RHEL-08-010543 - A separate RHEL 8 filesystem must be used for the /tmp directory.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program.
-
-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 also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
+ <description>The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.</description>
</metadata>
- <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so with the silent option or RHEL version is 8.2 or newer.">
- <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18602" />
- <criteria operator="AND" comment="Check that system-auth and password-auth are configured to use silent.">
- <criterion comment="pam_faillock.so preauth silent is in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18600" />
- <criterion comment="pam_faillock.so preauth silent is in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18601" />
- </criteria>
+ <criteria>
+ <criterion comment="There is a separate file system for /tmp." test_ref="oval:mil.disa.stig.rhel8:tst:15800" />
+ <criterion comment="There is a separate file system configured for /tmp." test_ref="oval:mil.disa.stig.rhel8:tst:15801" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:187" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:159" version="2">
<metadata>
- <title>RHEL-08-020019 - RHEL 8 must prevent system messages from being presented when three unsuccessful logon attempts occur.</title>
+ <title>RHEL-08-010550 - RHEL 8 must not permit direct logons to the root account using remote access via SSH.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in /etc/passwd and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout.
-
-From "faillock.conf" man pages: Note that the default directory that "pam_faillock" uses is usually cleared on system boot so the access will be also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
+ <description>Even though the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging on directly as root. In addition, logging on with a user-specific account provides individual accountability of actions performed on the system.</description>
</metadata>
- <criteria operator="OR" comment="Both system-auth and password-auth are properly configured to use pam_faillock.so and silent or RHEL version is 8.1 or older.">
- <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18706" />
- <criterion comment="silent is set in /etc/security/faillock.conf" test_ref="oval:mil.disa.stig.rhel8:tst:18707" />
+ <criteria comment="OpenSSH is installed AND PermitRootLogin == no">
+ <extend_definition comment="OpenSSH is installed" definition_ref="oval:mil.disa.stig.rhel8:def:324" />
+ <criterion comment="/etc/ssh/sshd_config:PermitRootLogin == no" test_ref="oval:mil.disa.stig.rhel8:tst:15900" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:188" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:160" version="2">
<metadata>
- <title>RHEL-08-020020 - RHEL 8 must log user name information when unsuccessful logon attempts occur.</title>
+ <title>RHEL-08-010560 - The auditd service must be running in RHEL 8.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program.
+ <description>Configuring RHEL 8 to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across the DoD that reflects the most restrictive security posture consistent with operational requirements.
-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 also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
+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.</description>
</metadata>
- <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so with the audit option or RHEL version is 8.2 or newer.">
- <criterion comment="The RHEL 8 version is RHEL 8.2 or newer" test_ref="oval:mil.disa.stig.rhel8:tst:18802" />
- <criteria operator="AND" comment="Check that system-auth and password-auth are configured to use audit.">
- <criterion comment="pam_faillock.so preauth audit is in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18800" />
- <criterion comment="pam_faillock.so preauth audit is in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18801" />
- </criteria>
+ <criteria>
+ <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:244" comment="auditd package is installed" />
+ <criterion comment="check for running auditd" test_ref="oval:mil.disa.stig.rhel8:tst:16000" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:189" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:161" class="compliance" version="1">
<metadata>
- <title>RHEL-08-020021 - RHEL 8 must prevent system messages from being presented when three unsuccessful logon attempts occur.</title>
+ <title>RHEL-08-010561 - The rsyslog service must be running in RHEL 8.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in /etc/passwd and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout.
+ <description>Configuring RHEL 8 to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across the DoD that reflects the most restrictive security posture consistent with operational requirements.
-From "faillock.conf" man pages: Note that the default directory that "pam_faillock" uses is usually cleared on system boot so the access will be also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
+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.</description>
</metadata>
- <criteria operator="OR" comment="/etc/security/faillock.conf has audit configured or RHEL version is 8.1 or older.">
- <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18906" />
- <criterion comment="audit is set in /etc/security/faillock.conf" test_ref="oval:mil.disa.stig.rhel8:tst:18907" />
+ <criteria>
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16100" />
+ <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:412" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:190" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:162" class="compliance" version="2">
<metadata>
- <title>RHEL-08-020022 - RHEL 8 must include root when automatically locking an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.</title>
+ <title>RHEL-08-010571 - RHEL 8 must prevent files with the setuid and setgid bit set from being executed on the /boot directory.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program.
-
-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 also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
+ <description>The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</description>
</metadata>
- <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so with the even_deny_root option or RHEL version is 8.2 or newer.">
- <criterion comment="The RHEL 8 version is RHEL 8.2 or newer" test_ref="oval:mil.disa.stig.rhel8:tst:19002" />
- <criteria operator="AND" comment="Check that system-auth and password-auth are configured to use even_deny_root.">
- <criterion comment="pam_faillock.so preauth even_deny_root is in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:19000" />
- <criterion comment="pam_faillock.so preauth even_deny_root is in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:19001" />
+ <criteria operator="OR" comment="The system is UEFI or /boot is mounted and configured with the nosuid option">
+ <criterion comment="/boot/efi/EFI/redhat/grub.cfg exists." test_ref="oval:mil.disa.stig.rhel8:tst:10602" />
+ <criteria>
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16200" comment="/boot is mounted an configured with the nosuid option." />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16201" comment="If /boot is configured in /etc/fstab it is with the nosuid option." />
</criteria>
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:191" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:163" class="compliance" version="1">
<metadata>
- <title>RHEL-08-020023 - RHEL 8 must include root when automatically locking an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.</title>
+ <title>RHEL-08-010580 - RHEL 8 must prevent special devices on non-root local partitions.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in /etc/passwd and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout.
-
-From "faillock.conf" man pages: Note that the default directory that "pam_faillock" uses is usually cleared on system boot so the access will be also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
+ <description>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access. The only legitimate location for device files is the /dev directory located on the root partition.</description>
</metadata>
- <criteria operator="OR" comment="Both system-auth and password-auth are properly configured to use pam_faillock.so and even_deny_root or RHEL version is 8.1 or older.">
- <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:19106" />
- <criterion comment="even_deny_root is set in /etc/security/faillock.conf" test_ref="oval:mil.disa.stig.rhel8:tst:19107" />
+ <criteria>
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16300" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16301" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:192" class="compliance" version="3">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:165" version="2">
<metadata>
- <title>RHEL-08-020024 - RHEL 8 must limit the number of concurrent sessions to ten for all accounts and/or account types.</title>
+ <title>RHEL-08-010630 - RHEL 8 must prevent code from being executed on file systems that are imported via Network File System (NFS).</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Operating system management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the number of allowed users and sessions per user is helpful in reducing the risks related to DoS attacks.
-
-This requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions should be defined based on mission needs and the operational environment for each system.</description>
+ <description>The "noexec" mount option causes the system not to execute binary files. This option must be used for mounting any file system not containing approved binary as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</description>
</metadata>
- <criteria>
- <criterion comment="limits.conf:maxlogins is set to 10 or less by default" test_ref="oval:mil.disa.stig.rhel8:tst:19200" />
- <criterion comment="limits.conf:maxlogins is set to 10 or less for non-default domains" test_ref="oval:mil.disa.stig.rhel8:tst:19201" />
+ <criteria operator="AND">
+ <criterion comment="remote nfs filesystems in /etc/fstab have noexec" test_ref="oval:mil.disa.stig.rhel8:tst:16500" />
+ <criterion comment="actual nfs mounts have noexec" test_ref="oval:mil.disa.stig.rhel8:tst:16501" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:193" class="compliance" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:166" class="compliance" version="1">
<metadata>
- <title>RHEL-08-020040 - RHEL 8 must enable a user session lock until that user re-establishes access using established identification and authentication procedures for command line sessions.</title>
+ <title>RHEL-08-010640 - RHEL 8 must prevent special devices on file systems that are imported via Network File System (NFS).</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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, RHEL 8 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.
-
-Tmux is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen. Red Hat endorses tmux as the recommended session controlling package.</description>
+ <description>The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19301" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16600" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16601" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:194" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:167" version="2">
<metadata>
- <title>RHEL-08-020041 - RHEL 8 must ensure session control is automatically started at shell initialization.</title>
+ <title>RHEL-08-010650 - RHEL 8 must prevent files with the setuid and setgid bit set from being executed on file systems that are imported via Network File System (NFS).</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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, RHEL 8 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.
-
-Tmux is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen. Red Hat endorses tmux as the recommended session controlling package.</description>
+ <description>The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19400" />
+ <criteria operator="AND">
+ <criterion comment="remote nfs filesystems in /etc/fstab have nosuid" test_ref="oval:mil.disa.stig.rhel8:tst:16700" />
+ <criterion comment="actual nfs mounts have nosuid" test_ref="oval:mil.disa.stig.rhel8:tst:16701" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:195" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:168" version="2">
<metadata>
- <title>RHEL-08-020042 - RHEL 8 must prevent users from disabling session control mechanisms.</title>
+ <title>RHEL-08-010671 - RHEL 8 must disable the kernel.core_pattern.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
+ <description>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 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, RHEL 8 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.
+The sysctl --system command will load settings from all system configuration files. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. Files are read from directories in the following list from top to bottom. Once a file of a given filename is loaded, any file of the same name in subsequent directories is ignored.
+/etc/sysctl.d/*.conf
+/run/sysctl.d/*.conf
+/usr/local/lib/sysctl.d/*.conf
+/usr/lib/sysctl.d/*.conf
+/lib/sysctl.d/*.conf
+/etc/sysctl.conf
-Tmux is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen. Red Hat endorses tmux as the recommended session controlling package.</description>
+Based on the information above, if a configuration file that begins with "99-" is created in the "/etc/sysctl.d/" directory, it will take precedence over any other configuration file on the system.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19500" />
+ <criteria operator="AND">
+ <criterion comment="kernel.core_pattern setting in kernel is '|/bin/false'." test_ref="oval:mil.disa.stig.rhel8:tst:16800" />
+ <criterion comment="kernel.core_pattern setting in /etc/sysctld./99-sysctl.conf is set to '|/bin/false', and nothing else" test_ref="oval:mil.disa.stig.rhel8:tst:16801" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:196" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:169" class="compliance" version="1">
<metadata>
- <title>RHEL-08-020100 - RHEL 8 must ensure a password complexity module is enabled.</title>
+ <title>RHEL-08-010673 - RHEL 8 must disable core dumps for all users.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.
-
-RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. This is set in both:
-/etc/pam.d/password-auth
-/etc/pam.d/system-auth
+ <description>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.
-Note the value of "retry" set in these configuration files should be between "1" and "3". Manual changes to the listed files may be overwritten by the "authselect" program.</description>
+A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers trying to debug problems.</description>
</metadata>
- <criteria>
- <criterion comment="The pam_pwquality module is included in password-auth." test_ref="oval:mil.disa.stig.rhel8:tst:19600" />
- <criterion comment="The pam_pwquality module is included in system-auth." test_ref="oval:mil.disa.stig.rhel8:tst:19601" />
+ <criteria operator="OR">
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16900" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:16901" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:197" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:170" class="compliance" version="1">
<metadata>
- <title>RHEL-08-020110 - RHEL 8 must enforce password complexity by requiring that at least one uppercase character be used.</title>
+ <title>RHEL-08-010674 - RHEL 8 must disable storing core dumps.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
+ <description>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.
-RHEL 8 utilizes pwquality as a mechanism to enforce password complexity. Note that in order to require uppercase characters, without degrading the "minlen" value, the credit value must be expressed as a negative number in "/etc/security/pwquality.conf".</description>
+A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers trying to debug problems.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19700" comment="at least one uppercase character is required" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:17000" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:198" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:171" class="compliance" version="1">
<metadata>
- <title>RHEL-08-020120 - RHEL 8 must enforce password complexity by requiring that at least one lower-case character be used.</title>
+ <title>RHEL-08-010675 - RHEL 8 must disable core dump backtraces.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
+ <description>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.
-RHEL 8 utilizes pwquality as a mechanism to enforce password complexity. Note that in order to require lower-case characters without degrading the "minlen" value, the credit value must be expressed as a negative number in "/etc/security/pwquality.conf".</description>
+A core dump includes a memory image taken at the time the operating system terminates an application. The memory image could contain sensitive data and is generally useful only for developers trying to debug problems.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19800" comment="at least one lowercase character is required" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:17100" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:199" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:177" version="2">
<metadata>
- <title>RHEL-08-020130 - RHEL 8 must enforce password complexity by requiring that at least one numeric character be used.</title>
+ <title>RHEL-08-010760 - All RHEL 8 local interactive user accounts must be assigned a home directory upon creation</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. Note that in order to require numeric characters, without degrading the minlen value, the credit value must be expressed as a negative number in "/etc/security/pwquality.conf".</description>
+ <description>If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19900" comment="at least one numeric character is required" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:17700" comment="All RHEL 8 local interactive user accounts are assigned a home directory upon creation" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:200" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:179" version="2">
<metadata>
- <title>RHEL-08-020140 - RHEL 8 must require the maximum number of repeating characters of the same character class be limited to four when passwords are changed.</title>
+ <title>RHEL-08-010830 - RHEL 8 must not allow users to override SSH environment variables.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
-
-RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. The "maxclassrepeat" option sets the maximum number of allowed same consecutive characters in the same class in the new password.</description>
+ <description>SSH environment options potentially allow users to bypass access restriction in some configurations.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20000" comment="the maximum number of repeating characters of the same character class must be limited to four when passwords are changed" />
+ <criteria comment="IF SSH is installed, THEN verify PermitUserEnvironment is set to no in /etc/ssh/sshd_config." operator="OR">
+ <extend_definition comment="The openssh-server package is installed." definition_ref="oval:mil.disa.stig.rhel8:def:99" negate="true" />
+ <criterion comment="/etc/ssh/sshd_config:PermitUserEnvironment == no" test_ref="oval:mil.disa.stig.rhel8:tst:17900" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:201" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:180" version="3">
<metadata>
- <title>RHEL-08-020150 - RHEL 8 must require the maximum number of repeating characters be limited to three when passwords are changed.</title>
+ <title>RHEL-08-020010 - RHEL 8 must automatically lock an account when three unsuccessful logon attempts occur.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
+ <description>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.
-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.
+RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program.
-RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. The "maxrepeat" option sets the maximum number of allowed same consecutive characters in a new password.</description>
+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 also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20100" comment="the maximum number of repeating characters must be limited to three when passwords are changed" />
+ <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so to lock an account after 3 failed login attempts or RHEL version is 8.2 or greater.">
+ <criterion comment="The RHEL 8 version is RHEL 8.2 or newer" test_ref="oval:mil.disa.stig.rhel8:tst:18006" />
+ <criteria operator="AND" comment="Check that system-auth and password-auth are configured to lock an account after 3 failed login attempts.">
+ <criterion comment="pam_faillock.so authfail line exists in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18000" />
+ <criterion comment="pam_faillock.so preauth deny value set in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18002" />
+ <criterion comment="account required pam_faillock.so exists in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18004" />
+ <criterion comment="pam_faillock.so authfail exists in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18001" />
+ <criterion comment="pam_faillock.so preauth deny value set in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18003" />
+ <criterion comment="account required pam_faillock.so exists in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18005" />
+ </criteria>
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:202" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:181" version="2">
<metadata>
- <title>RHEL-08-020160 - RHEL 8 must require the change of at least four character classes when passwords are changed.</title>
+ <title>RHEL-08-020011 - RHEL 8 must automatically lock an account when three unsuccessful logon attempts occur.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
+ <description>In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in /etc/passwd and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout.
-RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. The "minclass" option sets the minimum number of required classes of characters for the new password (digits, uppercase, lowercase, others).</description>
+From "faillock.conf" man pages: Note that the default directory that "pam_faillock" uses is usually cleared on system boot so the access will be also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20200" comment="passwords must contain at least four character classes" />
+ <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so to lock an account after 3 failed login attempts or RHEL version is 8.1 or older.">
+ <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18106" />
+ <criterion comment="deny is set to 3 or less but not 0 in /etc/security/faillock.conf" test_ref="oval:mil.disa.stig.rhel8:tst:18107" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:203" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:182" version="1">
<metadata>
- <title>RHEL-08-020170 - RHEL 8 must require the change of at least 8 characters when passwords are changed.</title>
+ <title>RHEL-08-020012 - RHEL 8 must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
+ <description>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.
-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.
+RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program.
-RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. The "difok" option sets the number of characters in a password that must not be present in the old password.</description>
+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.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20300" />
+ <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so to us the fail_interval between 1 and 900 or RHEL version is 8.2 or newer.">
+ <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18203" />
+ <criteria operator="AND" comment="Check that system-auth and password-auth are configured to use a fail_interval between 1 and 900.">
+ <criterion comment="pam_faillock.so peauth fail_interval value set to 900 or less but not 0 in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18200" />
+ <criterion comment="pam_faillock.so peauth fail_interval value set to 900 or less but not 0 in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18201" />
+ </criteria>
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:204" version="4">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:183" version="2">
<metadata>
- <title>RHEL-08-020180 - RHEL 8 passwords must have a 24 hours/1 day minimum password lifetime restriction in /etc/shadow.</title>
+ <title>RHEL-08-020013 - RHEL 8 must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.</description>
+ <description>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.
+
+In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in /etc/passwd and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout.
+
+From "faillock.conf" 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.</description>
</metadata>
- <criteria>
- <criterion comment="Root does not have a minimum password age of 0 or blank" test_ref="oval:mil.disa.stig.rhel8:tst:20400" />
- <criterion comment="Non-system users do not have a minimum password age of 0 or blank" test_ref="oval:mil.disa.stig.rhel8:tst:20401" />
+ <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so to fail_interval between 1 and 900 or RHEL version is 8.1 or older.">
+ <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18306" />
+ <criterion comment="fail_interval is set to 900 or greater in /etc/security/faillock.conf" test_ref="oval:mil.disa.stig.rhel8:tst:18307" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:205" class="compliance" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:184" version="1">
<metadata>
- <title>RHEL-08-020190 - RHEL 8 passwords for new users or password changes must have a 24 hours/1 day minimum password lifetime restriction in /etc/logins.def.</title>
+ <title>RHEL-08-020014 - RHEL 8 must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.</description>
+ <description>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.
+
+RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program.
+
+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.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20500" />
+ <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so the unlock_time equals 0 or RHEL version is 8.2 or newer.">
+ <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18404" />
+ <criteria operator="AND" comment="Check that system-auth and password-auth are configured to use a unlock_time between 1 and 900.">
+ <criterion comment="pam_faillock.so preauth unlock_time value set to 0 in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18400" />
+ <criterion comment="pam_faillock.so preauth unlock_time value set to 0 in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18401" />
+ <criterion comment="pam_faillock.so authfail unlock_time value set to 0 in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18402" />
+ <criterion comment="pam_faillock.so authfail unlock_time value set to 0 in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18403" />
+ </criteria>
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:206" class="compliance" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:185" version="2">
<metadata>
- <title>RHEL-08-020200 - RHEL 8 user account passwords must have a 60-day maximum password lifetime restriction.</title>
+ <title>RHEL-08-020015 - RHEL 8 must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If RHEL 8 does not limit the lifetime of passwords and force users to change their passwords, there is the risk that RHEL 8 passwords could be compromised.</description>
+ <description>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.
+
+In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in /etc/passwd and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout.
+
+From "faillock.conf" 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.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20600" />
+ <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so to unlock_time between 1 and 900 or RHEL version is 8.1 or older.">
+ <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18506" />
+ <criterion comment="unlock_time is set to 0 in /etc/security/faillock.conf" test_ref="oval:mil.disa.stig.rhel8:tst:18507" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:207" version="5">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:186" version="1">
<metadata>
- <title>RHEL-08-020210 - RHEL 8 user account passwords must be configured so that existing passwords are restricted to a 60-day maximum lifetime.</title>
+ <title>RHEL-08-020018 - RHEL 8 must prevent system messages from being presented when three unsuccessful logon attempts occur.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If RHEL 8 does not limit the lifetime of passwords and force users to change their passwords, there is the risk that RHEL 8 passwords could be compromised.</description>
+ <description>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.
+
+RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program.
+
+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 also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
</metadata>
- <criteria>
- <criterion comment="No password in /etc/shadow has a maximum password age of 0 or greater than 60" test_ref="oval:mil.disa.stig.rhel8:tst:20700" />
- <criterion comment="Root password in /etc/shadow does not have a maximum password age of 0 or greater than 60" test_ref="oval:mil.disa.stig.rhel8:tst:20701" />
- <criterion comment="Non-system users do not have a blank entry in /etc/shadow for maximum password age" test_ref="oval:mil.disa.stig.rhel8:tst:20702" />
- <criterion comment="Root does not have a blank entry in /etc/shadow for maximum password age" test_ref="oval:mil.disa.stig.rhel8:tst:20703" />
+ <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so with the silent option or RHEL version is 8.2 or newer.">
+ <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18602" />
+ <criteria operator="AND" comment="Check that system-auth and password-auth are configured to use silent.">
+ <criterion comment="pam_faillock.so preauth silent is in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18600" />
+ <criterion comment="pam_faillock.so preauth silent is in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18601" />
+ </criteria>
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:208" class="compliance" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:187" version="2">
<metadata>
- <title>RHEL-08-020220 - RHEL 8 passwords must be prohibited from reuse for a minimum of five generations.</title>
+ <title>RHEL-08-020019 - RHEL 8 must prevent system messages from being presented when three unsuccessful logon attempts occur.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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 reuse their password consecutively when that password has exceeded its defined lifetime, the end result is a password that is not changed per policy requirements.
+ <description>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.
-RHEL 8 utilizes "pwquality" consecutively as a mechanism to enforce password complexity. This is set in both:
-/etc/pam.d/password-auth
-/etc/pam.d/system-auth.
+In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in /etc/passwd and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout.
-Note that manual changes to the listed files may be overwritten by the "authselect" program.</description>
+From "faillock.conf" man pages: Note that the default directory that "pam_faillock" uses is usually cleared on system boot so the access will be also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20800" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20801" />
+ <criteria operator="OR" comment="Both system-auth and password-auth are properly configured to use pam_faillock.so and silent or RHEL version is 8.1 or older.">
+ <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18706" />
+ <criterion comment="silent is set in /etc/security/faillock.conf" test_ref="oval:mil.disa.stig.rhel8:tst:18707" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:209" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:188" version="1">
<metadata>
- <title>RHEL-08-020230 - RHEL 8 passwords must have a minimum of 15 characters.</title>
+ <title>RHEL-08-020020 - RHEL 8 must log user name information when unsuccessful logon attempts occur.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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 increase exponentially the time and/or resources required to compromise the password.
-
-RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. Configurations are set in the "etc/security/pwquality.conf" file.
+ <description>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 "minlen", sometimes noted as minimum length, acts as a "score" of complexity based on the credit components of the "pwquality" module. By setting the credit components to a negative value, not only will those components be required, they will not count towards the total "score" of "minlen". This will enable "minlen" to require a 15-character minimum.
+RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program.
-The DoD minimum password requirement is 15 characters.</description>
+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 also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20900" />
+ <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so with the audit option or RHEL version is 8.2 or newer.">
+ <criterion comment="The RHEL 8 version is RHEL 8.2 or newer" test_ref="oval:mil.disa.stig.rhel8:tst:18802" />
+ <criteria operator="AND" comment="Check that system-auth and password-auth are configured to use audit.">
+ <criterion comment="pam_faillock.so preauth audit is in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18800" />
+ <criterion comment="pam_faillock.so preauth audit is in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:18801" />
+ </criteria>
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:210" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:189" version="2">
<metadata>
- <title>RHEL-08-020231 - RHEL 8 passwords for new users must have a minimum of 15 characters.</title>
+ <title>RHEL-08-020021 - RHEL 8 must prevent system messages from being presented when three unsuccessful logon attempts occur.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
+ <description>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.
-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 increase exponentially the time and/or resources required to compromise the password.
+In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in /etc/passwd and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout.
-The DoD minimum password requirement is 15 characters.</description>
+From "faillock.conf" man pages: Note that the default directory that "pam_faillock" uses is usually cleared on system boot so the access will be also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21000" />
+ <criteria operator="OR" comment="/etc/security/faillock.conf has audit configured or RHEL version is 8.1 or older.">
+ <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:18906" />
+ <criterion comment="audit is set in /etc/security/faillock.conf" test_ref="oval:mil.disa.stig.rhel8:tst:18907" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:211" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:190" version="2">
<metadata>
- <title>RHEL-08-020260 - RHEL 8 account identifiers (individuals, groups, roles, and devices) must be disabled after 35 days of inactivity.</title>
+ <title>RHEL-08-020022 - RHEL 8 must include root when automatically locking an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained.
+ <description>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.
-RHEL 8 needs to track periods of inactivity and disable application identifiers after 35 days of inactivity.</description>
+RHEL 8 can utilize the "pam_faillock.so" for this purpose. Note that manual changes to the listed files may be overwritten by the "authselect" program.
+
+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 also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21100" />
+ <criteria operator="OR" comment="Either system-auth and password-auth are properly configured to use pam_faillock.so with the even_deny_root option or RHEL version is 8.2 or newer.">
+ <criterion comment="The RHEL 8 version is RHEL 8.2 or newer" test_ref="oval:mil.disa.stig.rhel8:tst:19002" />
+ <criteria operator="AND" comment="Check that system-auth and password-auth are configured to use even_deny_root.">
+ <criterion comment="pam_faillock.so preauth even_deny_root is in system-auth" test_ref="oval:mil.disa.stig.rhel8:tst:19000" />
+ <criterion comment="pam_faillock.so preauth even_deny_root is in password-auth" test_ref="oval:mil.disa.stig.rhel8:tst:19001" />
+ </criteria>
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:212" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:191" version="3">
<metadata>
- <title>RHEL-08-020280 - All RHEL 8 passwords must contain at least one special character.</title>
+ <title>RHEL-08-020023 - RHEL 8 must include root when automatically locking an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
+ <description>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.
-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.
+In RHEL 8.2 the "/etc/security/faillock.conf" file was incorporated to centralize the configuration of the pam_faillock.so module. Also introduced is a "local_users_only" option that will only track failed user authentication attempts for local users in /etc/passwd and ignore centralized (AD, IdM, LDAP, etc.) users to allow the centralized platform to solely manage user lockout.
-RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. Note that to require special characters without degrading the "minlen" value, the credit value must be expressed as a negative number in "/etc/security/pwquality.conf".</description>
+From "faillock.conf" man pages: Note that the default directory that "pam_faillock" uses is usually cleared on system boot so the access will be also re-enabled after system reboot. If that is undesirable a different tally directory must be set with the "dir" option.</description>
</metadata>
- <criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21200" />
+ <criteria operator="OR" comment="Both system-auth and password-auth are properly configured to use pam_faillock.so and even_deny_root or RHEL version is 8.1 or older.">
+ <criterion comment="The RHEL 8 version is RHEL 8.1 or RHEL 8.0" test_ref="oval:mil.disa.stig.rhel8:tst:19106" />
+ <criterion comment="even_deny_root is set in /etc/security/faillock.conf" test_ref="oval:mil.disa.stig.rhel8:tst:19107" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:214" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:192" class="compliance" version="3">
<metadata>
- <title>RHEL-08-020300 - RHEL 8 must prevent the use of dictionary words for passwords.</title>
+ <title>RHEL-08-020024 - RHEL 8 must limit the number of concurrent sessions to ten for all accounts and/or account types.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>If RHEL 8 allows the user to select passwords based on dictionary words, this increases the chances of password compromise by increasing the opportunity for successful guesses, and brute-force attacks.</description>
+ <description>Operating system management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the number of allowed users and sessions per user is helpful in reducing the risks related to DoS attacks.
+
+This requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions should be defined based on mission needs and the operational environment for each system.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21400" />
+ <criterion comment="limits.conf:maxlogins is set to 10 or less by default" test_ref="oval:mil.disa.stig.rhel8:tst:19200" />
+ <criterion comment="limits.conf:maxlogins is set to 10 or less for non-default domains" test_ref="oval:mil.disa.stig.rhel8:tst:19201" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:215" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:193" class="compliance" version="2">
<metadata>
- <title>RHEL-08-020310 - RHEL 8 must enforce a delay of at least four seconds between logon prompts following a failed logon attempt.</title>
+ <title>RHEL-08-020040 - RHEL 8 must enable a user session lock until that user re-establishes access using established identification and authentication procedures for command line sessions.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Configuring the operating system to implement organization-wide security implementation guides and security checklists verifies compliance with federal standards and establishes a common security baseline across the DoD that reflects the most restrictive security posture consistent with operational requirements.
+ <description>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.
-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, and directory permission settings; and settings for functions, ports, protocols, services, and remote connections.</description>
+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, RHEL 8 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.
+
+Tmux is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen. Red Hat endorses tmux as the recommended session controlling package.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21500" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19301" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:216" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:194" class="compliance" version="2">
<metadata>
- <title>RHEL-08-020330 - RHEL 8 must not have accounts configured with blank or null passwords.</title>
+ <title>RHEL-08-020041 - RHEL 8 must ensure session control is automatically started at shell initialization.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.</description>
+ <description>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, RHEL 8 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.
+
+Tmux is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen. Red Hat endorses tmux as the recommended session controlling package.</description>
</metadata>
- <criteria comment="Empty passwords must not be used during authentication.">
- <criterion comment="The PermitEmptyPasswords option is not set to yes in /etc/ssh/sshd_config." test_ref="oval:mil.disa.stig.rhel8:tst:21602" />
+ <criteria>
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19400" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19401" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:218" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:195" class="compliance" version="1">
<metadata>
- <title>RHEL-08-020350 - RHEL 8 must display the date and time of the last successful account logon upon an SSH logon.</title>
+ <title>RHEL-08-020042 - RHEL 8 must prevent users from disabling session control mechanisms.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Providing users with feedback on when account accesses via SSH last occurred facilitates user recognition and reporting of unauthorized account use.</description>
+ <description>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, RHEL 8 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.
+
+Tmux is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen. Red Hat endorses tmux as the recommended session controlling package.</description>
</metadata>
- <criteria comment="OpenSSH is installed AND PrintLastLog == yes">
- <extend_definition comment="OpenSSH is installed" definition_ref="oval:mil.disa.stig.rhel8:def:324" />
- <criterion comment="/etc/ssh/sshd_config:PrintLastLog == yes" test_ref="oval:mil.disa.stig.rhel8:tst:21800" />
+ <criteria>
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19500" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:219" class="compliance" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:196" version="2">
<metadata>
- <title>RHEL-08-020351 - RHEL 8 must define default permissions for all authenticated users in such a way that the user can only read and modify their own files.</title>
+ <title>RHEL-08-020100 - RHEL 8 must ensure the password complexity module is enabled in the password-auth file.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Setting the most restrictive default permissions ensures that when new accounts are created, they do not have unnecessary access.</description>
+ <description>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. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.
+
+RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. This is set in both:
+/etc/pam.d/password-auth
+/etc/pam.d/system-auth</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21900" />
+ <criterion comment="The pam_pwquality module is included in password-auth." test_ref="oval:mil.disa.stig.rhel8:tst:19600" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:220" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:197" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030000 - The RHEL 8 audit system must be configured to audit the execution of privileged functions and prevent all software from executing at higher privilege levels than users executing the software.</title>
+ <title>RHEL-08-020110 - RHEL 8 must enforce password complexity by requiring that at least one uppercase character be used.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.</description>
+ <description>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.
+
+RHEL 8 utilizes pwquality as a mechanism to enforce password complexity. Note that in order to require uppercase characters, without degrading the "minlen" value, the credit value must be expressed as a negative number in "/etc/security/pwquality.conf".</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of execve syscall comparing uids" test_ref="oval:mil.disa.stig.rhel8:tst:22000" />
- <criterion comment="Audit 64-bit invocations of execve syscall comparing uids" test_ref="oval:mil.disa.stig.rhel8:tst:22001" />
- <criterion comment="Audit 32-bit invocations of execve syscall comparing gids" test_ref="oval:mil.disa.stig.rhel8:tst:22002" />
- <criterion comment="Audit 64-bit invocations of execve syscall comparing gids" test_ref="oval:mil.disa.stig.rhel8:tst:22003" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19700" comment="at least one uppercase character is required" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:222" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:198" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030020 - The RHEL 8 System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) must be alerted of an audit processing failure event.</title>
+ <title>RHEL-08-020120 - RHEL 8 must enforce password complexity by requiring that at least one lower-case character be used.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
+ <description>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.
-Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded.
+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.
-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.</description>
+RHEL 8 utilizes pwquality as a mechanism to enforce password complexity. Note that in order to require lower-case characters without degrading the "minlen" value, the credit value must be expressed as a negative number in "/etc/security/pwquality.conf".</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22200" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19800" comment="at least one lowercase character is required" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:223" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:199" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030040 - The RHEL 8 System must take appropriate action when an audit processing failure occurs.</title>
+ <title>RHEL-08-020130 - RHEL 8 must enforce password complexity by requiring that at least one numeric character be used.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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.
+ <description>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.
-Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded.
+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.
-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.</description>
+RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. Note that in order to require numeric characters, without degrading the minlen value, the credit value must be expressed as a negative number in "/etc/security/pwquality.conf".</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22300" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:19900" comment="at least one numeric character is required" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:224" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:200" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030050 - The RHEL 8 System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) must be alerted when the audit storage volume is full.</title>
+ <title>RHEL-08-020140 - RHEL 8 must require the maximum number of repeating characters of the same character class be limited to four when passwords are changed.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>It is critical that when RHEL 8 is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.
-
-When availability is an overriding concern, other approved actions in response to an audit failure are as follows:
+ <description>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.
-1) If the failure was caused by the lack of audit record storage capacity, RHEL 8 must continue generating audit records if possible (automatically restarting the audit service if necessary) and overwriting the oldest audit records in a first-in-first-out manner.
+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.
-2) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, RHEL 8 must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.</description>
+RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. The "maxclassrepeat" option sets the maximum number of allowed same consecutive characters in the same class in the new password.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22400" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20000" comment="the maximum number of repeating characters of the same character class must be limited to four when passwords are changed" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:225" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:201" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030060 - The RHEL 8 audit system must take appropriate action when the audit storage volume is full.</title>
+ <title>RHEL-08-020150 - RHEL 8 must require the maximum number of repeating characters be limited to three when passwords are changed.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>It is critical that when RHEL 8 is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.
-
-When availability is an overriding concern, other approved actions in response to an audit failure are as follows:
+ <description>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.
-1) If the failure was caused by the lack of audit record storage capacity, RHEL 8 must continue generating audit records if possible (automatically restarting the audit service if necessary) and overwriting the oldest audit records in a first-in-first-out manner.
+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.
-2) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, RHEL 8 must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.</description>
+RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. The "maxrepeat" option sets the maximum number of allowed same consecutive characters in a new password.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22500" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20100" comment="the maximum number of repeating characters must be limited to three when passwords are changed" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:226" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:202" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030061 - The RHEL 8 audit system must audit local events.</title>
+ <title>RHEL-08-020160 - RHEL 8 must require the change of at least four character classes when passwords are changed.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+ <description>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.
-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.</description>
+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.
+
+RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. The "minclass" option sets the minimum number of required classes of characters for the new password (digits, uppercase, lowercase, others).</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22600" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20200" comment="passwords must contain at least four character classes" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:227" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:203" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030062 - RHEL 8 must label all off-loaded audit logs before sending them to the central log server.</title>
+ <title>RHEL-08-020170 - RHEL 8 must require the change of at least 8 characters when passwords are changed.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, 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.
+ <description>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.
-Enriched logging is needed to determine who, what, and when events occur on a system. Without this, determining root cause of an event will be much more difficult.
+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.
-When audit logs are not labeled before they are sent to a central log server, the audit data will not be able to be analyzed and tied back to the correct system.</description>
+RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. The "difok" option sets the number of characters in a password that must not be present in the old password.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22700" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20300" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:228" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:204" version="4">
<metadata>
- <title>RHEL-08-030063 - RHEL 8 must resolve audit information before writing to disk.</title>
+ <title>RHEL-08-020180 - RHEL 8 passwords must have a 24 hours/1 day minimum password lifetime restriction in /etc/shadow.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, 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.
-
-Enriched logging aids in making sense of who, what, and when events occur on a system. Without this, determining root cause of an event will be much more difficult.</description>
+ <description>Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22800" />
+ <criterion comment="Root does not have a minimum password age of 0 or blank" test_ref="oval:mil.disa.stig.rhel8:tst:20400" />
+ <criterion comment="Non-system users do not have a minimum password age of 0 or blank" test_ref="oval:mil.disa.stig.rhel8:tst:20401" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:229" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:205" class="compliance" version="2">
<metadata>
- <title>RHEL-08-030070 - RHEL 8 audit logs must have a mode of 0600 or less permissive to prevent unauthorized read access.</title>
+ <title>RHEL-08-020190 - RHEL 8 passwords for new users or password changes must have a 24 hours/1 day minimum password lifetime restriction in /etc/logins.def.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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 RHEL 8 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.</description>
+ <description>Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22900" comment="audit log has mode 0600 or less permissive" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20500" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:230" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:206" class="compliance" version="2">
<metadata>
- <title>RHEL-08-030080 - RHEL 8 audit logs must be owned by root to prevent unauthorized read access.</title>
+ <title>RHEL-08-020200 - RHEL 8 user account passwords must have a 60-day maximum password lifetime restriction.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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 RHEL 8 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.</description>
+ <description>Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If RHEL 8 does not limit the lifetime of passwords and force users to change their passwords, there is the risk that RHEL 8 passwords could be compromised.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23000" comment="audit logs are owned by root" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20600" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:231" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:207" version="5">
<metadata>
- <title>RHEL-08-030090 - RHEL 8 audit logs must be group-owned by root to prevent unauthorized read access.</title>
+ <title>RHEL-08-020210 - RHEL 8 user account passwords must be configured so that existing passwords are restricted to a 60-day maximum lifetime.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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 RHEL 8 activity.</description>
+ <description>Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If RHEL 8 does not limit the lifetime of passwords and force users to change their passwords, there is the risk that RHEL 8 passwords could be compromised.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23100" comment="audit logs are group-owned by root" />
+ <criterion comment="No password in /etc/shadow has a maximum password age of 0 or greater than 60" test_ref="oval:mil.disa.stig.rhel8:tst:20700" />
+ <criterion comment="Root password in /etc/shadow does not have a maximum password age of 0 or greater than 60" test_ref="oval:mil.disa.stig.rhel8:tst:20701" />
+ <criterion comment="Non-system users do not have a blank entry in /etc/shadow for maximum password age" test_ref="oval:mil.disa.stig.rhel8:tst:20702" />
+ <criterion comment="Root does not have a blank entry in /etc/shadow for maximum password age" test_ref="oval:mil.disa.stig.rhel8:tst:20703" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:232" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:208" class="compliance" version="4">
<metadata>
- <title>RHEL-08-030100 - RHEL 8 audit log directory must be owned by root to prevent unauthorized read access.</title>
+ <title>RHEL-08-020220 - RHEL 8 must be configured in the password-auth file to prohibit password reuse for a minimum of five generations.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
+ <description>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 reuse their password consecutively when that password has exceeded its defined lifetime, the end result is a password that is not changed per policy requirements.
-Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 activity.</description>
+RHEL 8 utilizes "pwhistory" consecutively as a mechanism to prohibit password reuse. This is set in both:
+/etc/pam.d/password-auth
+/etc/pam.d/system-auth.
+
+Note that manual changes to the listed files may be overwritten by the "authselect" program.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23200" comment="audit log directories are owned by root" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20801" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:233" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:209" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030110 - RHEL 8 audit log directory must be group-owned by root to prevent unauthorized read access.</title>
+ <title>RHEL-08-020230 - RHEL 8 passwords must have a minimum of 15 characters.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
+ <description>The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
-Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 activity.</description>
+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 increase exponentially the time and/or resources required to compromise the password.
+
+RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. Configurations are set in the "etc/security/pwquality.conf" file.
+
+The "minlen", sometimes noted as minimum length, acts as a "score" of complexity based on the credit components of the "pwquality" module. By setting the credit components to a negative value, not only will those components be required, they will not count towards the total "score" of "minlen". This will enable "minlen" to require a 15-character minimum.
+
+The DoD minimum password requirement is 15 characters.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23300" comment="audit log directories are group-owned by root" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:20900" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:234" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:210" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030120 - RHEL 8 audit log directory must have a mode of 0700 or less permissive to prevent unauthorized read access.</title>
+ <title>RHEL-08-020231 - RHEL 8 passwords for new users must have a minimum of 15 characters.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
+ <description>The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
-Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 system activity.</description>
+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 increase exponentially the time and/or resources required to compromise the password.
+
+The DoD minimum password requirement is 15 characters.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23400" comment="audit log directory has a mode of 0700 or less permissive" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21000" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:235" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:211" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030121 - RHEL 8 audit system must protect auditing rules from unauthorized change.</title>
+ <title>RHEL-08-020260 - RHEL 8 account identifiers (individuals, groups, roles, and devices) must be disabled after 35 days of inactivity.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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 RHEL 8 system activity.
+ <description>Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained.
-In immutable mode, unauthorized users cannot execute changes to the audit system to potentially hide malicious activity and then put the audit rules back. A system reboot would be noticeable and a system administrator could then investigate the unauthorized changes.</description>
+RHEL 8 needs to track periods of inactivity and disable application identifiers after 35 days of inactivity.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23500" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21100" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:236" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:212" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030122 - RHEL 8 audit system must protect logon UIDs from unauthorized change.</title>
+ <title>RHEL-08-020280 - All RHEL 8 passwords must contain at least one special character.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
+ <description>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.
-Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 system activity.
+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.
-In immutable mode, unauthorized users cannot execute changes to the audit system to potentially hide malicious activity and then put the audit rules back. A system reboot would be noticeable and a system administrator could then investigate the unauthorized changes.</description>
+RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. Note that to require special characters without degrading the "minlen" value, the credit value must be expressed as a negative number in "/etc/security/pwquality.conf".</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23600" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21200" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:237" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:214" class="compliance" version="2">
<metadata>
- <title>RHEL-08-030130 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.</title>
+ <title>RHEL-08-020300 - RHEL 8 must prevent the use of dictionary words for passwords.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs 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).</description>
+ <description>If RHEL 8 allows the user to select passwords based on dictionary words, this increases the chances of password compromise by increasing the opportunity for successful guesses, and brute-force attacks.</description>
</metadata>
- <criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit modifications to /etc/shadow" test_ref="oval:mil.disa.stig.rhel8:tst:23700" />
+ <criteria operator="OR">
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21400" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21401" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:238" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:215" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030140 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/security/opasswd.</title>
+ <title>RHEL-08-020310 - RHEL 8 must enforce a delay of at least four seconds between logon prompts following a failed logon attempt.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Configuring the operating system to implement organization-wide security implementation guides and security checklists verifies compliance with federal standards and establishes a common security baseline across the DoD that reflects the most restrictive security posture consistent with operational requirements.
-Audit records can be generated from various components within the information system (e.g., module or policy filter).</description>
+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, and directory permission settings; and settings for functions, ports, protocols, services, and remote connections.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit modifications to /etc/security/opasswd" test_ref="oval:mil.disa.stig.rhel8:tst:23800" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21500" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:239" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:216" version="2">
<metadata>
- <title>RHEL-08-030150 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd.</title>
+ <title>RHEL-08-020330 - RHEL 8 must not have accounts configured with blank or null passwords.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs 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).</description>
+ <description>If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.</description>
</metadata>
- <criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit modifications to /etc/passwd" test_ref="oval:mil.disa.stig.rhel8:tst:23900" />
+ <criteria comment="Empty passwords must not be used during authentication.">
+ <criterion comment="The PermitEmptyPasswords option is not set to yes in /etc/ssh/sshd_config." test_ref="oval:mil.disa.stig.rhel8:tst:21602" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:240" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:218" version="2">
<metadata>
- <title>RHEL-08-030160 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow.</title>
+ <title>RHEL-08-020350 - RHEL 8 must display the date and time of the last successful account logon upon an SSH logon.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs 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).</description>
+ <description>Providing users with feedback on when account accesses via SSH last occurred facilitates user recognition and reporting of unauthorized account use.</description>
</metadata>
- <criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit modifications to /etc/gshadow" test_ref="oval:mil.disa.stig.rhel8:tst:24000" />
+ <criteria comment="OpenSSH is installed AND PrintLastLog == yes">
+ <extend_definition comment="OpenSSH is installed" definition_ref="oval:mil.disa.stig.rhel8:def:324" />
+ <criterion comment="/etc/ssh/sshd_config:PrintLastLog == yes" test_ref="oval:mil.disa.stig.rhel8:tst:21800" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:241" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:219" class="compliance" version="2">
<metadata>
- <title>RHEL-08-030170 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group.</title>
+ <title>RHEL-08-020351 - RHEL 8 must define default permissions for all authenticated users in such a way that the user can only read and modify their own files.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs 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).</description>
+ <description>Setting the most restrictive default permissions ensures that when new accounts are created, they do not have unnecessary access.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit modifications to /etc/group" test_ref="oval:mil.disa.stig.rhel8:tst:24100" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:21900" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:242" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:220" version="2">
<metadata>
- <title>RHEL-08-030171 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers.</title>
+ <title>RHEL-08-030000 - The RHEL 8 audit system must be configured to audit the execution of privileged functions and prevent all software from executing at higher privilege levels than users executing the software.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs 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).</description>
+ <description>Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.</description>
</metadata>
<criteria>
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:24200" comment="Audit modifications to /etc/sudoers" />
+ <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
+ <criterion comment="Audit 32-bit invocations of execve syscall comparing uids" test_ref="oval:mil.disa.stig.rhel8:tst:22000" />
+ <criterion comment="Audit 64-bit invocations of execve syscall comparing uids" test_ref="oval:mil.disa.stig.rhel8:tst:22001" />
+ <criterion comment="Audit 32-bit invocations of execve syscall comparing gids" test_ref="oval:mil.disa.stig.rhel8:tst:22002" />
+ <criterion comment="Audit 64-bit invocations of execve syscall comparing gids" test_ref="oval:mil.disa.stig.rhel8:tst:22003" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:243" class="compliance" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:222" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030172 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers.d/.</title>
+ <title>RHEL-08-030020 - The RHEL 8 System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) must be alerted of an audit processing failure event.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>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 records can be generated from various components within the information system (e.g., module or policy filter).</description>
+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.</description>
</metadata>
<criteria>
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:24300" comment="Audit modifications to /etc/sudoers.d/" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22200" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:244" version="4">
+ <definition id="oval:mil.disa.stig.rhel8:def:223" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030180 - The RHEL 8 audit package must be installed.</title>
+ <title>RHEL-08-030040 - The RHEL 8 System must take appropriate action when an audit processing failure occurs.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+ <description>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 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.
+Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded.
-Associating event types with detected events in RHEL 8 audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured RHEL 8 system.</description>
+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.</description>
</metadata>
<criteria>
- <criterion comment="package audit is installed" test_ref="oval:mil.disa.stig.rhel8:tst:24400" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22300" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:245" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:225" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030190 - Successful/unsuccessful uses of the su command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030060 - The RHEL 8 audit system must take appropriate action when the audit storage volume is full.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>It is critical that when RHEL 8 is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "su" command allows a user to run commands with a substitute user and group ID.
+When availability is an overriding concern, other approved actions in response to an audit failure are as follows:
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+1) If the failure was caused by the lack of audit record storage capacity, RHEL 8 must continue generating audit records if possible (automatically restarting the audit service if necessary) and overwriting the oldest audit records in a first-in-first-out manner.
+
+2) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, RHEL 8 must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit invocations of /usr/bin/su" test_ref="oval:mil.disa.stig.rhel8:tst:24500" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22500" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:246" class="compliance" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:226" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030200 - The RHEL 8 audit system must be configured to audit any usage of the lremovexattr system call.</title>
+ <title>RHEL-08-030061 - The RHEL 8 audit system must audit local events.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs 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). "Lremovexattr" is a system call that removes extended attributes. This is used for removal of extended attributes from symbolic links.
+ <description>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+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.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of lremovexattr syscall" test_ref="oval:mil.disa.stig.rhel8:tst:24600" />
- <criterion comment="Audit 64-bit invocations of lremovexattr syscall" test_ref="oval:mil.disa.stig.rhel8:tst:24601" />
- <criterion comment="Audit 32-bit invocations of lremovexattr syscall by root" test_ref="oval:mil.disa.stig.rhel8:tst:24602" />
- <criterion comment="Audit 64-bit invocations of lremovexattr syscall by root" test_ref="oval:mil.disa.stig.rhel8:tst:24603" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22600" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:247" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:227" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030210 - The RHEL 8 audit system must be configured to audit any usage of the removexattr system call</title>
+ <title>RHEL-08-030062 - RHEL 8 must label all off-loaded audit logs before sending them to the central log server.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). "Removexattr" is a system call that removes extended attributes.
+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.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+Enriched logging is needed to determine who, what, and when events occur on a system. Without this, determining root cause of an event will be much more difficult.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219, SRG-OS-000466-GPOS-00210</description>
+When audit logs are not labeled before they are sent to a central log server, the audit data will not be able to be analyzed and tied back to the correct system.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of removexattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:24700" />
- <criterion comment="Audit 64-bit invocations of removexattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:24701" />
- <criterion comment="Audit 32-bit invocations of removexattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:24702" />
- <criterion comment="Audit 64-bit invocations of removexattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:24703" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22700" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:248" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:228" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030220 - The RHEL 8 audit system must be configured to audit any usage of the lsetxattr system call.</title>
+ <title>RHEL-08-030063 - RHEL 8 must resolve audit information before writing to disk.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). "Lsetxattr" is a system call used to set an extended attribute value. This is used to set extended attributes on a symbolic link.
+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.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+Enriched logging aids in making sense of who, what, and when events occur on a system. Without this, determining root cause of an event will be much more difficult.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of lsetxattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:24800" />
- <criterion comment="Audit 64-bit invocations of lsetxattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:24801" />
- <criterion comment="Audit 32-bit invocations of lsetxattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:24802" />
- <criterion comment="Audit 64-bit invocations of lsetxattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:24803" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22800" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:249" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:229" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030230 - The RHEL 8 audit system must be configured to audit any usage of the fsetxattr system call</title>
+ <title>RHEL-08-030070 - RHEL 8 audit logs must have a mode of 0600 or less permissive to prevent unauthorized read access.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Audit records can be generated from various components within the information system (e.g., module or policy filter). "Fsetxattr" is a system call used to set an extended attribute value. This is used to set extended attributes on a file.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The auid representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+ <description>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 RHEL 8 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.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219</description>
+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.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of fsetxattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:24900" />
- <criterion comment="Audit 64-bit invocations of fsetxattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:24901" />
- <criterion comment="Audit 32-bit invocations of fsetxattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:24902" />
- <criterion comment="Audit 64-bit invocations of fsetxattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:24903" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:22900" comment="audit log has mode 0600 or less permissive" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:250" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:230" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030240 - The RHEL 8 audit system must be configured to audit any usage of the fremovexattr system call</title>
+ <title>RHEL-08-030080 - RHEL 8 audit logs must be owned by root to prevent unauthorized read access.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs 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). "Fremovexattr" is a system call that removes extended attributes. This is used for removal of extended attributes from a file.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+ <description>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 RHEL 8 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.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219, SRG-OS-000466-GPOS-00210</description>
+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.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of fremovexattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:25000" />
- <criterion comment="Audit 64-bit invocations of fremovexattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:25001" />
- <criterion comment="Audit 32-bit invocations of fremovexattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:25002" />
- <criterion comment="Audit 64-bit invocations of fremovexattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:25003" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23000" comment="audit logs are owned by root" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:251" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:231" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030250 - Successful/unsuccessful uses of the chage command in RHEL 8 must generate an audit record</title>
+ <title>RHEL-08-030090 - RHEL 8 audit logs must be group-owned by root to prevent unauthorized read access.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs 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 "chage" command is used to change or view user password expiry information.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+ <description>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215</description>
+Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 activity.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit invocations of /usr/bin/chage" test_ref="oval:mil.disa.stig.rhel8:tst:25100" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23100" comment="audit logs are group-owned by root" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:252" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:232" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030260 - Successful/unsuccessful uses of the chcon command in RHEL 8 must generate an audit record</title>
+ <title>RHEL-08-030100 - RHEL 8 audit log directory must be owned by root to prevent unauthorized read access.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs 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 "chcon" command is used to change file SELinux security context.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+ <description>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215</description>
+Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 activity.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit invocations of /usr/bin/chcon" test_ref="oval:mil.disa.stig.rhel8:tst:25200" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23200" comment="audit log directories are owned by root" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:253" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:233" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030270 - The RHEL 8 audit system must be configured to audit any usage of the setxattr system call.</title>
+ <title>RHEL-08-030110 - RHEL 8 audit log directory must be group-owned by root to prevent unauthorized read access.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs 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). "Setxattr" is a system call used to set an extended attribute value.
+ <description>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 activity.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of setxattr syscall" test_ref="oval:mil.disa.stig.rhel8:tst:25300" />
- <criterion comment="Audit 64-bit invocations of setxattr syscall" test_ref="oval:mil.disa.stig.rhel8:tst:25301" />
- <criterion comment="Audit 32-bit invocations of setxattr syscall by root" test_ref="oval:mil.disa.stig.rhel8:tst:25302" />
- <criterion comment="Audit 64-bit invocations of setxattr syscall by root" test_ref="oval:mil.disa.stig.rhel8:tst:25303" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23300" comment="audit log directories are group-owned by root" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:254" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:234" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030280 - Successful/unsuccessful uses of the ssh-agent in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030120 - RHEL 8 audit log directory must have a mode of 0700 or less permissive to prevent unauthorized read access.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs 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 "ssh-agent" is a program to hold private keys used for public key authentication.
+ <description>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 system activity.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit invocations of /usr/bin/ssh-agent" test_ref="oval:mil.disa.stig.rhel8:tst:25400" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23400" comment="audit log directory has a mode of 0700 or less permissive" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:255" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:235" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030290 - Successful/unsuccessful uses of the passwd command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030121 - RHEL 8 audit system must protect auditing rules from unauthorized change.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "passwd" command is used to change passwords for user accounts.
+Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 system activity.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+In immutable mode, unauthorized users cannot execute changes to the audit system to potentially hide malicious activity and then put the audit rules back. A system reboot would be noticeable and a system administrator could then investigate the unauthorized changes.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit invocations of /usr/bin/passwd" test_ref="oval:mil.disa.stig.rhel8:tst:25500" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23500" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:256" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:236" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030300 - Successful/unsuccessful uses of the mount command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030122 - RHEL 8 audit system must protect logon UIDs from unauthorized change.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "mount" command is used to mount a filesystem.
+Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit RHEL 8 system activity.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+In immutable mode, unauthorized users cannot execute changes to the audit system to potentially hide malicious activity and then put the audit rules back. A system reboot would be noticeable and a system administrator could then investigate the unauthorized changes.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit executions of /usr/bin/mount" test_ref="oval:mil.disa.stig.rhel8:tst:25602" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:23600" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:257" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:237" version="2">
<metadata>
- <title>RHEL-08-030301 - Successful/unsuccessful uses of the umount command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030130 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "umount" command is used to unmount a filesystem.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+Audit records can be generated from various components within the information system (e.g., module or policy filter).</description>
</metadata>
<criteria>
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:25700" comment="Audit invocations of /usr/bin/umount" />
+ <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
+ <criterion comment="Audit modifications to /etc/shadow" test_ref="oval:mil.disa.stig.rhel8:tst:23700" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:258" class="compliance" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:238" version="2">
<metadata>
- <title>RHEL-08-030302 - Successful/unsuccessful uses of the mount syscall in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030140 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/security/opasswd.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "mount" syscall is used to mount a filesystem.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+Audit records can be generated from various components within the information system (e.g., module or policy filter).</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of mount syscall" test_ref="oval:mil.disa.stig.rhel8:tst:25800" />
- <criterion comment="Audit 64-bit invocations of mount syscall" test_ref="oval:mil.disa.stig.rhel8:tst:25801" />
+ <criterion comment="Audit modifications to /etc/security/opasswd" test_ref="oval:mil.disa.stig.rhel8:tst:23800" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:259" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:239" version="2">
<metadata>
- <title>RHEL-08-030310 - Successful/unsuccessful uses of the unix_update in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030150 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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. "Unix_update" is a helper program for the "pam_unix" module that updates the password for a given user. It is not intended to be run directly from the command line and logs a security violation if done so.
+ <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+Audit records can be generated from various components within the information system (e.g., module or policy filter).</description>
</metadata>
<criteria>
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:25900" comment="Audit invocations of /usr/sbin/unix_update" />
+ <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
+ <criterion comment="Audit modifications to /etc/passwd" test_ref="oval:mil.disa.stig.rhel8:tst:23900" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:260" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:240" version="2">
<metadata>
- <title>RHEL-08-030311 - Successful/unsuccessful uses of postdrop in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030160 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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 "postdrop" command creates a file in the maildrop directory and copies its standard input to the file.
+ <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+Audit records can be generated from various components within the information system (e.g., module or policy filter).</description>
</metadata>
<criteria>
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26000" comment="Audit invocations of /usr/sbin/postdrop" />
+ <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
+ <criterion comment="Audit modifications to /etc/gshadow" test_ref="oval:mil.disa.stig.rhel8:tst:24000" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:261" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:241" version="2">
<metadata>
- <title>RHEL-08-030312 - Successful/unsuccessful uses of postqueue in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030170 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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 "postqueue" command implements the Postfix user interface for queue management.
+ <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+Audit records can be generated from various components within the information system (e.g., module or policy filter).</description>
</metadata>
<criteria>
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26100" comment="Audit invocations of /usr/sbin/postqueue" />
+ <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
+ <criterion comment="Audit modifications to /etc/group" test_ref="oval:mil.disa.stig.rhel8:tst:24100" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:262" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:242" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030313 - Successful/unsuccessful uses of semanage in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030171 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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 "semanage" command is used to configure certain elements of SELinux policy without requiring modification to or recompilation from policy sources.
+ <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+Audit records can be generated from various components within the information system (e.g., module or policy filter).</description>
</metadata>
<criteria>
<extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26200" comment="Audit invocations of /usr/sbin/semanage" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:24200" comment="Audit modifications to /etc/sudoers" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:263" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:243" class="compliance" version="2">
<metadata>
- <title>RHEL-08-030314 - Successful/unsuccessful uses of setfiles in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030172 - RHEL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers.d/.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>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 "setfiles" command is primarily used to initialize the security context fields (extended attributes) on one or more filesystems (or parts of them). Usually it is initially run as part of the SELinux installation process (a step commonly known as labeling).
+ <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+Audit records can be generated from various components within the information system (e.g., module or policy filter).</description>
</metadata>
<criteria>
<extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26300" comment="Audit invocations of /usr/sbin/setfiles" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:24300" comment="Audit modifications to /etc/sudoers.d/" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:264" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:244" version="4">
<metadata>
- <title>RHEL-08-030315 - Successful/unsuccessful uses of userhelper in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030180 - The RHEL 8 audit package must be installed.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+ <description>Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-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 "userhelper" command is not intended to be run interactively. "Userhelper" provides a basic interface to change a user's password, gecos information, and shell. The main difference between this program and its traditional equivalents (passwd, chfn, chsh) is that prompts are written to standard out to make it easy for a graphical user interface wrapper to interface to it as a child process.
+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.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+Associating event types with detected events in RHEL 8 audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured RHEL 8 system.</description>
</metadata>
<criteria>
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26400" comment="Audit invocations of /usr/sbin/userhelper" />
+ <criterion comment="package audit is installed" test_ref="oval:mil.disa.stig.rhel8:tst:24400" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:265" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:245" version="2">
<metadata>
- <title>RHEL-08-030316 - Successful/unsuccessful uses of setsebool in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030190 - Successful/unsuccessful uses of the su command in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+ <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-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 "setsebool" command sets the current state of a particular SELinux boolean or a list of booleans to a given value.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "su" command allows a user to run commands with a substitute user and group ID.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26500" comment="Audit invocations of /usr/sbin/setsebool" />
+ <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
+ <criterion comment="Audit invocations of /usr/bin/su" test_ref="oval:mil.disa.stig.rhel8:tst:24500" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:266" version="5">
+ <definition id="oval:mil.disa.stig.rhel8:def:246" class="compliance" version="4">
<metadata>
- <title>RHEL-08-030317 - Successful/unsuccessful uses of unix_chkpwd in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030200 - The RHEL 8 audit system must be configured to audit any usage of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr and lremovexattr system calls.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+ <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
-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 "unix_chkpwd" command is a helper program for the pam_unix module that verifies the password of the current user. It also checks password and account expiration dates in shadow. It is not intended to be run directly from the command line and logs a security violation if done so.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). "Setxattr" is a system call used to set an extended attribute value.
+"Fsetxattr" is a system call used to set an extended attribute value. This is used to set extended attributes on a file.
+"Lsetxattr" is a system call used to set an extended attribute value. This is used to set extended attributes on a symbolic link.
+"Removexattr" is a system call that removes extended attributes.
+"Fremovexattr" is a system call that removes extended attributes. This is used for removal of extended attributes from a file.
+"Lremovexattr" is a system call that removes extended attributes. This is used for removal of extended attributes from symbolic links.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+
+The system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when you have to since these affect performance. The more rules, the bigger the performance hit. You can help the performance, though, by combining syscalls into one rule whenever possible.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit invocations of /usr/sbin/unix_chkpwd" test_ref="oval:mil.disa.stig.rhel8:tst:26600" />
+ <criterion comment="Audit 32-bit invocations of setxattr syscall" test_ref="oval:mil.disa.stig.rhel8:tst:25300" />
+ <criterion comment="Audit 64-bit invocations of setxattr syscall" test_ref="oval:mil.disa.stig.rhel8:tst:25301" />
+ <criterion comment="Audit 32-bit invocations of setxattr syscall by root" test_ref="oval:mil.disa.stig.rhel8:tst:25302" />
+ <criterion comment="Audit 64-bit invocations of setxattr syscall by root" test_ref="oval:mil.disa.stig.rhel8:tst:25303" />
+ <criterion comment="Audit 32-bit invocations of fremovexattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:25000" />
+ <criterion comment="Audit 64-bit invocations of fremovexattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:25001" />
+ <criterion comment="Audit 32-bit invocations of fremovexattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:25002" />
+ <criterion comment="Audit 64-bit invocations of fremovexattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:25003" />
+ <criterion comment="Audit 32-bit invocations of fsetxattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:24900" />
+ <criterion comment="Audit 64-bit invocations of fsetxattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:24901" />
+ <criterion comment="Audit 32-bit invocations of fsetxattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:24902" />
+ <criterion comment="Audit 64-bit invocations of fsetxattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:24903" />
+ <criterion comment="Audit 32-bit invocations of lsetxattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:24800" />
+ <criterion comment="Audit 64-bit invocations of lsetxattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:24801" />
+ <criterion comment="Audit 32-bit invocations of lsetxattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:24802" />
+ <criterion comment="Audit 64-bit invocations of lsetxattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:24803" />
+ <criterion comment="Audit 32-bit invocations of removexattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:24700" />
+ <criterion comment="Audit 64-bit invocations of removexattr syscall (auid&gt;=1000)" test_ref="oval:mil.disa.stig.rhel8:tst:24701" />
+ <criterion comment="Audit 32-bit invocations of removexattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:24702" />
+ <criterion comment="Audit 64-bit invocations of removexattr syscall (auid=0)" test_ref="oval:mil.disa.stig.rhel8:tst:24703" />
+ <criterion comment="Audit 32-bit invocations of lremovexattr syscall" test_ref="oval:mil.disa.stig.rhel8:tst:24600" />
+ <criterion comment="Audit 64-bit invocations of lremovexattr syscall" test_ref="oval:mil.disa.stig.rhel8:tst:24601" />
+ <criterion comment="Audit 32-bit invocations of lremovexattr syscall by root" test_ref="oval:mil.disa.stig.rhel8:tst:24602" />
+ <criterion comment="Audit 64-bit invocations of lremovexattr syscall by root" test_ref="oval:mil.disa.stig.rhel8:tst:24603" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:267" version="4">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:251" version="3">
<metadata>
- <title>RHEL-08-030320 - Successful/unsuccessful uses of the ssh-keysign in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030250 - Successful/unsuccessful uses of the chage command in RHEL 8 must generate an audit record</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "ssh-keysign" program is an SSH helper program for host-based authentication.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "chage" command is used to change or view user password expiry information.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit invocations of /usr/libexec/openssh/ssh-keysign" test_ref="oval:mil.disa.stig.rhel8:tst:26700" />
+ <criterion comment="Audit invocations of /usr/bin/chage" test_ref="oval:mil.disa.stig.rhel8:tst:25100" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:268" version="3">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:252" version="3">
<metadata>
- <title>RHEL-08-030330 - Successful/unsuccessful uses of the setfacl command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030260 - Successful/unsuccessful uses of the chcon command in RHEL 8 must generate an audit record</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "setfacl" command is used to set file access control lists.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "chcon" command is used to change file SELinux security context.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit invocations of /usr/bin/setfacl" test_ref="oval:mil.disa.stig.rhel8:tst:26800" />
+ <criterion comment="Audit invocations of /usr/bin/chcon" test_ref="oval:mil.disa.stig.rhel8:tst:25200" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:269" class="compliance" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:254" version="3">
<metadata>
- <title>RHEL-08-030340 - Successful/unsuccessful uses of the pam_timestamp_check command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030280 - Successful/unsuccessful uses of the ssh-agent in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "pam_timestamp_check" command is used to check if the default timestamp is valid.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "ssh-agent" is a program to hold private keys used for public key authentication.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26900" comment="Audit invocations of /usr/sbin/pam_timestamp_check" />
+ <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
+ <criterion comment="Audit invocations of /usr/bin/ssh-agent" test_ref="oval:mil.disa.stig.rhel8:tst:25400" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:270" version="3">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:255" version="3">
<metadata>
- <title>RHEL-08-030350 - Successful/unsuccessful uses of the newgrp command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030290 - Successful/unsuccessful uses of the passwd command in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "newgrp" command is used to change the current group ID during a login session.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "passwd" command is used to change passwords for user accounts.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit invocations of /usr/bin/newgrp" test_ref="oval:mil.disa.stig.rhel8:tst:27000" />
+ <criterion comment="Audit invocations of /usr/bin/passwd" test_ref="oval:mil.disa.stig.rhel8:tst:25500" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:271" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:256" version="3">
<metadata>
- <title>RHEL-08-030360 - Successful/unsuccessful uses of the init_module command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030300 - Successful/unsuccessful uses of the mount command in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "init_module" command is used to load a kernel module.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "mount" command is used to mount a filesystem.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of init_module syscall" test_ref="oval:mil.disa.stig.rhel8:tst:27100" />
- <criterion comment="Audit 64-bit invocations of init_module syscall" test_ref="oval:mil.disa.stig.rhel8:tst:27101" />
+ <criterion comment="Audit executions of /usr/bin/mount" test_ref="oval:mil.disa.stig.rhel8:tst:25602" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:272" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:257" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030361 - Successful/unsuccessful uses of the rename command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030301 - Successful/unsuccessful uses of the umount command in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "rename" command will rename the specified files by replacing the first occurrence of expression in their name by replacement.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "umount" command is used to unmount a filesystem.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27200" comment="Audit 32-bit invocations of rename" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27201" comment="Audit 64-bit invocations of rename" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:25700" comment="Audit invocations of /usr/bin/umount" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:273" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:258" class="compliance" version="2">
<metadata>
- <title>RHEL-08-030362 - Successful/unsuccessful uses of the renameat command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030302 - Successful/unsuccessful uses of the mount syscall in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "renameat" command renames a file, moving it between directories if required.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "mount" syscall is used to mount a filesystem.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
- <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27300" comment="Audit 32-bit invocations of renameat" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27301" comment="Audit 64-bit invocations of renameat" />
+ <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
+ <criterion comment="Audit 32-bit invocations of mount syscall" test_ref="oval:mil.disa.stig.rhel8:tst:25800" />
+ <criterion comment="Audit 64-bit invocations of mount syscall" test_ref="oval:mil.disa.stig.rhel8:tst:25801" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:274" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:259" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030363 - Successful/unsuccessful uses of the rmdir command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030310 - Successful/unsuccessful uses of the unix_update in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "rmdir" command removes empty directories.
+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. "Unix_update" is a helper program for the "pam_unix" module that updates the password for a given user. It is not intended to be run directly from the command line and logs a security violation if done so.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27400" comment="Audit 32-bit invocations of rmdir" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27401" comment="Audit 64-bit invocations of rmdir" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:25900" comment="Audit invocations of /usr/sbin/unix_update" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:275" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:260" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030364 - Successful/unsuccessful uses of the unlink command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030311 - Successful/unsuccessful uses of postdrop in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "unlink" command deletes a name from the filesystem. If that name was the last link to a file and no processes have the file open, the file is deleted and the space it was using is made available for reuse.
+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 "postdrop" command creates a file in the maildrop directory and copies its standard input to the file.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27500" comment="Audit 32-bit invocations of unlink" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27501" comment="Audit 64-bit invocations of unlink" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26000" comment="Audit invocations of /usr/sbin/postdrop" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:276" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:261" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030365 - Successful/unsuccessful uses of the unlinkat command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030312 - Successful/unsuccessful uses of postqueue in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "unlinkat" system call operates in exactly the same way as either "unlink" or "rmdir" except for the differences described in the manual page.
+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 "postqueue" command implements the Postfix user interface for queue management.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27600" comment="Audit 32-bit invocations of unlinkat" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27601" comment="Audit 64-bit invocations of unlinkat" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26100" comment="Audit invocations of /usr/sbin/postqueue" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:277" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:262" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030370 - Successful/unsuccessful uses of the gpasswd command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030313 - Successful/unsuccessful uses of semanage in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "gpasswd" command is used to administer /etc/group and /etc/gshadow. Every group can have administrators, members and a password.
+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 "semanage" command is used to configure certain elements of SELinux policy without requiring modification to or recompilation from policy sources.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit invocations of /usr/bin/gpasswd" test_ref="oval:mil.disa.stig.rhel8:tst:27700" />
+ <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26200" comment="Audit invocations of /usr/sbin/semanage" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:278" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:263" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030380 - Successful/unsuccessful uses of the finit_module command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030314 - Successful/unsuccessful uses of setfiles in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "finit_module" command is used to load a kernel module.
+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 "setfiles" command is primarily used to initialize the security context fields (extended attributes) on one or more filesystems (or parts of them). Usually it is initially run as part of the SELinux installation process (a step commonly known as labeling).
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of finit_module syscall" test_ref="oval:mil.disa.stig.rhel8:tst:27800" />
- <criterion comment="Audit 64-bit invocations of finit_module syscall" test_ref="oval:mil.disa.stig.rhel8:tst:27801" />
+ <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26300" comment="Audit invocations of /usr/sbin/setfiles" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:279" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:264" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030390 - Successful/unsuccessful uses of the delete_module command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030315 - Successful/unsuccessful uses of userhelper in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "delete_module" command is used to unload a kernel module.
+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 "userhelper" command is not intended to be run interactively. "Userhelper" provides a basic interface to change a user's password, gecos information, and shell. The main difference between this program and its traditional equivalents (passwd, chfn, chsh) is that prompts are written to standard out to make it easy for a graphical user interface wrapper to interface to it as a child process.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of delete_module syscall" test_ref="oval:mil.disa.stig.rhel8:tst:27900" />
- <criterion comment="Audit 64-bit invocations of delete_module syscall" test_ref="oval:mil.disa.stig.rhel8:tst:27901" />
+ <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26400" comment="Audit invocations of /usr/sbin/userhelper" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:280" version="3">
+ <definition id="oval:mil.disa.stig.rhel8:def:265" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030400 - Successful/unsuccessful uses of the crontab command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030316 - Successful/unsuccessful uses of setsebool in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "crontab" command is used to maintain crontab files for individual users. Crontab is the program used to install, remove, or list the tables used to drive the cron daemon. This is similar to the task scheduler used in other operating systems.
+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 "setsebool" command sets the current state of a particular SELinux boolean or a list of booleans to a given value.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit invocations of /usr/bin/crontab" test_ref="oval:mil.disa.stig.rhel8:tst:28000" />
+ <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26500" comment="Audit invocations of /usr/sbin/setsebool" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:281" version="3">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:266" version="5">
<metadata>
- <title>RHEL-08-030410 - Successful/unsuccessful uses of the chsh command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030317 - Successful/unsuccessful uses of unix_chkpwd in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
- <description>Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
+ <description>Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-Audit records can be generated from various components within the information system (e.g., module or policy filter). The "chsh" command is used to change the login shell.
+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 "unix_chkpwd" command is a helper program for the pam_unix module that verifies the password of the current user. It also checks password and account expiration dates in shadow. It is not intended to be run directly from the command line and logs a security violation if done so.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit invocations of /usr/bin/chsh" test_ref="oval:mil.disa.stig.rhel8:tst:28100" />
+ <criterion comment="Audit invocations of /usr/sbin/unix_chkpwd" test_ref="oval:mil.disa.stig.rhel8:tst:26600" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:282" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:267" version="4">
<metadata>
- <title>RHEL-08-030420 - Successful/unsuccessful uses of the truncate command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030320 - Successful/unsuccessful uses of the ssh-keysign in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "truncate" and "ftruncate" functions are used to truncate a file to a specified length.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "ssh-keysign" program is an SSH helper program for host-based authentication.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of truncate syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28200" />
- <criterion comment="Audit 64-bit invocations of truncate syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28201" />
- <criterion comment="Audit 32-bit invocations of truncate syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28202" />
- <criterion comment="Audit 64-bit invocations of truncate syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28203" />
+ <criterion comment="Audit invocations of /usr/libexec/openssh/ssh-keysign" test_ref="oval:mil.disa.stig.rhel8:tst:26700" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:283" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:268" version="3">
<metadata>
- <title>RHEL-08-030430 - Successful/unsuccessful uses of the openat system call in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030330 - Successful/unsuccessful uses of the setfacl command in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "openat" system call opens a file specified by a relative pathname.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "setfacl" command is used to set file access control lists.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of openat syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28300" />
- <criterion comment="Audit 64-bit invocations of openat syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28301" />
- <criterion comment="Audit 32-bit invocations of openat syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28302" />
- <criterion comment="Audit 64-bit invocations of openat syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28303" />
+ <criterion comment="Audit invocations of /usr/bin/setfacl" test_ref="oval:mil.disa.stig.rhel8:tst:26800" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:284" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:269" class="compliance" version="1">
<metadata>
- <title>RHEL-08-030440 - Successful/unsuccessful uses of the open system call in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030340 - Successful/unsuccessful uses of the pam_timestamp_check command in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "open system" call opens a file specified by a pathname. If the specified file does not exist, it may optionally be created by "open".
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "pam_timestamp_check" command is used to check if the default timestamp is valid.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of open syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28400" />
- <criterion comment="Audit 64-bit invocations of open syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28401" />
- <criterion comment="Audit 32-bit invocations of open syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28402" />
- <criterion comment="Audit 64-bit invocations of open syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28403" />
+ <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:26900" comment="Audit invocations of /usr/sbin/pam_timestamp_check" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:285" version="3">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:270" version="3">
<metadata>
- <title>RHEL-08-030450 - Successful/unsuccessful uses of the open_by_handle_at system call in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030350 - Successful/unsuccessful uses of the newgrp command in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "name_to_handle_at" and "open_by_handle_at" system calls split the functionality of openat into two parts: "name_to_handle_at" returns an opaque handle that corresponds to a specified file; "open_by_handle_at" opens the file corresponding to a handle returned by a previous call to "name_to_handle_at" and returns an open file descriptor.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "newgrp" command is used to change the current group ID during a login session.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of open_by_handle_at syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28500" />
- <criterion comment="Audit 64-bit invocations of open_by_handle_at syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28501" />
- <criterion comment="Audit 32-bit invocations of open_by_handle_at syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28502" />
- <criterion comment="Audit 64-bit invocations of open_by_handle_at syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28503" />
+ <criterion comment="Audit invocations of /usr/bin/newgrp" test_ref="oval:mil.disa.stig.rhel8:tst:27000" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:286" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:271" version="3">
<metadata>
- <title>RHEL-08-030460 - Successful/unsuccessful uses of the ftruncate command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030360 - Successful/unsuccessful uses of the init_module and finit_module command system calls in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "truncate" and "ftruncate" functions are used to truncate a file to a specified length.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "init_module" and "finit_module" command system calls is are used to load a kernel module.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+
+The system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when you have to since these affect performance. The more rules, the bigger the performance hit. You can help the performance, though, by combining syscalls into one rule whenever possible.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of ftruncate syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28600" />
- <criterion comment="Audit 64-bit invocations of ftruncate syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28601" />
- <criterion comment="Audit 32-bit invocations of ftruncate syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28602" />
- <criterion comment="Audit 64-bit invocations of ftruncate syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28603" />
+ <criterion comment="Audit 32-bit invocations of init_module syscall" test_ref="oval:mil.disa.stig.rhel8:tst:27100" />
+ <criterion comment="Audit 64-bit invocations of init_module syscall" test_ref="oval:mil.disa.stig.rhel8:tst:27101" />
+ <criterion comment="Audit 32-bit invocations of finit_module syscall" test_ref="oval:mil.disa.stig.rhel8:tst:27800" />
+ <criterion comment="Audit 64-bit invocations of finit_module syscall" test_ref="oval:mil.disa.stig.rhel8:tst:27801" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:287" version="2">
+ <definition id="oval:mil.disa.stig.rhel8:def:272" class="compliance" version="2">
<metadata>
- <title>RHEL-08-030470 - Successful/unsuccessful uses of the creat system call in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030361 - Successful/unsuccessful uses of the rename, unlink, rmdir, renameat and unlinkat commandsystem calls in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "creat" system call is used to open and possibly create a file or device.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "rename" command system call will rename the specified files by replacing the first occurrence of expression in their name by replacement.
+The "unlink" system call deletes a name from the filesystem. If that name was the last link to a file and no processes have the file open, the file is deleted and the space it was using is made available for reuse.
+The "rmdir" system call removes empty directories.
+The "renameat" system call renames a file, moving it between directories if required.
+The "unlinkat" system call operates in exactly the same way as either "unlink" or "rmdir" except for the differences described in the manual page.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+The system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when you have to since these affect performance. The more rules, the bigger the performance hit. You can help the performance, though, by combining syscalls into one rule whenever possible.</description>
</metadata>
<criteria>
- <extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of creat syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28700" />
- <criterion comment="Audit 64-bit invocations of creat syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28701" />
- <criterion comment="Audit 32-bit invocations of creat syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28702" />
- <criterion comment="Audit 64-bit invocations of creat syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28703" />
+ <extend_definition definition_ref="oval:mil.disa.stig.rhel8:def:160" comment="The auditd package is installed and running" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27200" comment="Audit 32-bit invocations of rename" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27201" comment="Audit 64-bit invocations of rename" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27300" comment="Audit 32-bit invocations of renameat" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27301" comment="Audit 64-bit invocations of renameat" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27400" comment="Audit 32-bit invocations of rmdir" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27401" comment="Audit 64-bit invocations of rmdir" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27500" comment="Audit 32-bit invocations of unlink" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27501" comment="Audit 64-bit invocations of unlink" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27600" comment="Audit 32-bit invocations of unlinkat" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:27601" comment="Audit 64-bit invocations of unlinkat" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:288" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:277" version="3">
<metadata>
- <title>RHEL-08-030480 - Successful/unsuccessful uses of the chown command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030370 - Successful/unsuccessful uses of the gpasswd command in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "chown" command is used to change file owner and group.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "gpasswd" command is used to administer /etc/group and /etc/gshadow. Every group can have administrators, members and a password.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of chown syscall" test_ref="oval:mil.disa.stig.rhel8:tst:28800" />
- <criterion comment="Audit 64-bit invocations of chown syscall" test_ref="oval:mil.disa.stig.rhel8:tst:28801" />
+ <criterion comment="Audit invocations of /usr/bin/gpasswd" test_ref="oval:mil.disa.stig.rhel8:tst:27700" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:289" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:279" version="2">
<metadata>
- <title>RHEL-08-030490 - Successful/unsuccessful uses of the chmod command in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030390 - Successful/unsuccessful uses of the delete_module command in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "chmod" command changes the file mode bits of each given file according to mode, which can be either a symbolic representation of changes to make, or an octal number representing the bit pattern for the new mode bits.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "delete_module" command is used to unload a kernel module.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of chmod syscall" test_ref="oval:mil.disa.stig.rhel8:tst:28900" />
- <criterion comment="Audit 64-bit invocations of chmod syscall" test_ref="oval:mil.disa.stig.rhel8:tst:28901" />
+ <criterion comment="Audit 32-bit invocations of delete_module syscall" test_ref="oval:mil.disa.stig.rhel8:tst:27900" />
+ <criterion comment="Audit 64-bit invocations of delete_module syscall" test_ref="oval:mil.disa.stig.rhel8:tst:27901" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:290" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:280" version="3">
<metadata>
- <title>RHEL-08-030500 - Successful/unsuccessful uses of the lchown system call in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030400 - Successful/unsuccessful uses of the crontab command in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "lchown" system call is used to change the ownership of the file specified by a path, which does not dereference symbolic links.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "crontab" command is used to maintain crontab files for individual users. Crontab is the program used to install, remove, or list the tables used to drive the cron daemon. This is similar to the task scheduler used in other operating systems.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of lchown syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29000" />
- <criterion comment="Audit 64-bit invocations of lchown syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29001" />
+ <criterion comment="Audit invocations of /usr/bin/crontab" test_ref="oval:mil.disa.stig.rhel8:tst:28000" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:291" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:281" version="3">
<metadata>
- <title>RHEL-08-030510 - Successful/unsuccessful uses of the fchownat system call in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030410 - Successful/unsuccessful uses of the chsh command in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "fchownat" system call is used to change ownership of a file relative to a directory file descriptor.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "chsh" command is used to change the login shell.
When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of fchownat syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29100" />
- <criterion comment="Audit 64-bit invocations of fchownat syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29101" />
+ <criterion comment="Audit invocations of /usr/bin/chsh" test_ref="oval:mil.disa.stig.rhel8:tst:28100" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:292" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:282" version="3">
<metadata>
- <title>RHEL-08-030520 - Successful/unsuccessful uses of the fchown system call in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030420 - Successful/unsuccessful uses of the truncate, ftruncate, creat, open, openat, and open_by_handle_at system calls in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "fchown" system call is used to change the ownership of a file referred to by the open file descriptor.
+Audit records can be generated from various components within the information system (e.g., module or policy filter). The "truncate" and "ftruncate" functions are used to truncate a file to a specified length.
+The "creat" system call is used to open and possibly create a file or device.
+The "open" system call opens a file specified by a pathname. If the specified file does not exist, it may optionally be created by "open".
+The "openat" system call opens a file specified by a relative pathname.
+The "name_to_handle_at" and "open_by_handle_at" system calls split the functionality of openat into two parts: "name_to_handle_at" returns an opaque handle that corresponds to a specified file; "open_by_handle_at" opens the file corresponding to a handle returned by a previous call to "name_to_handle_at" and returns an open file descriptor.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+The system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when you have to since these affect performance. The more rules, the bigger the performance hit. You can help the performance, though, by combining syscalls into one rule whenever possible.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of fchown syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29200" />
- <criterion comment="Audit 64-bit invocations of fchown syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29201" />
+ <criterion comment="Audit 32-bit invocations of truncate syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28200" />
+ <criterion comment="Audit 64-bit invocations of truncate syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28201" />
+ <criterion comment="Audit 32-bit invocations of truncate syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28202" />
+ <criterion comment="Audit 64-bit invocations of truncate syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28203" />
+ <criterion comment="Audit 32-bit invocations of openat syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28300" />
+ <criterion comment="Audit 64-bit invocations of openat syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28301" />
+ <criterion comment="Audit 32-bit invocations of openat syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28302" />
+ <criterion comment="Audit 64-bit invocations of openat syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28303" />
+ <criterion comment="Audit 32-bit invocations of open syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28400" />
+ <criterion comment="Audit 64-bit invocations of open syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28401" />
+ <criterion comment="Audit 32-bit invocations of open syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28402" />
+ <criterion comment="Audit 64-bit invocations of open syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28403" />
+ <criterion comment="Audit 32-bit invocations of open_by_handle_at syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28500" />
+ <criterion comment="Audit 64-bit invocations of open_by_handle_at syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28501" />
+ <criterion comment="Audit 32-bit invocations of open_by_handle_at syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28502" />
+ <criterion comment="Audit 64-bit invocations of open_by_handle_at syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28503" />
+ <criterion comment="Audit 32-bit invocations of ftruncate syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28600" />
+ <criterion comment="Audit 64-bit invocations of ftruncate syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28601" />
+ <criterion comment="Audit 32-bit invocations of ftruncate syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28602" />
+ <criterion comment="Audit 64-bit invocations of ftruncate syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28603" />
+ <criterion comment="Audit 32-bit invocations of creat syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28700" />
+ <criterion comment="Audit 64-bit invocations of creat syscall with exit EPERM" test_ref="oval:mil.disa.stig.rhel8:tst:28701" />
+ <criterion comment="Audit 32-bit invocations of creat syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28702" />
+ <criterion comment="Audit 64-bit invocations of creat syscall with exit EACCES" test_ref="oval:mil.disa.stig.rhel8:tst:28703" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:293" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:288" version="3">
<metadata>
- <title>RHEL-08-030530 - Successful/unsuccessful uses of the fchmodat system call in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030480 - Successful/unsuccessful uses of the chown, fchown, fchownat and lchown system calls in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "fchmodat" system call is used to change permissions of a file relative to a directory file descriptor.
+Audit records can be generated from various components within the information system (e.g., module or policy filter).
+The "chown" command is used to change file owner and group.
+The "fchown" system call is used to change the ownership of a file referred to by the open file descriptor.
+The "fchownat" system call is used to change ownership of a file relative to a directory file descriptor.
+The "lchown" system call is used to change the ownership of the file specified by a path, which does not dereference symbolic links.
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+The system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when you have to since these affect performance. The more rules, the bigger the performance hit. You can help the performance, though, by combining syscalls into one rule whenever possible.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
- <criterion comment="Audit 32-bit invocations of fchmodat syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29300" />
- <criterion comment="Audit 64-bit invocations of fchmodat syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29301" />
+ <criterion comment="Audit 32-bit invocations of chown syscall" test_ref="oval:mil.disa.stig.rhel8:tst:28800" />
+ <criterion comment="Audit 64-bit invocations of chown syscall" test_ref="oval:mil.disa.stig.rhel8:tst:28801" />
+ <criterion comment="Audit 32-bit invocations of lchown syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29000" />
+ <criterion comment="Audit 64-bit invocations of lchown syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29001" />
+ <criterion comment="Audit 32-bit invocations of fchownat syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29100" />
+ <criterion comment="Audit 64-bit invocations of fchownat syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29101" />
+ <criterion comment="Audit 32-bit invocations of fchown syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29200" />
+ <criterion comment="Audit 64-bit invocations of fchown syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29201" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:294" version="2">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:289" version="3">
<metadata>
- <title>RHEL-08-030540 - Successful/unsuccessful uses of the fchmod system call in RHEL 8 must generate an audit record.</title>
+ <title>RHEL-08-030490 - Successful/unsuccessful uses of the chmod, fchmod and fchmodat system calls in RHEL 8 must generate an audit record.</title>
<affected family="unix">
<platform>Red Hat Enterprise Linux 8</platform>
</affected>
<description>Without generating audit records that are specific to the security and mission needs 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 "fchmod" system call is used to change permissions of a file.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.</description>
+Audit records can be generated from various components within the information system (e.g., module or policy filter).
+The "chmod" command system call changes the file mode bits of each given file according to mode, which can be either a symbolic representation of changes to make, or an octal number representing the bit pattern for the new mode bits.
+The "fchmod" system call is used to change permissions of a file.
+The "fchmodat" system call is used to change permissions of a file relative to a directory file descriptor.
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+The system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when you have to since these affect performance. The more rules, the bigger the performance hit. You can help the performance, though, by combining syscalls into one rule whenever possible.</description>
</metadata>
<criteria>
<extend_definition comment="The auditd package is installed and running" definition_ref="oval:mil.disa.stig.rhel8:def:160" />
+ <criterion comment="Audit 32-bit invocations of chmod syscall" test_ref="oval:mil.disa.stig.rhel8:tst:28900" />
+ <criterion comment="Audit 64-bit invocations of chmod syscall" test_ref="oval:mil.disa.stig.rhel8:tst:28901" />
+ <criterion comment="Audit 32-bit invocations of fchmodat syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29300" />
+ <criterion comment="Audit 64-bit invocations of fchmodat syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29301" />
<criterion comment="Audit 32-bit invocations of fchmod syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29400" />
<criterion comment="Audit 64-bit invocations of fchmod syscall" test_ref="oval:mil.disa.stig.rhel8:tst:29401" />
</criteria>
@@ -13550,7 +12310,7 @@ If a privileged user were to log on using this service, the privileged user pass
<criterion comment="The rsh-server package is absent." test_ref="oval:mil.disa.stig.rhel8:tst:31700" />
</criteria>
</definition>
- <definition id="oval:mil.disa.stig.rhel8:def:318" class="compliance" version="1">
+ <definition id="oval:mil.disa.stig.rhel8:def:318" class="compliance" version="2">
<metadata>
<title>RHEL-08-040021 - RHEL 8 must disable the asynchronous transfer mode (ATM) protocol.</title>
<affected family="unix">
@@ -13563,8 +12323,8 @@ Failing to disconnect unused protocols can result in a system compromise.
The Asynchronous Transfer Mode (ATM) is a protocol operating on network, data link, and physical layers, based on virtual circuits and virtual paths. Disabling ATM protects the system against exploitation of any laws in its implementation.</description>
</metadata>
<criteria>
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:31800" />
- <criterion test_ref="oval:mil.disa.stig.rhel8:tst:31801" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:31800" comment="/etc/modprobe.d contains a file that contains 'install atm /bin/true'" />
+ <criterion test_ref="oval:mil.disa.stig.rhel8:tst:31801" comment="/etc/modprobe.d contains a file that contains 'blacklist atm'" />
</criteria>
</definition>
<definition id="oval:mil.disa.stig.rhel8:def:319" class="compliance" version="1">
@@ -14594,7 +13354,7 @@ FIPS 140-2 is the current standard for validating that mechanisms used to access
<criterion comment="ALL is not configured in /etc/sudoers.d" test_ref="oval:mil.disa.stig.rhel8:tst:41401" />
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:415" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:415" version="2">
<metadata>
<title>RHEL-08-010383 - RHEL 8 must use the invoking user's password for privilege escalation when using "sudo".</title>
<affected family="unix">
@@ -14604,21 +13364,21 @@ FIPS 140-2 is the current standard for validating that mechanisms used to access
For more information on each of the listed configurations, reference the sudoers(5) manual page.</description>
</metadata>
<criteria operator="AND">
- <criteria operator="OR">
+ <criteria operator="ONE">
<criterion comment="Defaults !targetpw is configured in /etc/sudoers" test_ref="oval:mil.disa.stig.rhel8:tst:41500" />
<criterion comment="Defaults !targetpw is configured in /etc/sudoers.d" test_ref="oval:mil.disa.stig.rhel8:tst:41501" />
</criteria>
- <criteria operator="OR">
+ <criteria operator="ONE">
<criterion comment="Defaults !rootpw is configured in /etc/sudoers" test_ref="oval:mil.disa.stig.rhel8:tst:41502" />
<criterion comment="Defaults !rootpw is configured in /etc/sudoers.d" test_ref="oval:mil.disa.stig.rhel8:tst:41503" />
</criteria>
- <criteria operator="OR">
+ <criteria operator="ONE">
<criterion comment="Defaults !runaspw is configured in /etc/sudoers" test_ref="oval:mil.disa.stig.rhel8:tst:41504" />
<criterion comment="Defaults !runaspw is configured in /etc/sudoers.d" test_ref="oval:mil.disa.stig.rhel8:tst:41505" />
</criteria>
</criteria>
</definition>
- <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:416" version="1">
+ <definition class="compliance" id="oval:mil.disa.stig.rhel8:def:416" version="2">
<metadata>
<title>RHEL-08-010384 - RHEL 8 must require re-authentication when using the "sudo" command.</title>
<affected family="unix">
@@ -14630,7 +13390,7 @@ When operating systems provide the capability to escalate a functional capabilit
If the value is set to an integer less than 0, the user's time stamp will not expire and the user will not have to re-authenticate for privileged actions until the user's session is terminated.</description>
</metadata>
- <criteria operator="OR">
+ <criteria operator="ONE">
<criterion comment="Defaults timestamp_timeout is configured in /etc/sudoers" test_ref="oval:mil.disa.stig.rhel8:tst:41600" />
<criterion comment="Defaults timestamp_timeout is configured in /etc/sudoers.d" test_ref="oval:mil.disa.stig.rhel8:tst:41601" />
</criteria>
@@ -14651,9 +13411,19 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<rpminfo_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#linux" check="all" check_existence="all_exist" id="oval:mil.disa.stig.rhel8:tst:9900" comment="The openssh package is installed." version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:9900" />
</rpminfo_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="at_least_one_exists" comment="The RHEL 8 minor version is supported." id="oval:mil.disa.stig.rhel8:tst:10000" version="2" state_operator="OR">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="at_least_one_exists" comment="The RHEL 8 minor version is supported." id="oval:mil.disa.stig.rhel8:tst:10000" version="5" state_operator="OR">
<object object_ref="oval:mil.disa.stig.rhel8:obj:10000" />
- <state state_ref="oval:mil.disa.stig.rhel8:ste:10000" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:10001" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:10002" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:10003" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:10004" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:10005" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:10006" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:10007" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:10008" />
+ </textfilecontent54_test>
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="at_least_one_exists" comment="The RHEL 8 minor version is supported." id="oval:mil.disa.stig.rhel8:tst:10001" version="3" state_operator="OR">
+ <object object_ref="oval:mil.disa.stig.rhel8:obj:10001" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:10001" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:10002" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:10003" />
@@ -14678,10 +13448,14 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="none_exist" comment="No active password hash in /etc/shadow has a prefix other than '$6'." id="oval:mil.disa.stig.rhel8:tst:10400" version="1">
<object object_ref="oval:mil.disa.stig.rhel8:obj:10401" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="only_one_exists" comment="Check the file /etc/pam.d/password-auth to see if the password section for pam_unix.so sets rounds to a value no lower than 5000." id="oval:mil.disa.stig.rhel8:tst:10500" version="1">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/login.defs: SHA_CRYPT_MIN_ROUNDS, if set, is set to 5000 or greater" check="all" check_existence="any_exist" id="oval:mil.disa.stig.rhel8:tst:10500" version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:10500" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:10500" />
</textfilecontent54_test>
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/login.defs: SHA_CRYPT_MAX_ROUNDS, if set, is set to 5000 or greater" check="all" check_existence="any_exist" id="oval:mil.disa.stig.rhel8:tst:10501" version="2">
+ <object object_ref="oval:mil.disa.stig.rhel8:obj:10501" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:10500" />
+ </textfilecontent54_test>
<textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="all_exist" comment="/boot/efi/EFI/redhat/grub.cfg:superusers exists and has a name." id="oval:mil.disa.stig.rhel8:tst:10600" version="1">
<object object_ref="oval:mil.disa.stig.rhel8:obj:10600" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:10600" />
@@ -14768,10 +13542,24 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/sysconfig/sshd: SSH_USE_STRONG_RNG=32" check="all" id="oval:mil.disa.stig.rhel8:tst:12200" version="1">
<object object_ref="oval:mil.disa.stig.rhel8:obj:12200" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/crypto-policies/back-ends/opensslcnf.config: MinProtocol = TLSv1.2 or newer" check="all" state_operator="OR" id="oval:mil.disa.stig.rhel8:tst:12300" version="2">
+ <rpminfo_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#linux" comment="Package crypto-policies is version 20210617 or newer." check="all" id="oval:mil.disa.stig.rhel8:tst:12300" version="4">
<object object_ref="oval:mil.disa.stig.rhel8:obj:12300" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:12300" />
+ </rpminfo_test>
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/crypto-policies/back-ends/opensslcnf.config: MinProtocol = TLSv1.2 or newer." check="all" state_operator="OR" id="oval:mil.disa.stig.rhel8:tst:12301" version="1">
+ <object object_ref="oval:mil.disa.stig.rhel8:obj:12301" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:12301" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:12302" />
+ </textfilecontent54_test>
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/crypto-policies/back-ends/opensslcnf.config: TLS.MinProtocol = TLSv1.2 or newer." check="all" state_operator="OR" id="oval:mil.disa.stig.rhel8:tst:12302" version="1">
+ <object object_ref="oval:mil.disa.stig.rhel8:obj:12302" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:12301" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:12302" />
+ </textfilecontent54_test>
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/crypto-policies/back-ends/opensslcnf.config: DTLS.MinProtocol = DTLSv1.2 or newer." check="all" state_operator="OR" id="oval:mil.disa.stig.rhel8:tst:12303" version="1">
+ <object object_ref="oval:mil.disa.stig.rhel8:obj:12303" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:12303" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:12304" />
</textfilecontent54_test>
<file_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#unix" check="all" check_existence="all_exist" comment="System command files have mode 755 or less permissive" id="oval:mil.disa.stig.rhel8:tst:12400" version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:12401" />
@@ -15141,19 +13929,17 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="the lock-command is set in /etc/tmux.conf" check="all" id="oval:mil.disa.stig.rhel8:tst:19301" version="1">
<object object_ref="oval:mil.disa.stig.rhel8:obj:19301" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/bashrc contains a line to properly configure tmux" check="all" id="oval:mil.disa.stig.rhel8:tst:19400" version="2">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/profile.d/*.sh contains a shell script to initialize the tmux terminal multiplexer as each shell is called." check="all" id="oval:mil.disa.stig.rhel8:tst:19400" version="3">
<object object_ref="oval:mil.disa.stig.rhel8:obj:19400" />
</textfilecontent54_test>
+ <process58_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#unix" comment="The tmux process is running." check="all" id="oval:mil.disa.stig.rhel8:tst:19401" version="1">
+ <object object_ref="oval:mil.disa.stig.rhel8:obj:19401" />
+ </process58_test>
<textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/shells does not contain any instances of tmux" check="all" check_existence="none_exist" id="oval:mil.disa.stig.rhel8:tst:19500" version="1">
<object object_ref="oval:mil.disa.stig.rhel8:obj:19500" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" comment="The pam_pwquality module is included in password-auth with the correct retry setting." id="oval:mil.disa.stig.rhel8:tst:19600" version="1">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" comment="The pam_pwquality module is included in password-auth." id="oval:mil.disa.stig.rhel8:tst:19600" version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:19600" />
- <state state_ref="oval:mil.disa.stig.rhel8:ste:19600" />
- </textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" comment="The pam_pwquality module is included in system-auth with the correct retry setting." id="oval:mil.disa.stig.rhel8:tst:19601" version="1">
- <object object_ref="oval:mil.disa.stig.rhel8:obj:19601" />
- <state state_ref="oval:mil.disa.stig.rhel8:ste:19600" />
</textfilecontent54_test>
<textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="at least one uppercase character is required" check="all" id="oval:mil.disa.stig.rhel8:tst:19700" version="1">
<object object_ref="oval:mil.disa.stig.rhel8:obj:19700" />
@@ -15216,11 +14002,7 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="none_exist" comment="Root does not have a blank entry in /etc/shadow for maximum password age" id="oval:mil.disa.stig.rhel8:tst:20703" version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:20704" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/pam.d/system-auth: pam_pwhistory.so has remember set to 5 or greater" check="all" id="oval:mil.disa.stig.rhel8:tst:20800" version="1">
- <object object_ref="oval:mil.disa.stig.rhel8:obj:20800" />
- <state state_ref="oval:mil.disa.stig.rhel8:ste:20800" />
- </textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/pam.d/password-auth: pam_pwhistory.so has remember set to 5 or greater" check="all" id="oval:mil.disa.stig.rhel8:tst:20801" version="1">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/pam.d/password-auth: pam_pwhistory.so has remember set to 5 or greater" check="all" id="oval:mil.disa.stig.rhel8:tst:20801" version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:20801" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:20800" />
</textfilecontent54_test>
@@ -15245,6 +14027,10 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<object object_ref="oval:mil.disa.stig.rhel8:obj:21400" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:9801" />
</textfilecontent54_test>
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="passwords must not be dictionary words" check="all" id="oval:mil.disa.stig.rhel8:tst:21401" version="1">
+ <object object_ref="oval:mil.disa.stig.rhel8:obj:21401" />
+ <state state_ref="oval:mil.disa.stig.rhel8:ste:9801" />
+ </textfilecontent54_test>
<textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/login.defs: FAIL_DELAY = 4 or greater" check="all" id="oval:mil.disa.stig.rhel8:tst:21500" version="1">
<object object_ref="oval:mil.disa.stig.rhel8:obj:21500" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:21500" />
@@ -15282,11 +14068,6 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<state state_ref="oval:mil.disa.stig.rhel8:ste:22301" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:22302" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/audit/auditd.conf: max_log_file_action = syslog or keep_logs" check="all" state_operator="OR" id="oval:mil.disa.stig.rhel8:tst:22400" version="1">
- <object object_ref="oval:mil.disa.stig.rhel8:obj:22400" />
- <state state_ref="oval:mil.disa.stig.rhel8:ste:22400" />
- <state state_ref="oval:mil.disa.stig.rhel8:ste:22401" />
- </textfilecontent54_test>
<textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/audit/auditd.conf: disk_full_action = SYSLOG, SINGLE, or HALT" check="all" state_operator="OR" id="oval:mil.disa.stig.rhel8:tst:22500" version="1">
<object object_ref="oval:mil.disa.stig.rhel8:obj:22500" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:22300" />
@@ -15736,7 +14517,7 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/modprobe.d contains a file that contains 'install atm /bin/true'" check="all" id="oval:mil.disa.stig.rhel8:tst:31800" version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:31800" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/modprobe.d contains a file that contains 'blacklist atn'" check="all" id="oval:mil.disa.stig.rhel8:tst:31801" version="2">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/modprobe.d contains a file that contains 'blacklist atm'" check="all" id="oval:mil.disa.stig.rhel8:tst:31801" version="3">
<object object_ref="oval:mil.disa.stig.rhel8:obj:31801" />
</textfilecontent54_test>
<textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/etc/modprobe.d contains a file that contains 'install can /bin/true'" check="all" id="oval:mil.disa.stig.rhel8:tst:31900" version="2">
@@ -16093,29 +14874,29 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="none_exist" comment="ALL does not exist in /etc/sudoers.d" id="oval:mil.disa.stig.rhel8:tst:41401" version="1">
<object object_ref="oval:mil.disa.stig.rhel8:obj:41401" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="at_least_one_exists" comment="Defaults !targetpw is configured in /etc/sudoers" id="oval:mil.disa.stig.rhel8:tst:41500" version="1">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="only_one_exists" comment="Defaults !targetpw is configured in /etc/sudoers" id="oval:mil.disa.stig.rhel8:tst:41500" version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:41500" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="at_least_one_exists" comment="Defaults !targetpw is configured in /etc/sudoers.d" id="oval:mil.disa.stig.rhel8:tst:41501" version="1">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="only_one_exists" comment="Defaults !targetpw is configured in /etc/sudoers.d" id="oval:mil.disa.stig.rhel8:tst:41501" version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:41501" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="at_least_one_exists" comment="Defaults !rootpw is configured in /etc/sudoers" id="oval:mil.disa.stig.rhel8:tst:41502" version="1">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="only_one_exists" comment="Defaults !rootpw is configured in /etc/sudoers" id="oval:mil.disa.stig.rhel8:tst:41502" version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:41502" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="at_least_one_exists" comment="Defaults !rootpw is configured in /etc/sudoers.d" id="oval:mil.disa.stig.rhel8:tst:41503" version="1">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="only_one_exists" comment="Defaults !rootpw is configured in /etc/sudoers.d" id="oval:mil.disa.stig.rhel8:tst:41503" version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:41503" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="at_least_one_exists" comment="Defaults !runaspw is configured in /etc/sudoers" id="oval:mil.disa.stig.rhel8:tst:41504" version="1">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="only_one_exists" comment="Defaults !runaspw is configured in /etc/sudoers" id="oval:mil.disa.stig.rhel8:tst:41504" version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:41504" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="at_least_one_exists" comment="Defaults !runaspw is configured in /etc/sudoers.d" id="oval:mil.disa.stig.rhel8:tst:41505" version="1">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="only_one_exists" comment="Defaults !runaspw is configured in /etc/sudoers.d" id="oval:mil.disa.stig.rhel8:tst:41505" version="2">
<object object_ref="oval:mil.disa.stig.rhel8:obj:41505" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="at_least_one_exists" comment="Defaults timestamp_timeout is configured in /etc/sudoers" id="oval:mil.disa.stig.rhel8:tst:41600" version="2">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="only_one_exists" comment="Defaults timestamp_timeout is configured in /etc/sudoers" id="oval:mil.disa.stig.rhel8:tst:41600" version="3">
<object object_ref="oval:mil.disa.stig.rhel8:obj:41600" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:41600" />
</textfilecontent54_test>
- <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="at_least_one_exists" comment="Defaults timestamp_timeout is configured in /etc/sudoers.d" id="oval:mil.disa.stig.rhel8:tst:41601" version="2">
+ <textfilecontent54_test xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" check="all" check_existence="only_one_exists" comment="Defaults timestamp_timeout is configured in /etc/sudoers.d" id="oval:mil.disa.stig.rhel8:tst:41601" version="3">
<object object_ref="oval:mil.disa.stig.rhel8:obj:41601" />
<state state_ref="oval:mil.disa.stig.rhel8:ste:41600" />
</textfilecontent54_test>
@@ -16155,6 +14936,12 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<pattern operation="pattern match">^\s*CPE_NAME="cpe:/o:redhat:enterprise_linux:8\.(\d+)\b</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:10001" version="3" comment="The minor version of RHEL 8">
+ <path>/etc</path>
+ <filename>os-release</filename>
+ <pattern operation="pattern match">^\s*PRETTY_NAME="Red Hat Enterprise Linux 8\.(\d+)\b</pattern>
+ <instance datatype="int" operation="greater than or equal">1</instance>
+ </textfilecontent54_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/proc/sys/crypto/fips_enabled" id="oval:mil.disa.stig.rhel8:obj:10100" version="1">
<filepath datatype="string">/proc/sys/crypto/fips_enabled</filepath>
<pattern operation="pattern match">^(\d+)$</pattern>
@@ -16182,10 +14969,14 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<filter action="exclude">oval:mil.disa.stig.rhel8:ste:10401</filter>
</set>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="Check the file /etc/pam.d/password-auth for the setting: password sufficient pam_unix.so sha512 rounds=(some number)" id="oval:mil.disa.stig.rhel8:obj:10500" version="1">
- <path datatype="string">/etc/pam.d</path>
- <filename datatype="string">password-auth</filename>
- <pattern operation="pattern match">^[ \t]*password[ \t]+sufficient[ \t]+pam_unix\.so(?:[ \t]+|(?:[ \t][^#\r\f\n]+[ \t]))rounds=([\d]+)(?:[ \t]|$)</pattern>
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:10500" version="2">
+ <filepath>/etc/login.defs</filepath>
+ <pattern operation="pattern match">^\s*SHA_CRYPT_MIN_ROUNDS\s+(\d+)\b</pattern>
+ <instance datatype="int" operation="greater than or equal">1</instance>
+ </textfilecontent54_object>
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:10501" version="2">
+ <filepath>/etc/login.defs</filepath>
+ <pattern operation="pattern match">^\s*SHA_CRYPT_MAX_ROUNDS\s+(\d+)\b</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="/boot/efi/EFI/redhat/grub.cfg:superusers" id="oval:mil.disa.stig.rhel8:obj:10600" version="1">
@@ -16256,9 +15047,22 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<pattern operation="pattern match">^[ \t]*SSH_USE_STRONG_RNG[ \t]*=[ \t]*32[ \t]*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:12300" version="2">
+ <rpminfo_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#linux" id="oval:mil.disa.stig.rhel8:obj:12300" version="3">
+ <name>crypto-policies</name>
+ </rpminfo_object>
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:12301" version="2">
+ <filepath>/etc/crypto-policies/back-ends/opensslcnf.config</filepath>
+ <pattern operation="pattern match">^\s*MinProtocol\s*=\s*([\.\w]+)\s*(?:#.*)?$</pattern>
+ <instance datatype="int" operation="greater than or equal">1</instance>
+ </textfilecontent54_object>
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:12302" version="2">
+ <filepath>/etc/crypto-policies/back-ends/opensslcnf.config</filepath>
+ <pattern operation="pattern match">^\s*TLS\.MinProtocol\s*=\s*([\.\w]+)\s*(?:#.*)?$</pattern>
+ <instance datatype="int" operation="greater than or equal">1</instance>
+ </textfilecontent54_object>
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:12303" version="2">
<filepath>/etc/crypto-policies/back-ends/opensslcnf.config</filepath>
- <pattern operation="pattern match">^\s*MinProtocol\s*=\s*(\S+)\s*(?:#.*)?$</pattern>
+ <pattern operation="pattern match">^\s*DTLS\.MinProtocol\s*=\s*([\.\w]+)\s*(?:#.*)?$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
<file_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#unix" comment="All files in system command directories" id="oval:mil.disa.stig.rhel8:obj:12400" version="1">
@@ -16687,25 +15491,25 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<pattern operation="pattern match">^\s*set\s+-g\s+lock-command\s+vlock\s*(?:#.*)?$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:19400" version="5">
- <filepath>/etc/bashrc</filepath>
- <pattern operation="pattern match">^\s*\[\s+-n\s+"\$PS1"\s+-a\s+-z\s+"\$TMUX"\s+\]\s+&amp;&amp;\s+exec\s+tmux\s*(?:#.*)?$</pattern>
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:19400" version="7">
+ <path>/etc/profile.d</path>
+ <filename operation="pattern match">\.sh$</filename>
+ <pattern operation="pattern match">^\s*if\s+\[\s*"\$PS1"\s*\];\s+then\s+parent=\$\(ps\s+-o\s+ppid=\s+-p\s+\$\$\)\s+name=\$\(ps\s+-o\s+comm=\s+-p\s+\$parent\)\s+case\s+"\$name"\s+in\s+\(sshd\|login\)\s+exec\s+tmux\s+;;\s+esac\s+fi\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
+ <process58_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#unix" id="oval:mil.disa.stig.rhel8:obj:19401" version="2">
+ <command_line operation="pattern match">^(/usr/bin/)?tmux\b</command_line>
+ <pid datatype="int" operation="greater than">1</pid>
+ </process58_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:19500" version="1">
<behaviors ignore_case="true" />
<filepath>/etc/shells</filepath>
<pattern operation="pattern match">tmux</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:19600" version="1" comment="pam_pwquality in password-auth">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:19600" version="2" comment="pam_pwquality in password-auth">
<filepath>/etc/pam.d/password-auth</filepath>
- <pattern operation="pattern match">^\s*password\s+(?:(?:required)|(?:requisite))\s+pam_pwquality\.so.*retry=(\S+)\b</pattern>
- <instance datatype="int" operation="greater than or equal">1</instance>
- </textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:19601" version="1" comment="pam_pwquality in system-auth">
- <filepath>/etc/pam.d/system-auth</filepath>
- <pattern operation="pattern match">^\s*password\s+(?:(?:required)|(?:requisite))\s+pam_pwquality\.so.*retry=(\S+)\b</pattern>
+ <pattern operation="pattern match">^\s*password\s+(?:required|requisite)\s+pam_pwquality\.so\b</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="ucredit setting in /etc/security/pwquality.conf" id="oval:mil.disa.stig.rhel8:obj:19700" version="1">
@@ -16801,14 +15605,9 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<pattern datatype="string" operation="pattern match">^root:[^:]*:[^:]*:[^:]*::</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:20800" version="4">
- <filepath>/etc/pam.d/system-auth</filepath>
- <pattern operation="pattern match">^\s*password\s+required\s+pam_pwhistory\.so\s+[^#\n]*\bremember=(\d).*$</pattern>
- <instance datatype="int" operation="greater than or equal">1</instance>
- </textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:20801" version="4">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:20801" version="5">
<filepath>/etc/pam.d/password-auth</filepath>
- <pattern operation="pattern match">^\s*password\s+required\s+pam_pwhistory\.so\s+[^#\n]*\bremember=(\d).*$</pattern>
+ <pattern operation="pattern match">^\s*password\s+required\s+pam_pwhistory\.so\s+[^#\n]*\bremember=(\d+)\b</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:20900" version="1">
@@ -16836,6 +15635,12 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<pattern operation="pattern match">^\s*dictcheck\s*=\s*(\d*)\s*(?:#.*)?$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:21401" version="2">
+ <path>/etc/pwquality.conf.d/</path>
+ <filename operation="pattern match">^.*\.conf$</filename>
+ <pattern operation="pattern match">^\s*dictcheck\s*=\s*(\d*)\s*(?:#.*)?$</pattern>
+ <instance datatype="int" operation="greater than or equal">1</instance>
+ </textfilecontent54_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:21500" version="2">
<filepath>/etc/login.defs</filepath>
<pattern operation="pattern match">^\s*FAIL_DELAY\s+(\d+)\s*$</pattern>
@@ -16886,11 +15691,6 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<pattern operation="pattern match">(?i)^\s*disk_error_action\s*=\s*(\w+)\s*(?:#.*)?$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:22400" version="2">
- <filepath>/etc/audit/auditd.conf</filepath>
- <pattern operation="pattern match">(?i)^\s*max_log_file_action\s*=\s*(\w+)\s*(?:#.*)?$</pattern>
- <instance datatype="int" operation="greater than or equal">1</instance>
- </textfilecontent54_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:22500" version="2">
<filepath>/etc/audit/auditd.conf</filepath>
<pattern operation="pattern match">(?i)^\s*disk_full_action\s*=\s*(\w+)\s*(?:#.*)?$</pattern>
@@ -16977,104 +15777,104 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+path=/usr/bin/su\s+(-F\s+perm=([rwa]*x[rwa]*)\s+)?-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit lremovexattr syscall" id="oval:mil.disa.stig.rhel8:obj:24600" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit lremovexattr syscall" id="oval:mil.disa.stig.rhel8:obj:24600" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+lremovexattr\s+|(\s+|,)lremovexattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+lremovexattr\s+|(\s+|,)lremovexattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit lremovexattr syscall" id="oval:mil.disa.stig.rhel8:obj:24601" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit lremovexattr syscall" id="oval:mil.disa.stig.rhel8:obj:24601" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+lremovexattr\s+|(\s+|,)lremovexattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+lremovexattr\s+|(\s+|,)lremovexattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit lremovexattr syscall (invoked by root)" id="oval:mil.disa.stig.rhel8:obj:24602" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit lremovexattr syscall (invoked by root)" id="oval:mil.disa.stig.rhel8:obj:24602" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+lremovexattr\s+|(\s+|,)lremovexattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+lremovexattr\s+|(\s+|,)lremovexattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit lremovexattr syscall (invoked by root)" id="oval:mil.disa.stig.rhel8:obj:24603" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit lremovexattr syscall (invoked by root)" id="oval:mil.disa.stig.rhel8:obj:24603" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+lremovexattr\s+|(\s+|,)lremovexattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+lremovexattr\s+|(\s+|,)lremovexattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit removexattr syscall (auid&gt;=1000)" id="oval:mil.disa.stig.rhel8:obj:24700" version="3">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit removexattr syscall (auid&gt;=1000)" id="oval:mil.disa.stig.rhel8:obj:24700" version="4">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+removexattr\s+|(\s+|,)removexattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+removexattr\s+|(\s+|,)removexattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit removexattr syscall (auid&gt;=1000)" id="oval:mil.disa.stig.rhel8:obj:24701" version="3">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit removexattr syscall (auid&gt;=1000)" id="oval:mil.disa.stig.rhel8:obj:24701" version="4">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+removexattr\s+|(\s+|,)removexattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+removexattr\s+|(\s+|,)removexattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit removexattr syscall (auid=0)" id="oval:mil.disa.stig.rhel8:obj:24702" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit removexattr syscall (auid=0)" id="oval:mil.disa.stig.rhel8:obj:24702" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+removexattr\s+|(\s+|,)removexattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+removexattr\s+|(\s+|,)removexattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit removexattr syscall (auid=0)" id="oval:mil.disa.stig.rhel8:obj:24703" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit removexattr syscall (auid=0)" id="oval:mil.disa.stig.rhel8:obj:24703" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+removexattr\s+|(\s+|,)removexattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+removexattr\s+|(\s+|,)removexattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit lsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24800" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit lsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24800" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+lsetxattr\s+|(\s+|,)lsetxattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+lsetxattr\s+|(\s+|,)lsetxattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit lsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24801" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit lsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24801" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+lsetxattr\s+|(\s+|,)lsetxattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+lsetxattr\s+|(\s+|,)lsetxattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit lsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24802" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit lsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24802" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+lsetxattr\s+|(\s+|,)lsetxattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+lsetxattr\s+|(\s+|,)lsetxattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit lsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24803" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit lsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24803" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+lsetxattr\s+|(\s+|,)lsetxattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+lsetxattr\s+|(\s+|,)lsetxattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24900" version="3">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24900" version="4">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fsetxattr\s+|(\s+|,)fsetxattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fsetxattr\s+|(\s+|,)fsetxattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24901" version="3">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24901" version="4">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fsetxattr\s+|(\s+|,)fsetxattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fsetxattr\s+|(\s+|,)fsetxattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24902" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24902" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fsetxattr\s+|(\s+|,)fsetxattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fsetxattr\s+|(\s+|,)fsetxattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24903" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fsetxattr syscall" id="oval:mil.disa.stig.rhel8:obj:24903" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fsetxattr\s+|(\s+|,)fsetxattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fsetxattr\s+|(\s+|,)fsetxattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fremovexattr syscall (auid&gt;=1000)" id="oval:mil.disa.stig.rhel8:obj:25000" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fremovexattr syscall (auid&gt;=1000)" id="oval:mil.disa.stig.rhel8:obj:25000" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fremovexattr\s+|(\s+|,)fremovexattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fremovexattr\s+|(\s+|,)fremovexattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fremovexattr syscall (auid&gt;=1000)" id="oval:mil.disa.stig.rhel8:obj:25001" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fremovexattr syscall (auid&gt;=1000)" id="oval:mil.disa.stig.rhel8:obj:25001" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fremovexattr\s+|(\s+|,)fremovexattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fremovexattr\s+|(\s+|,)fremovexattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fremovexattr syscall (auid=0)" id="oval:mil.disa.stig.rhel8:obj:25002" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fremovexattr syscall (auid=0)" id="oval:mil.disa.stig.rhel8:obj:25002" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fremovexattr\s+|(\s+|,)fremovexattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fremovexattr\s+|(\s+|,)fremovexattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fremovexattr syscall (auid=0)" id="oval:mil.disa.stig.rhel8:obj:25003" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fremovexattr syscall (auid=0)" id="oval:mil.disa.stig.rhel8:obj:25003" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fremovexattr\s+|(\s+|,)fremovexattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fremovexattr\s+|(\s+|,)fremovexattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:25100" version="3">
@@ -17087,24 +15887,24 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+path=/usr/bin/chcon\s+(-F\s+perm=([rwa]*x[rwa]*)\s+)?-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit setxattr syscall" id="oval:mil.disa.stig.rhel8:obj:25300" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit setxattr syscall" id="oval:mil.disa.stig.rhel8:obj:25300" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+setxattr\s+|(\s+|,)setxattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+setxattr\s+|(\s+|,)setxattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit setxattr syscall" id="oval:mil.disa.stig.rhel8:obj:25301" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit setxattr syscall" id="oval:mil.disa.stig.rhel8:obj:25301" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+setxattr\s+|(\s+|,)setxattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+setxattr\s+|(\s+|,)setxattr(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit setxattr syscall" id="oval:mil.disa.stig.rhel8:obj:25302" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit setxattr syscall" id="oval:mil.disa.stig.rhel8:obj:25302" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+setxattr\s+|(\s+|,)setxattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+setxattr\s+|(\s+|,)setxattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit setxattr syscall" id="oval:mil.disa.stig.rhel8:obj:25303" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit setxattr syscall" id="oval:mil.disa.stig.rhel8:obj:25303" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+setxattr\s+|(\s+|,)setxattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+setxattr\s+|(\s+|,)setxattr(\s+|,))).*-F\s+auid=0(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:25400" version="3">
@@ -17197,64 +15997,64 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+path=/usr/bin/newgrp\s+(-F\s+perm=([rwa]*x[rwa]*)\s+)?-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit init_module syscall" id="oval:mil.disa.stig.rhel8:obj:27100" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit init_module syscall" id="oval:mil.disa.stig.rhel8:obj:27100" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+init_module\s+|(\s+|,)init_module(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+init_module\s+|(\s+|,)init_module(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit init_module syscall" id="oval:mil.disa.stig.rhel8:obj:27101" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit init_module syscall" id="oval:mil.disa.stig.rhel8:obj:27101" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+init_module\s+|(\s+|,)init_module(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+init_module\s+|(\s+|,)init_module(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit rename command" id="oval:mil.disa.stig.rhel8:obj:27200" version="3">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit rename command" id="oval:mil.disa.stig.rhel8:obj:27200" version="4">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+rename\s+|(\s+|,)rename(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+rename\s+|(\s+|,)rename(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit rename command" id="oval:mil.disa.stig.rhel8:obj:27201" version="3">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit rename command" id="oval:mil.disa.stig.rhel8:obj:27201" version="4">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+rename\s+|(\s+|,)rename(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+rename\s+|(\s+|,)rename(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit renameat command" id="oval:mil.disa.stig.rhel8:obj:27300" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit renameat command" id="oval:mil.disa.stig.rhel8:obj:27300" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+renameat\s+|(\s+|,)renameat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+renameat\s+|(\s+|,)renameat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit renameat command" id="oval:mil.disa.stig.rhel8:obj:27301" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit renameat command" id="oval:mil.disa.stig.rhel8:obj:27301" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+renameat\s+|(\s+|,)renameat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+renameat\s+|(\s+|,)renameat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit rmdir command" id="oval:mil.disa.stig.rhel8:obj:27400" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit rmdir command" id="oval:mil.disa.stig.rhel8:obj:27400" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+rmdir\s+|(\s+|,)rmdir(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+rmdir\s+|(\s+|,)rmdir(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit rmdir command" id="oval:mil.disa.stig.rhel8:obj:27401" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit rmdir command" id="oval:mil.disa.stig.rhel8:obj:27401" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+rmdir\s+|(\s+|,)rmdir(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+rmdir\s+|(\s+|,)rmdir(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit unlink command" id="oval:mil.disa.stig.rhel8:obj:27500" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit unlink command" id="oval:mil.disa.stig.rhel8:obj:27500" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+unlink\s+|(\s+|,)unlink(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+unlink\s+|(\s+|,)unlink(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit unlink command" id="oval:mil.disa.stig.rhel8:obj:27501" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit unlink command" id="oval:mil.disa.stig.rhel8:obj:27501" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+unlink\s+|(\s+|,)unlink(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+unlink\s+|(\s+|,)unlink(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit unlinkat command" id="oval:mil.disa.stig.rhel8:obj:27600" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit unlinkat command" id="oval:mil.disa.stig.rhel8:obj:27600" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+unlinkat\s+|(\s+|,)unlinkat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+unlinkat\s+|(\s+|,)unlinkat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit unlinkat command" id="oval:mil.disa.stig.rhel8:obj:27601" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit unlinkat command" id="oval:mil.disa.stig.rhel8:obj:27601" version="2">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+unlinkat\s+|(\s+|,)unlinkat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+unlinkat\s+|(\s+|,)unlinkat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:27700" version="3">
@@ -17262,14 +16062,14 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+path=/usr/bin/gpasswd\s+(-F\s+perm=([rwa]*x[rwa]*)\s+)?-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit finit_module syscall" id="oval:mil.disa.stig.rhel8:obj:27800" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit finit_module syscall" id="oval:mil.disa.stig.rhel8:obj:27800" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+finit_module\s+|(\s+|,)finit_module(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+finit_module\s+|(\s+|,)finit_module(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit finit_module syscall" id="oval:mil.disa.stig.rhel8:obj:27801" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit finit_module syscall" id="oval:mil.disa.stig.rhel8:obj:27801" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+finit_module\s+|(\s+|,)finit_module(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+finit_module\s+|(\s+|,)finit_module(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit delete_module syscall" id="oval:mil.disa.stig.rhel8:obj:27900" version="2">
@@ -17292,194 +16092,194 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+path=/usr/bin/chsh\s+(-F\s+perm=([rwa]*x[rwa]*)\s+)?-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit truncate syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28200" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit truncate syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28200" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+truncate\s+|(\s+|,)truncate(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+truncate\s+|(\s+|,)truncate(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit truncate syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28201" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit truncate syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28201" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+truncate\s+|(\s+|,)truncate(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+truncate\s+|(\s+|,)truncate(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit truncate syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28202" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit truncate syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28202" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+truncate\s+|(\s+|,)truncate(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+truncate\s+|(\s+|,)truncate(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit truncate syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28203" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit truncate syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28203" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+truncate\s+|(\s+|,)truncate(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+truncate\s+|(\s+|,)truncate(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit openat syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28300" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit openat syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28300" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+openat\s+|(\s+|,)openat(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+openat\s+|(\s+|,)openat(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit openat syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28301" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit openat syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28301" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+openat\s+|(\s+|,)openat(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+openat\s+|(\s+|,)openat(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit openat syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28302" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit openat syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28302" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+openat\s+|(\s+|,)openat(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+openat\s+|(\s+|,)openat(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit openat syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28303" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit openat syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28303" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+openat\s+|(\s+|,)openat(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+openat\s+|(\s+|,)openat(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit open syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28400" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit open syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28400" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+open\s+|(\s+|,)open(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+open\s+|(\s+|,)open(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit open syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28401" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit open syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28401" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+open\s+|(\s+|,)open(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+open\s+|(\s+|,)open(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit open syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28402" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit open syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28402" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+open\s+|(\s+|,)open(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+open\s+|(\s+|,)open(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit open syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28403" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit open syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28403" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+open\s+|(\s+|,)open(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+open\s+|(\s+|,)open(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit open_by_handle_at syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28500" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit open_by_handle_at syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28500" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+open_by_handle_at\s+|(\s+|,)open_by_handle_at(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+open_by_handle_at\s+|(\s+|,)open_by_handle_at(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit open_by_handle_at syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28501" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit open_by_handle_at syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28501" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+open_by_handle_at\s+|(\s+|,)open_by_handle_at(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+open_by_handle_at\s+|(\s+|,)open_by_handle_at(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit open_by_handle_at syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28502" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit open_by_handle_at syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28502" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+open_by_handle_at\s+|(\s+|,)open_by_handle_at(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+open_by_handle_at\s+|(\s+|,)open_by_handle_at(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit open_by_handle_at syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28503" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit open_by_handle_at syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28503" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+open_by_handle_at\s+|(\s+|,)open_by_handle_at(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+open_by_handle_at\s+|(\s+|,)open_by_handle_at(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit ftruncate syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28600" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit ftruncate syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28600" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+ftruncate\s+|(\s+|,)ftruncate(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+ftruncate\s+|(\s+|,)ftruncate(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit ftruncate syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28601" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit ftruncate syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28601" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+ftruncate\s+|(\s+|,)ftruncate(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+ftruncate\s+|(\s+|,)ftruncate(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit ftruncate syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28602" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit ftruncate syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28602" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+ftruncate\s+|(\s+|,)ftruncate(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+ftruncate\s+|(\s+|,)ftruncate(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit ftruncate syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28603" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit ftruncate syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28603" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+ftruncate\s+|(\s+|,)ftruncate(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+ftruncate\s+|(\s+|,)ftruncate(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit creat syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28700" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit creat syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28700" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+creat\s+|(\s+|,)creat(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+creat\s+|(\s+|,)creat(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit creat syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28701" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit creat syscall with exit EPERM" id="oval:mil.disa.stig.rhel8:obj:28701" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+creat\s+|(\s+|,)creat(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+creat\s+|(\s+|,)creat(\s+|,))).*-F\s+exit=-EPERM\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit creat syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28702" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit creat syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28702" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+creat\s+|(\s+|,)creat(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+creat\s+|(\s+|,)creat(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit creat syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28703" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit creat syscall with exit EACCES" id="oval:mil.disa.stig.rhel8:obj:28703" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+creat\s+|(\s+|,)creat(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+creat\s+|(\s+|,)creat(\s+|,))).*-F\s+exit=-EACCES\s+-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit chown syscall" id="oval:mil.disa.stig.rhel8:obj:28800" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit chown syscall" id="oval:mil.disa.stig.rhel8:obj:28800" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+chown\s+|(\s+|,)chown(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+chown\s+|(\s+|,)chown(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit chown syscall" id="oval:mil.disa.stig.rhel8:obj:28801" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit chown syscall" id="oval:mil.disa.stig.rhel8:obj:28801" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+chown\s+|(\s+|,)chown(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+chown\s+|(\s+|,)chown(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit chmod syscall" id="oval:mil.disa.stig.rhel8:obj:28900" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit chmod syscall" id="oval:mil.disa.stig.rhel8:obj:28900" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+chmod\s+|(\s+|,)chmod(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+chmod\s+|(\s+|,)chmod(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit chmod syscall" id="oval:mil.disa.stig.rhel8:obj:28901" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit chmod syscall" id="oval:mil.disa.stig.rhel8:obj:28901" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+chmod\s+|(\s+|,)chmod(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+chmod\s+|(\s+|,)chmod(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit lchown syscall" id="oval:mil.disa.stig.rhel8:obj:29000" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit lchown syscall" id="oval:mil.disa.stig.rhel8:obj:29000" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+lchown\s+|(\s+|,)lchown(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+lchown\s+|(\s+|,)lchown(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit lchown syscall" id="oval:mil.disa.stig.rhel8:obj:29001" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit lchown syscall" id="oval:mil.disa.stig.rhel8:obj:29001" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+lchown\s+|(\s+|,)lchown(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+lchown\s+|(\s+|,)lchown(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fchownat syscall" id="oval:mil.disa.stig.rhel8:obj:29100" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fchownat syscall" id="oval:mil.disa.stig.rhel8:obj:29100" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fchownat\s+|(\s+|,)fchownat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fchownat\s+|(\s+|,)fchownat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fchownat syscall" id="oval:mil.disa.stig.rhel8:obj:29101" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fchownat syscall" id="oval:mil.disa.stig.rhel8:obj:29101" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fchownat\s+|(\s+|,)fchownat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fchownat\s+|(\s+|,)fchownat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fchown syscall" id="oval:mil.disa.stig.rhel8:obj:29200" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fchown syscall" id="oval:mil.disa.stig.rhel8:obj:29200" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fchown\s+|(\s+|,)fchown(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fchown\s+|(\s+|,)fchown(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fchown syscall" id="oval:mil.disa.stig.rhel8:obj:29201" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fchown syscall" id="oval:mil.disa.stig.rhel8:obj:29201" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fchown\s+|(\s+|,)fchown(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fchown\s+|(\s+|,)fchown(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fchmodat syscall" id="oval:mil.disa.stig.rhel8:obj:29300" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fchmodat syscall" id="oval:mil.disa.stig.rhel8:obj:29300" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fchmodat\s+|(\s+|,)fchmodat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fchmodat\s+|(\s+|,)fchmodat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fchmodat syscall" id="oval:mil.disa.stig.rhel8:obj:29301" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fchmodat syscall" id="oval:mil.disa.stig.rhel8:obj:29301" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fchmodat\s+|(\s+|,)fchmodat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fchmodat\s+|(\s+|,)fchmodat(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fchmod syscall" id="oval:mil.disa.stig.rhel8:obj:29400" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="32-bit fchmod syscall" id="oval:mil.disa.stig.rhel8:obj:29400" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fchmod\s+|(\s+|,)fchmod(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+fchmod\s+|(\s+|,)fchmod(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fchmod syscall" id="oval:mil.disa.stig.rhel8:obj:29401" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="64-bit fchmod syscall" id="oval:mil.disa.stig.rhel8:obj:29401" version="3">
<filepath>/etc/audit/audit.rules</filepath>
- <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fchmod\s+|(\s+|,)fchmod(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)\S+)?\s*$</pattern>
+ <pattern operation="pattern match">^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+fchmod\s+|(\s+|,)fchmod(\s+|,))).*-F\s+auid&gt;=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$</pattern>
<instance datatype="int" operation="greater than or equal">1</instance>
</textfilecontent54_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:29500" version="2">
@@ -17552,7 +16352,7 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<rpminfo_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#linux" id="oval:mil.disa.stig.rhel8:obj:31700" version="1">
<name>rsh-server</name>
</rpminfo_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:31800" version="2">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:31800" version="4">
<path>/etc/modprobe.d</path>
<filename operation="pattern match">.*</filename>
<pattern operation="pattern match">^[ \t]*install[ \t]+atm[ \t]+/bin/true[ \t]*$</pattern>
@@ -17904,37 +16704,37 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<pattern operation="pattern match">^\s*ALL\s+ALL\=\(ALL(?:|\:ALL)\)\s+ALL\s*$</pattern>
<instance datatype="int">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41500" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41500" version="2">
<filepath>/etc/sudoers</filepath>
- <pattern operation="pattern match">^\s*Defaults \!targetpw\s*$</pattern>
+ <pattern operation="pattern match">^\s*Defaults\s+\!targetpw\s*$</pattern>
<instance datatype="int">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41501" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41501" version="2">
<path>/etc/sudoers.d</path>
<filename operation="pattern match">^.*$</filename>
- <pattern operation="pattern match">^\s*Defaults \!targetpw\s*$</pattern>
+ <pattern operation="pattern match">^\s*Defaults\s+\!targetpw\s*$</pattern>
<instance datatype="int">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41502" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41502" version="2">
<filepath>/etc/sudoers</filepath>
- <pattern operation="pattern match">^\s*Defaults \!rootpw\s*$</pattern>
+ <pattern operation="pattern match">^\s*Defaults\s+\!rootpw\s*$</pattern>
<instance datatype="int">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41503" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41503" version="2">
<path>/etc/sudoers.d</path>
<filename operation="pattern match">^.*$</filename>
- <pattern operation="pattern match">^\s*Defaults \!rootpw\s*$</pattern>
+ <pattern operation="pattern match">^\s*Defaults\s+\!rootpw\s*$</pattern>
<instance datatype="int">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41504" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41504" version="2">
<filepath>/etc/sudoers</filepath>
- <pattern operation="pattern match">^\s*Defaults \!runaspw\s*$</pattern>
+ <pattern operation="pattern match">^\s*Defaults\s+\!runaspw\s*$</pattern>
<instance datatype="int">1</instance>
</textfilecontent54_object>
- <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41505" version="1">
+ <textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41505" version="2">
<path>/etc/sudoers.d</path>
<filename operation="pattern match">^.*$</filename>
- <pattern operation="pattern match">^\s*Defaults \!runaspw\s*$</pattern>
+ <pattern operation="pattern match">^\s*Defaults\s+\!runaspw\s*$</pattern>
<instance datatype="int">1</instance>
</textfilecontent54_object>
<textfilecontent54_object xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:obj:41600" version="1">
@@ -17956,9 +16756,6 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:9801" version="1">
<subexpression datatype="int" operation="equals">1</subexpression>
</textfilecontent54_state>
- <textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="The minor version is equal to 1." id="oval:mil.disa.stig.rhel8:ste:10000" version="2">
- <subexpression datatype="int" operation="equals">1</subexpression>
- </textfilecontent54_state>
<textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="The minor version is equal to 2." id="oval:mil.disa.stig.rhel8:ste:10001" version="1">
<subexpression datatype="int" operation="equals">2</subexpression>
</textfilecontent54_state>
@@ -17995,7 +16792,7 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="Exclude hashes with leading '$6'." id="oval:mil.disa.stig.rhel8:ste:10401" version="1">
<subexpression datatype="string" operation="pattern match">^[$][6]</subexpression>
</textfilecontent54_state>
- <textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" comment="'rounds' is set to 5000 or more." id="oval:mil.disa.stig.rhel8:ste:10500" version="1">
+ <textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:10500" version="2">
<subexpression datatype="int" operation="greater than or equal">5000</subexpression>
</textfilecontent54_state>
<textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:10600" comment="GRUB superuser name" version="1">
@@ -18041,12 +16838,21 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<gwrite datatype="boolean">false</gwrite>
<owrite datatype="boolean">false</owrite>
</file_state>
- <textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:12300" version="1">
+ <rpminfo_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#linux" id="oval:mil.disa.stig.rhel8:ste:12300" version="2">
+ <version datatype="version" operation="greater than or equal">20210617</version>
+ </rpminfo_state>
+ <textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:12301" version="2">
<subexpression>TLSv1.2</subexpression>
</textfilecontent54_state>
- <textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:12301" version="1">
+ <textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:12302" version="1">
<subexpression>TLSv1.3</subexpression>
</textfilecontent54_state>
+ <textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:12303" version="1">
+ <subexpression>DTLSv1.2</subexpression>
+ </textfilecontent54_state>
+ <textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:12304" version="1">
+ <subexpression>DTLSv1.3</subexpression>
+ </textfilecontent54_state>
<file_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#unix" comment="symbolic links" id="oval:mil.disa.stig.rhel8:ste:12400" version="1">
<type datatype="string" operation="equals" entity_check="all">symbolic link</type>
</file_state>
@@ -18220,9 +17026,6 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:19200" version="1">
<subexpression datatype="int" operation="less than or equal">10</subexpression>
</textfilecontent54_state>
- <textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:19600" version="1" comment="1, 2, or 3">
- <subexpression datatype="string" operation="pattern match">^[123]$</subexpression>
- </textfilecontent54_state>
<textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:19700" version="2">
<subexpression datatype="int" operation="less than">0</subexpression>
</textfilecontent54_state>
@@ -18301,12 +17104,6 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
<textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:22302" version="3">
<subexpression operation="pattern match">(?i)^halt$</subexpression>
</textfilecontent54_state>
- <textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:22400" version="2">
- <subexpression operation="pattern match">(?i)^syslog$</subexpression>
- </textfilecontent54_state>
- <textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:22401" version="2">
- <subexpression operation="pattern match">(?i)^keep_logs$</subexpression>
- </textfilecontent54_state>
<textfilecontent54_state xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5#independent" id="oval:mil.disa.stig.rhel8:ste:22600" version="1">
<subexpression datatype="string" operation="pattern match">(?i)^yes$</subexpression>
</textfilecontent54_state>
@@ -18561,12 +17358,12 @@ If the value is set to an integer less than 0, the user's time stamp will not ex
</variables>
</oval_definitions>
</component>
- <component id="scap_mil.disa.stig_comp_U_RHEL_8_V1R3_STIG_SCAP_1-2_Benchmark-cpe-oval.xml" timestamp="2021-10-04T21:38:10">
+ <component id="scap_mil.disa.stig_comp_U_RHEL_8_V1R4_STIG_SCAP_1-2_Benchmark-cpe-oval.xml" timestamp="2022-01-03T11:44:34">
<oval_definitions xmlns="http://oval.mitre.org/XMLSchema/oval-definitions-5" xmlns:oval="http://oval.mitre.org/XMLSchema/oval-common-5">
<generator>
<oval:product_name>repotool</oval:product_name>
<oval:schema_version>5.10</oval:schema_version>
- <oval:timestamp>2021-10-04T21:38:10</oval:timestamp>
+ <oval:timestamp>2022-01-03T11:44:33</oval:timestamp>
</generator>
<definitions>
<definition class="inventory" id="oval:mil.disa.stig.rhel8:def:1" version="2">
diff --git a/shared/references/disa-stig-rhel8-v1r4-xccdf-manual.xml b/shared/references/disa-stig-rhel8-v1r5-xccdf-manual.xml
similarity index 81%
rename from shared/references/disa-stig-rhel8-v1r4-xccdf-manual.xml
rename to shared/references/disa-stig-rhel8-v1r5-xccdf-manual.xml
index 46c5fa15578..216e91f92c6 100644
--- a/shared/references/disa-stig-rhel8-v1r4-xccdf-manual.xml
+++ b/shared/references/disa-stig-rhel8-v1r5-xccdf-manual.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type='text/xsl' href='STIG_unclass.xsl'?><Benchmark xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:cpe="http://cpe.mitre.org/language/2.0" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/schema/xccdf-1.1.4.xsd http://cpe.mitre.org/dictionary/2.0 http://cpe.mitre.org/files/cpe-dictionary_2.1.xsd" id="RHEL_8_STIG" xml:lang="en" xmlns="http://checklists.nist.gov/xccdf/1.1"><status date="2021-08-18">accepted</status><title>Red Hat Enterprise Linux 8 Security Technical Implementation Guide</title><description>This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.</description><notice id="terms-of-use" xml:lang="en"></notice><front-matter xml:lang="en"></front-matter><rear-matter xml:lang="en"></rear-matter><reference href="https://cyber.mil"><dc:publisher>DISA</dc:publisher><dc:source>STIG.DOD.MIL</dc:source></reference><plain-text id="release-info">Release: 4 Benchmark Date: 27 Oct 2021</plain-text><plain-text id="generator">3.2.2.36079</plain-text><plain-text id="conventionsVersion">1.10.0</plain-text><version>1</version><Profile id="MAC-1_Classified"><title>I - Mission Critical Classified</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-230221" selected="true" /><select idref="V-230222" selected="true" /><select idref="V-230223" selected="true" /><select idref="V-230224" selected="true" /><select idref="V-230225" selected="true" /><select idref="V-230226" selected="true" /><select idref="V-230227" selected="true" /><select idref="V-230228" selected="true" /><select idref="V-230229" selected="true" /><select idref="V-230230" selected="true" /><select idref="V-230231" selected="true" /><select idref="V-230232" selected="true" /><select idref="V-230233" selected="true" /><select idref="V-230234" selected="true" /><select idref="V-230235" selected="true" /><select idref="V-230236" selected="true" /><select idref="V-230237" selected="true" /><select idref="V-230238" selected="true" /><select idref="V-230239" selected="true" /><select idref="V-230240" selected="true" /><select idref="V-230241" selected="true" /><select idref="V-230243" selected="true" /><select idref="V-230244" selected="true" /><select idref="V-230245" selected="true" /><select idref="V-230246" selected="true" /><select idref="V-230247" selected="true" /><select idref="V-230248" selected="true" /><select idref="V-230249" selected="true" /><select idref="V-230250" selected="true" /><select idref="V-230251" selected="true" /><select idref="V-230252" selected="true" /><select idref="V-230253" selected="true" /><select idref="V-230254" selected="true" /><select idref="V-230255" selected="true" /><select idref="V-230256" selected="true" /><select idref="V-230257" selected="true" /><select idref="V-230258" selected="true" /><select idref="V-230259" selected="true" /><select idref="V-230260" selected="true" /><select idref="V-230261" selected="true" /><select idref="V-230262" selected="true" /><select idref="V-230263" selected="true" /><select idref="V-230264" selected="true" /><select idref="V-230265" selected="true" /><select idref="V-230266" selected="true" /><select idref="V-230267" selected="true" /><select idref="V-230268" selected="true" /><select idref="V-230269" selected="true" /><select idref="V-230270" selected="true" /><select idref="V-230271" selected="true" /><select idref="V-230272" selected="true" /><select idref="V-230273" selected="true" /><select idref="V-230274" selected="true" /><select idref="V-230275" selected="true" /><select idref="
+<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type='text/xsl' href='STIG_unclass.xsl'?><Benchmark xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:cpe="http://cpe.mitre.org/language/2.0" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/schema/xccdf-1.1.4.xsd http://cpe.mitre.org/dictionary/2.0 http://cpe.mitre.org/files/cpe-dictionary_2.1.xsd" id="RHEL_8_STIG" xml:lang="en" xmlns="http://checklists.nist.gov/xccdf/1.1"><status date="2021-12-03">accepted</status><title>Red Hat Enterprise Linux 8 Security Technical Implementation Guide</title><description>This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.</description><notice id="terms-of-use" xml:lang="en"></notice><front-matter xml:lang="en"></front-matter><rear-matter xml:lang="en"></rear-matter><reference href="https://cyber.mil"><dc:publisher>DISA</dc:publisher><dc:source>STIG.DOD.MIL</dc:source></reference><plain-text id="release-info">Release: 5 Benchmark Date: 27 Jan 2022</plain-text><plain-text id="generator">3.2.2.36079</plain-text><plain-text id="conventionsVersion">1.10.0</plain-text><version>1</version><Profile id="MAC-1_Classified"><title>I - Mission Critical Classified</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-230221" selected="true" /><select idref="V-230222" selected="true" /><select idref="V-230223" selected="true" /><select idref="V-230224" selected="true" /><select idref="V-230225" selected="true" /><select idref="V-230226" selected="true" /><select idref="V-230227" selected="true" /><select idref="V-230228" selected="true" /><select idref="V-230229" selected="true" /><select idref="V-230230" selected="true" /><select idref="V-230231" selected="true" /><select idref="V-230232" selected="true" /><select idref="V-230233" selected="true" /><select idref="V-230234" selected="true" /><select idref="V-230235" selected="true" /><select idref="V-230236" selected="true" /><select idref="V-230237" selected="true" /><select idref="V-230238" selected="true" /><select idref="V-230239" selected="true" /><select idref="V-230240" selected="true" /><select idref="V-230241" selected="true" /><select idref="V-230243" selected="true" /><select idref="V-230244" selected="true" /><select idref="V-230245" selected="true" /><select idref="V-230246" selected="true" /><select idref="V-230247" selected="true" /><select idref="V-230248" selected="true" /><select idref="V-230249" selected="true" /><select idref="V-230250" selected="true" /><select idref="V-230251" selected="true" /><select idref="V-230252" selected="true" /><select idref="V-230253" selected="true" /><select idref="V-230254" selected="true" /><select idref="V-230255" selected="true" /><select idref="V-230256" selected="true" /><select idref="V-230257" selected="true" /><select idref="V-230258" selected="true" /><select idref="V-230259" selected="true" /><select idref="V-230260" selected="true" /><select idref="V-230261" selected="true" /><select idref="V-230262" selected="true" /><select idref="V-230263" selected="true" /><select idref="V-230264" selected="true" /><select idref="V-230265" selected="true" /><select idref="V-230266" selected="true" /><select idref="V-230267" selected="true" /><select idref="V-230268" selected="true" /><select idref="V-230269" selected="true" /><select idref="V-230270" selected="true" /><select idref="V-230271" selected="true" /><select idref="V-230272" selected="true" /><select idref="V-230273" selected="true" /><select idref="V-230274" selected="true" /><select idref="V-230275" selected="true" /><select idref="
Red Hat offers the Extended Update Support (EUS) ad-on to a Red Hat Enterprise Linux subscription, for a fee, for those customers who wish to standardize on a specific minor release for an extended period. The RHEL 8 minor releases eligible for EUS are 8.1, 8.2, 8.4, 8.6, and 8.8. Each RHEL 8 EUS stream is available for 24 months from the availability of the minor release. RHEL 8.10 will be the final minor release overall. For more details on the Red Hat Enterprise Linux Life Cycle visit https://access.redhat.com/support/policy/updates/errata.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-32865r567410_fix">Upgrade to a supported version of RHEL 8.</fixtext><fix id="F-32865r567410_fix" /><check system="C-32890r743912_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the version of the operating system is vendor supported.
@@ -80,13 +80,13 @@ $ sudo cat /proc/sys/crypto/fips_enabled
1
-If FIPS mode is not "on", the kernel boot parameter is not configured for FIPS mode, or the system does not have a value of "1" for "fips_enabled" in "/proc/sys/crypto", this is a finding.</check-content></check></Rule></Group><Group id="V-230224"><title>SRG-OS-000185-GPOS-00079</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230224r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-010030</version><title>All RHEL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection.</title><description>&lt;VulnDiscussion&gt;RHEL 8 systems handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.
+If FIPS mode is not "on", the kernel boot parameter is not configured for FIPS mode, or the system does not have a value of "1" for "fips_enabled" in "/proc/sys/crypto", this is a finding.</check-content></check></Rule></Group><Group id="V-230224"><title>SRG-OS-000185-GPOS-00079</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230224r809268_rule" weight="10.0" severity="medium"><version>RHEL-08-010030</version><title>All RHEL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection.</title><description>&lt;VulnDiscussion&gt;RHEL 8 systems handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.
Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields).
Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001199</ident><fixtext fixref="F-32868r567419_fix">Configure RHEL 8 to prevent unauthorized modification of all information at rest by using disk encryption.
-Encrypting a partition in an already installed system is more difficult, because existing partitions will need to be resized and changed. To encrypt an entire partition, dedicate a partition for encryption in the partition layout.</fixtext><fix id="F-32868r567419_fix" /><check system="C-32893r567418_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 prevents unauthorized disclosure or modification of all information requiring at-rest protection by using disk encryption.
+Encrypting a partition in an already installed system is more difficult, because existing partitions will need to be resized and changed. To encrypt an entire partition, dedicate a partition for encryption in the partition layout.</fixtext><fix id="F-32868r567419_fix" /><check system="C-32893r809267_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 prevents unauthorized disclosure or modification of all information requiring at-rest protection by using disk encryption.
If there is a documented and approved reason for not having data-at-rest encryption, this requirement is Not Applicable.
@@ -96,7 +96,7 @@ $ sudo blkid
/dev/mapper/rhel-root: UUID="67b7d7fe-de60-6fd0-befb-e6748cf97743" TYPE="crypto_LUKS"
-Every persistent disk partition present must be of type "crypto_LUKS". If any partitions other than pseudo file systems (such as /proc or /sys) are not type "crypto_LUKS", ask the administrator to indicate how the partitions are encrypted. If there is no evidence that all local disk partitions are encrypted, this is a finding.</check-content></check></Rule></Group><Group id="V-230225"><title>SRG-OS-000023-GPOS-00006</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230225r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-010040</version><title>RHEL 8 must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a ssh logon.</title><description>&lt;VulnDiscussion&gt;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.
+Every persistent disk partition present must be of type "crypto_LUKS". If any partitions other than the boot partition or pseudo file systems (such as /proc or /sys) are not type "crypto_LUKS", ask the administrator to indicate how the partitions are encrypted. If there is no evidence that these partitions are encrypted, this is a finding.</check-content></check></Rule></Group><Group id="V-230225"><title>SRG-OS-000023-GPOS-00006</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230225r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-010040</version><title>RHEL 8 must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a ssh logon.</title><description>&lt;VulnDiscussion&gt;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.
System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.
@@ -293,7 +293,7 @@ $ sudo grep -E '(auth.*|authpriv.*|daemon.*)' /etc/rsyslog.conf
auth.*;authpriv.*;daemon.* /var/log/secure
-If "auth.*", "authpriv.*" or "daemon.*" are not configured to be logged, this is a finding.</check-content></check></Rule></Group><Group id="V-230229"><title>SRG-OS-000066-GPOS-00034</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230229r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-010090</version><title>RHEL 8, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.</title><description>&lt;VulnDiscussion&gt;Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted.
+If "auth.*", "authpriv.*" or "daemon.*" are not configured to be logged, this is a finding.</check-content></check></Rule></Group><Group id="V-230229"><title>SRG-OS-000066-GPOS-00034</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230229r809270_rule" weight="10.0" severity="medium"><version>RHEL-08-010090</version><title>RHEL 8, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.</title><description>&lt;VulnDiscussion&gt;Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted.
A trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC.
@@ -301,11 +301,11 @@ When there is a chain of trust, usually the top entity to be trusted becomes the
This requirement verifies that a certification path to an accepted trust anchor is used for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement.
-Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000384-GPOS-00167&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000185</ident><fixtext fixref="F-32873r567434_fix">Configure RHEL 8, for PKI-based authentication, to validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.
+Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000384-GPOS-00167&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000185</ident><fixtext fixref="F-32873r809269_fix">Configure RHEL 8, for PKI-based authentication, to validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.
-Obtain a valid copy of the DoD root CA file from the PKI CA certificate bundle from cyber.mil and copy the DoD_PKE_CA_chain.pem into the following file:
+Obtain a valid copy of the DoD root CA file from the PKI CA certificate bundle at cyber.mil and copy into the following file:
-/etc/sssd/pki/sssd_auth_ca_db.pem</fixtext><fix id="F-32873r567434_fix" /><check system="C-32898r567433_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 for PKI-based authentication has valid certificates by constructing a certification path (which includes status information) to an accepted trust anchor.
+/etc/sssd/pki/sssd_auth_ca_db.pem</fixtext><fix id="F-32873r809269_fix" /><check system="C-32898r567433_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 for PKI-based authentication has valid certificates by constructing a certification path (which includes status information) to an accepted trust anchor.
Check that the system has a valid DoD root CA installed with the following command:
@@ -356,19 +356,19 @@ $ 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.</check-content></check></Rule></Group><Group id="V-230233"><title>SRG-OS-000073-GPOS-00041</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230233r743919_rule" weight="10.0" severity="medium"><version>RHEL-08-010130</version><title>The RHEL 8 password-auth file must be configured to use a sufficient number of hashing rounds.</title><description>&lt;VulnDiscussion&gt;The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required level of entropy.
+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.</check-content></check></Rule></Group><Group id="V-230233"><title>SRG-OS-000073-GPOS-00041</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230233r809273_rule" weight="10.0" severity="medium"><version>RHEL-08-010130</version><title>The RHEL 8 shadow password suite must be configured to use a sufficient number of hashing rounds.</title><description>&lt;VulnDiscussion&gt;The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required level of entropy.
-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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000196</ident><fixtext fixref="F-32877r743918_fix">Configure RHEL 8 to encrypt all stored passwords with a strong cryptographic hash.
+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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000196</ident><fixtext fixref="F-32877r809272_fix">Configure RHEL 8 to encrypt all stored passwords with a strong cryptographic hash.
-Edit/modify the following line in the "/etc/pam.d/password-auth" file and set "rounds" to a value no lower than "5000":
+Edit/modify the following line in the "/etc/login.defs" file and set "SHA_CRYPT_MIN_ROUNDS" to a value no lower than "5000":
-password sufficient pam_unix.so sha512 rounds=5000</fixtext><fix id="F-32877r743918_fix" /><check system="C-32902r743917_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Check that a minimum number of hash rounds is configured by running the following command:
+SHA_CRYPT_MIN_ROUNDS 5000</fixtext><fix id="F-32877r809272_fix" /><check system="C-32902r809271_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Check that a minimum number of hash rounds is configured by running the following command:
-$ sudo grep rounds /etc/pam.d/password-auth
+$ sudo egrep "^SHA_CRYPT_" /etc/login.defs
-password sufficient pam_unix.so sha512 rounds=5000
+If only one of "SHA_CRYPT_MIN_ROUNDS" or "SHA_CRYPT_MAX_ROUNDS" is set, and this value is below "5000", this is a finding.
-If "rounds" has a value below "5000", or is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230234"><title>SRG-OS-000080-GPOS-00048</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230234r743922_rule" weight="10.0" severity="high"><version>RHEL-08-010140</version><title>RHEL 8 operating systems booted with United Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user mode and maintenance.</title><description>&lt;VulnDiscussion&gt;If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 8 and is designed to require a password to boot into single-user mode or make modifications to the boot menu.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000213</ident><fixtext fixref="F-32878r743921_fix">Configure the system to require a grub bootloader password for the grub superusers account with the grub2-setpassword command, which creates/overwrites the /boot/efi/EFI/redhat/user.cfg file.
+If both "SHA_CRYPT_MIN_ROUNDS" and "SHA_CRYPT_MAX_ROUNDS" are set, and the highest value for either is below "5000", this is a finding.</check-content></check></Rule></Group><Group id="V-230234"><title>SRG-OS-000080-GPOS-00048</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230234r743922_rule" weight="10.0" severity="high"><version>RHEL-08-010140</version><title>RHEL 8 operating systems booted with United Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user mode and maintenance.</title><description>&lt;VulnDiscussion&gt;If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 8 and is designed to require a password to boot into single-user mode or make modifications to the boot menu.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000213</ident><fixtext fixref="F-32878r743921_fix">Configure the system to require a grub bootloader password for the grub superusers account with the grub2-setpassword command, which creates/overwrites the /boot/efi/EFI/redhat/user.cfg file.
Generate an encrypted grub2 password for the grub superusers account with the following command:
@@ -404,21 +404,21 @@ $ sudo grep sulogin-shell /usr/lib/systemd/system/rescue.service
ExecStart=-/usr/lib/systemd/systemd-sulogin-shell rescue
-If the "ExecStart" line is configured for anything other than "/usr/lib/systemd/systemd-sulogin-shell rescue", commented out, or missing, this is a finding.</check-content></check></Rule></Group><Group id="V-230237"><title>SRG-OS-000120-GPOS-00061</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230237r743931_rule" weight="10.0" severity="medium"><version>RHEL-08-010160</version><title>The RHEL 8 pam_unix.so module must be configured in the password-auth file to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.</title><description>&lt;VulnDiscussion&gt;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.
+If the "ExecStart" line is configured for anything other than "/usr/lib/systemd/systemd-sulogin-shell rescue", commented out, or missing, this is a finding.</check-content></check></Rule></Group><Group id="V-230237"><title>SRG-OS-000120-GPOS-00061</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230237r809276_rule" weight="10.0" severity="medium"><version>RHEL-08-010160</version><title>The RHEL 8 pam_unix.so module must be configured in the password-auth file to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.</title><description>&lt;VulnDiscussion&gt;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.
RHEL 8 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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000803</ident><fixtext fixref="F-32881r743930_fix">Configure RHEL 8 to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.
+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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000803</ident><fixtext fixref="F-32881r809275_fix">Configure RHEL 8 to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.
Edit/modify the following line in the "/etc/pam.d/password-auth" file to include the sha512 option for pam_unix.so:
-password sufficient pam_unix.so sha512 rounds=5000</fixtext><fix id="F-32881r743930_fix" /><check system="C-32906r743929_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that the pam_unix.so module is configured to use sha512.
+password sufficient pam_unix.so sha512</fixtext><fix id="F-32881r809275_fix" /><check system="C-32906r809274_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that the pam_unix.so module is configured to use sha512.
Check that the pam_unix.so module is configured to use sha512 in /etc/pam.d/password-auth with the following command:
$ sudo grep password /etc/pam.d/password-auth | grep pam_unix
-password sufficient pam_unix.so sha512 rounds=5000
+password sufficient pam_unix.so sha512
If "sha512" is missing, or is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230238"><title>SRG-OS-000120-GPOS-00061</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230238r646862_rule" weight="10.0" severity="medium"><version>RHEL-08-010161</version><title>RHEL 8 must prevent system daemons from using Kerberos for authentication.</title><description>&lt;VulnDiscussion&gt;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.
@@ -661,25 +661,40 @@ $ sudo update-crypto-policies --show
FIPS
-If the system-wide crypto policy is set to anything other than "FIPS", this is a finding.</check-content></check></Rule></Group><Group id="V-230255"><title>SRG-OS-000250-GPOS-00093</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230255r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-010294</version><title>The RHEL 8 operating system must implement DoD-approved TLS encryption in the OpenSSL package.</title><description>&lt;VulnDiscussion&gt;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.
-
-RHEL 8 incorporates system-wide crypto policies by default. The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/openssl.config file.
-
-Satisfies: SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174, SRG-OS-000125-GPOS-00065&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001453</ident><fixtext fixref="F-32899r567512_fix">Configure the RHEL 8 OpenSSL library to use only DoD-approved TLS encryption by editing the following line in the "/etc/crypto-policies/back-ends/opensslcnf.config" file:
-
-MinProtocol = TLSv1.2
-
-A reboot is required for the changes to take effect.</fixtext><fix id="F-32899r567512_fix" /><check system="C-32924r567511_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the OpenSSL library is configured to use only DoD-approved TLS encryption:
-
-$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
-
-MinProtocol = TLSv1.2
-
-If the "MinProtocol" is set to anything older than "TLSv1.2", this is a finding.</check-content></check></Rule></Group><Group id="V-230256"><title>SRG-OS-000250-GPOS-00093</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230256r792859_rule" weight="10.0" severity="medium"><version>RHEL-08-010295</version><title>The RHEL 8 operating system must implement DoD-approved TLS encryption in the GnuTLS package.</title><description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
+If the system-wide crypto policy is set to anything other than "FIPS", this is a finding.</check-content></check></Rule></Group><Group id="V-230255"><title>SRG-OS-000250-GPOS-00093</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230255r809382_rule" weight="10.0" severity="medium"><version>RHEL-08-010294</version><title>The RHEL 8 operating system must implement DoD-approved TLS encryption in the OpenSSL package.</title><description>&lt;VulnDiscussion&gt;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.
+
+RHEL 8 incorporates system-wide crypto policies by default. The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/openssl.config file.
+
+Satisfies: SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174, SRG-OS-000125-GPOS-00065&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001453</ident><fixtext fixref="F-32899r809381_fix">Configure the RHEL 8 OpenSSL library to use only DoD-approved TLS encryption by editing the following line in the "/etc/crypto-policies/back-ends/opensslcnf.config" file:
+
+For versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch:
+MinProtocol = TLSv1.2
+
+For version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer:
+TLS.MinProtocol = TLSv1.2
+DTLS.MinProtocol = DTLSv1.2
+A reboot is required for the changes to take effect.</fixtext><fix id="F-32899r809381_fix" /><check system="C-32924r809380_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the OpenSSL library is configured to use only DoD-approved TLS encryption:
+
+For versions prior to crypto-policies-20210617-1.gitc776d3e.el8.noarch:
+
+$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
+
+MinProtocol = TLSv1.2
+
+If the "MinProtocol" is set to anything older than "TLSv1.2", this is a finding.
+
+For version crypto-policies-20210617-1.gitc776d3e.el8.noarch and newer:
+
+$ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config
+
+TLS.MinProtocol = TLSv1.2
+DTLS.MinProtocol = DTLSv1.2
+
+If the "TLS.MinProtocol" is set to anything older than "TLSv1.2" or the "DTLS.MinProtocol" is set to anything older than DTLSv1.2, this is a finding.</check-content></check></Rule></Group><Group id="V-230256"><title>SRG-OS-000250-GPOS-00093</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230256r792859_rule" weight="10.0" severity="medium"><version>RHEL-08-010295</version><title>The RHEL 8 operating system must implement DoD-approved TLS encryption in the GnuTLS package.</title><description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Transport Layer Security (TLS) encryption is a required security setting as a number of known vulnerabilities have been reported against Secure Sockets Layer (SSL) and earlier versions of TLS. Encryption of private information is essential to ensuring data confidentiality. If private information is not encrypted, it can be intercepted and easily read by an unauthorized party. SQL Server must use a minimum of FIPS 140-2-approved TLS version 1.2, and all non-FIPS-approved SSL and TLS versions must be disabled. NIST SP 800-52 specifies the preferred configurations for government systems.
@@ -1077,23 +1092,23 @@ $ sudo yum list installed openssl-pkcs11
openssl-pkcs11.x86_64 0.4.8-2.el8 @anaconda
-If the "openssl-pkcs11" package is not installed, ask the administrator to indicate what type of multifactor authentication is being utilized and what packages are installed to support it. If there is no evidence of multifactor authentication being used, this is a finding.</check-content></check></Rule></Group><Group id="V-230274"><title>SRG-OS-000375-GPOS-00160</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230274r743945_rule" weight="10.0" severity="medium"><version>RHEL-08-010400</version><title>RHEL 8 must implement certificate status checking for multifactor authentication.</title><description>&lt;VulnDiscussion&gt;Using an authentication device, such as a DoD Common Access Card (CAC) or token that is separate from the information system, ensures that even if the information system is compromised, credentials stored on the authentication device will not be affected.
+If the "openssl-pkcs11" package is not installed, ask the administrator to indicate what type of multifactor authentication is being utilized and what packages are installed to support it. If there is no evidence of multifactor authentication being used, this is a finding.</check-content></check></Rule></Group><Group id="V-230274"><title>SRG-OS-000375-GPOS-00160</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230274r809281_rule" weight="10.0" severity="medium"><version>RHEL-08-010400</version><title>RHEL 8 must implement certificate status checking for multifactor authentication.</title><description>&lt;VulnDiscussion&gt;Using an authentication device, such as a DoD Common Access Card (CAC) or token that is separate from the information system, ensures that even if the information system is compromised, credentials stored on the authentication device will not be affected.
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 (PIV) card and the DoD CAC.
RHEL 8 includes multiple options for configuring certificate status checking, but for this requirement focuses on the System Security Services Daemon (SSSD). By default, sssd performs Online Certificate Status Protocol (OCSP) checking and certificate verification using a sha256 digest function.
-Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000377-GPOS-00162&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001948</ident><fixtext fixref="F-32918r567569_fix">Configure the operating system to implement certificate status checking for multifactor authentication.
+Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000377-GPOS-00162&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001948</ident><fixtext fixref="F-32918r809280_fix">Configure the operating system to implement certificate status checking for multifactor authentication.
Review the "/etc/sssd/sssd.conf" file to determine if the system is configured to prevent OCSP or certificate verification.
-Add the following line to the "/etc/sssd/sssd.conf" file:
+Add the following line to the [sssd] section of the "/etc/sssd/sssd.conf" file:
certificate_verification = ocsp_dgst=sha1
The "sssd" service must be restarted for the changes to take effect. To restart the "sssd" service, run the following command:
-$ sudo systemctl restart sssd.service</fixtext><fix id="F-32918r567569_fix" /><check system="C-32943r743944_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system implements certificate status checking for multifactor authentication.
+$ sudo systemctl restart sssd.service</fixtext><fix id="F-32918r809280_fix" /><check system="C-32943r743944_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system implements certificate status checking for multifactor authentication.
Check to see if Online Certificate Status Protocol (OCSP) is enabled and using the proper digest value on the system with the following command:
@@ -1455,23 +1470,7 @@ $ sudo grep -i PermitRootLogin /etc/ssh/sshd_config
PermitRootLogin no
-If the "PermitRootLogin" keyword is set to "yes", is missing, or is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230297"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230297r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-010560</version><title>The auditd service must be running in RHEL 8.</title><description>&lt;VulnDiscussion&gt;Configuring RHEL 8 to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across the 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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-32941r567638_fix">Start the auditd service, and enable the auditd service with the following commands:
-
-$ sudo systemctl start auditd.service
-
-$ sudo systemctl enable auditd.service</fixtext><fix id="F-32941r567638_fix" /><check system="C-32966r567637_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the audit service is enabled and active with the following commands:
-
-$ sudo systemctl is-enabled auditd
-
-enabled
-
-$ sudo systemctl is-active auditd
-
-active
-
-If the service is not "enabled" and "active" this is a finding.</check-content></check></Rule></Group><Group id="V-230298"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230298r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-010561</version><title>The rsyslog service must be running in RHEL 8.</title><description>&lt;VulnDiscussion&gt;Configuring RHEL 8 to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across the DoD that reflects the most restrictive security posture consistent with operational requirements.
+If the "PermitRootLogin" keyword is set to "yes", is missing, or is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230298"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230298r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-010561</version><title>The rsyslog service must be running in RHEL 8.</title><description>&lt;VulnDiscussion&gt;Configuring RHEL 8 to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across the 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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-32942r567641_fix">Start the auditd service, and enable the rsyslog service with the following commands:
@@ -2361,23 +2360,41 @@ $ sudo grep -i lock-command /etc/tmux.conf
set -g lock-command vlock
-If the "lock-command" is not set in the global settings to call "vlock", this is a finding.</check-content></check></Rule></Group><Group id="V-230349"><title>SRG-OS-000028-GPOS-00009</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230349r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-020041</version><title>RHEL 8 must ensure session control is automatically started at shell initialization.</title><description>&lt;VulnDiscussion&gt;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, RHEL 8 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.
-
-Tmux is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen. Red Hat endorses tmux as the recommended session controlling package.
-
-Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000056</ident><fixtext fixref="F-32993r567794_fix">Configure the operating system to initialize the tmux terminal multiplexer as each shell is called by adding the following line to the end of the "/etc/bashrc" configuration file:
-
-[ -n "$PS1" -a -z "$TMUX" ] &amp;&amp; exec tmux
-
-This setting will take effect at next logon.</fixtext><fix id="F-32993r567794_fix" /><check system="C-33018r567793_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system shell initialization file is configured to start each shell with the tmux terminal multiplexer with the following command:
-
-$ sudo grep -i tmux /etc/bashrc
+If the "lock-command" is not set in the global settings to call "vlock", this is a finding.</check-content></check></Rule></Group><Group id="V-230349"><title>SRG-OS-000028-GPOS-00009</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230349r810020_rule" weight="10.0" severity="medium"><version>RHEL-08-020041</version><title>RHEL 8 must ensure session control is automatically started at shell initialization.</title><description>&lt;VulnDiscussion&gt;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, RHEL 8 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.
+
+Tmux is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen. Red Hat endorses tmux as the recommended session controlling package.
+
+Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000056</ident><fixtext fixref="F-32993r809283_fix">Configure the operating system to initialize the tmux terminal multiplexer as each shell is called by adding the following lines to a custom.sh shell script in the /etc/profile.d/ directory:
-[ -n "$PS1" -a -z "$TMUX" ] &amp;&amp; exec tmux
+If [ "$PS1" ]; then
+parent=$(ps -o ppid= -p $$)
+name=$(ps -o comm= -p $parent)
+case "$name" in (sshd|login) exec tmux ;; esac
+fi
-If "tmux" is not configured as the example above, is commented out, or missing from the "/etc/bashrc" initialization file, this is a finding.</check-content></check></Rule></Group><Group id="V-230350"><title>SRG-OS-000028-GPOS-00009</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230350r627750_rule" weight="10.0" severity="low"><version>RHEL-08-020042</version><title>RHEL 8 must prevent users from disabling session control mechanisms.</title><description>&lt;VulnDiscussion&gt;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.
+This setting will take effect at next logon.</fixtext><fix id="F-32993r809283_fix" /><check system="C-33018r810019_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system shell initialization file is configured to start each shell with the tmux terminal multiplexer with the following commands:
+
+Determine if tmux is currently running:
+$ sudo ps all | grep tmux | grep -v grep
+
+If the command does not produce output, this is a finding.
+
+Determine the location of the tmux script:
+$ sudo grep tmux /etc/bashrc/etc/profile.d/*
+
+/etc/profile.d/tmux.sh: case "$name" in (sshd|login) exec tmux ;; esac
+
+Review the tmux script by using the following example:
+$ sudo 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) exec tmux ;; esac
+fi
+
+If "tmux" is not configured as the example above, is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-230350"><title>SRG-OS-000028-GPOS-00009</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230350r627750_rule" weight="10.0" severity="low"><version>RHEL-08-020042</version><title>RHEL 8 must prevent users from disabling session control mechanisms.</title><description>&lt;VulnDiscussion&gt;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, RHEL 8 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.
@@ -2520,31 +2537,23 @@ matchrule =&lt;SAN&gt;.*EDIPI@mil
maprule = (userCertificate;binary={cert!bin})
domains = testing.test
-If the certmap section does not exist, ask the System Administrator to indicate how certificates are mapped to accounts. If there is no evidence of certificate mapping, this is a finding.</check-content></check></Rule></Group><Group id="V-230356"><title>SRG-OS-000069-GPOS-00037</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230356r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-020100</version><title>RHEL 8 must ensure a password complexity module is enabled.</title><description>&lt;VulnDiscussion&gt;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. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.
-
-RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. This is set in both:
-/etc/pam.d/password-auth
-/etc/pam.d/system-auth
-
-Note the value of "retry" set in these configuration files should be between "1" and "3". Manual changes to the listed files may be overwritten by the "authselect" program.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000192</ident><fixtext fixref="F-33000r567815_fix">Configure the operating system to use "pwquality" to enforce password complexity rules.
+If the certmap section does not exist, ask the System Administrator to indicate how certificates are mapped to accounts. If there is no evidence of certificate mapping, this is a finding.</check-content></check></Rule></Group><Group id="V-230356"><title>SRG-OS-000069-GPOS-00037</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230356r809379_rule" weight="10.0" severity="medium"><version>RHEL-08-020100</version><title>RHEL 8 must ensure the password complexity module is enabled in the password-auth file.</title><description>&lt;VulnDiscussion&gt;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. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.
+
+RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. This is set in both:
+/etc/pam.d/password-auth
+/etc/pam.d/system-auth&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-33000r809286_fix">Configure the operating system to use "pwquality" to enforce password complexity rules.
-Add the following line to both "/etc/pam.d/password-auth" and "/etc/pam.d/system-auth" (or modify the line to have the required value):
+Add the following line to the "/etc/pam.d/password-auth" file (or modify the line to have the required value):
-password required pam_pwquality.so retry=3</fixtext><fix id="F-33000r567815_fix" /><check system="C-33025r567814_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system uses "pwquality" to enforce the password complexity rules.
+password required pam_pwquality.so</fixtext><fix id="F-33000r809286_fix" /><check system="C-33025r809285_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system uses "pwquality" to enforce the password complexity rules.
-Check for the use of "pwquality" with the following commands:
+Check for the use of "pwquality" in the password-auth file with the following command:
$ sudo cat /etc/pam.d/password-auth | grep pam_pwquality
-password required pam_pwquality.so retry=3
-
-$ sudo cat /etc/pam.d/system-auth | grep pam_pwquality
+password required pam_pwquality.so
-password required pam_pwquality.so retry=3
-
-If both commands do not return a line containing the value "pam_pwquality.so", or the line is commented out, this is a finding.
-
-If the value of "retry" is set to "0" or greater than "3", this is a finding.</check-content></check></Rule></Group><Group id="V-230357"><title>SRG-OS-000069-GPOS-00037</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230357r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-020110</version><title>RHEL 8 must enforce password complexity by requiring that at least one uppercase character be used.</title><description>&lt;VulnDiscussion&gt;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.
+If the command does not return a line containing the value "pam_pwquality.so", or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230357"><title>SRG-OS-000069-GPOS-00037</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230357r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-020110</version><title>RHEL 8 must enforce password complexity by requiring that at least one uppercase character be used.</title><description>&lt;VulnDiscussion&gt;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.
@@ -2586,7 +2595,7 @@ $ sudo grep dcredit /etc/security/pwquality.conf
dcredit = -1
-If the value of "dcredit" is a positive number or is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230360"><title>SRG-OS-000072-GPOS-00040</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230360r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-020140</version><title>RHEL 8 must require the maximum number of repeating characters of the same character class be limited to four when passwords are changed.</title><description>&lt;VulnDiscussion&gt;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.
+If the value of "dcredit" is a positive number or is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230360"><title>SRG-OS-000072-GPOS-00040</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230360r809289_rule" weight="10.0" severity="medium"><version>RHEL-08-020140</version><title>RHEL 8 must require the maximum number of repeating characters of the same character class be limited to four when passwords are changed.</title><description>&lt;VulnDiscussion&gt;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.
@@ -2594,13 +2603,13 @@ RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. The "
Add the following line to "/etc/security/pwquality.conf" conf (or modify the line to have the required value):
-maxclassrepeat = 4</fixtext><fix id="F-33004r567827_fix" /><check system="C-33029r567826_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Check for the value of the "maxclassrepeat" option in "/etc/security/pwquality.conf" with the following command:
+maxclassrepeat = 4</fixtext><fix id="F-33004r567827_fix" /><check system="C-33029r809288_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Check for the value of the "maxclassrepeat" option in "/etc/security/pwquality.conf" with the following command:
$ sudo grep maxclassrepeat /etc/security/pwquality.conf
maxclassrepeat = 4
-If the value of "maxclassrepeat" is set to more than "4" or is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230361"><title>SRG-OS-000072-GPOS-00040</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230361r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-020150</version><title>RHEL 8 must require the maximum number of repeating characters be limited to three when passwords are changed.</title><description>&lt;VulnDiscussion&gt;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.
+If the value of "maxclassrepeat" is set to "0", more than "4" or is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230361"><title>SRG-OS-000072-GPOS-00040</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230361r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-020150</version><title>RHEL 8 must require the maximum number of repeating characters be limited to three when passwords are changed.</title><description>&lt;VulnDiscussion&gt;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.
@@ -2675,21 +2684,21 @@ $ sudo awk -F: '$5 &gt; 60 {print $1 " " $5}' /etc/shadow
$ sudo awk -F: '$5 &lt;= 0 {print $1 " " $5}' /etc/shadow
-If any results are returned that are not associated with a system account, this is a finding.</check-content></check></Rule></Group><Group id="V-230368"><title>SRG-OS-000077-GPOS-00045</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230368r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-020220</version><title>RHEL 8 passwords must be prohibited from reuse for a minimum of five generations.</title><description>&lt;VulnDiscussion&gt;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 reuse their password consecutively when that password has exceeded its defined lifetime, the end result is a password that is not changed per policy requirements.
-
-RHEL 8 utilizes "pwquality" consecutively as a mechanism to enforce password complexity. This is set in both:
-/etc/pam.d/password-auth
-/etc/pam.d/system-auth.
-
-Note that manual changes to the listed files may be overwritten by the "authselect" program.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000200</ident><fixtext fixref="F-33012r567851_fix">Configure the operating system to prohibit password reuse for a minimum of five generations.
+If any results are returned that are not associated with a system account, this is a finding.</check-content></check></Rule></Group><Group id="V-230368"><title>SRG-OS-000077-GPOS-00045</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230368r810414_rule" weight="10.0" severity="medium"><version>RHEL-08-020220</version><title>RHEL 8 must be configured in the password-auth file to prohibit password reuse for a minimum of five generations.</title><description>&lt;VulnDiscussion&gt;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 reuse their password consecutively when that password has exceeded its defined lifetime, the end result is a password that is not changed per policy requirements.
+
+RHEL 8 uses "pwhistory" consecutively as a mechanism to prohibit password reuse. This is set in both:
+/etc/pam.d/password-auth
+/etc/pam.d/system-auth.
+
+Note that manual changes to the listed files may be overwritten by the "authselect" program.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000200</ident><fixtext fixref="F-33012r809291_fix">Configure the operating system in the password-auth file to prohibit password reuse for a minimum of five generations.
-Add the following line in "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" (or modify the line to have the required value):
+Add the following line in "/etc/pam.d/password-auth" (or modify the line to have the required value):
-password required pam_pwhistory.so use_authtok remember=5 retry=3</fixtext><fix id="F-33012r567851_fix" /><check system="C-33037r567850_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system prohibits password reuse for a minimum of five generations.
+password required pam_pwhistory.so use_authtok remember=5 retry=3</fixtext><fix id="F-33012r809291_fix" /><check system="C-33037r809290_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system is configured in the password-auth file to prohibit password reuse for a minimum of five generations.
-Check for the value of the "remember" argument in "/etc/pam.d/system-auth" and "/etc/pam.d/password-auth" with the following command:
+Check for the value of the "remember" argument in "/etc/pam.d/password-auth" with the following command:
-$ sudo grep -i remember /etc/pam.d/system-auth /etc/pam.d/password-auth
+$ sudo grep -i remember /etc/pam.d/password-auth
password required pam_pwhistory.so use_authtok remember=5 retry=3
@@ -3065,23 +3074,7 @@ $ sudo grep disk_error_action /etc/audit/auditd.conf
disk_error_action = HALT
-If the value of the "disk_error_action" option is not "SYSLOG", "SINGLE", or "HALT", or the line is commented out, ask the system administrator to indicate how the system takes appropriate action when an audit process failure occurs. If there is no evidence of appropriate action, this is a finding.</check-content></check></Rule></Group><Group id="V-230391"><title>SRG-OS-000047-GPOS-00023</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230391r743998_rule" weight="10.0" severity="medium"><version>RHEL-08-030050</version><title>The RHEL 8 System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) must be alerted when the audit storage volume is full.</title><description>&lt;VulnDiscussion&gt;It is critical that when RHEL 8 is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.
-
-When availability is an overriding concern, other approved actions in response to an audit failure are as follows:
-
-1) If the failure was caused by the lack of audit record storage capacity, RHEL 8 must continue generating audit records if possible (automatically restarting the audit service if necessary) and overwriting the oldest audit records in a first-in-first-out manner.
-
-2) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, RHEL 8 must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000140</ident><fixtext fixref="F-33035r743997_fix">Configure RHEL 8 to notify the System Administrator (SA) and Information System Security Officer (ISSO) when the audit storage volume is full by configuring the "max_log_file_action" parameter in the "/etc/audit/auditd.conf" file with the a value of "syslog" or "keep_logs":
-
-max_log_file_action = syslog</fixtext><fix id="F-33035r743997_fix" /><check system="C-33060r567919_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that the SA and ISSO (at a minimum) are notified when the audit storage volume is full.
-
-Check which action RHEL 8 takes when the audit storage volume is full with the following command:
-
-$ sudo grep max_log_file_action /etc/audit/auditd.conf
-
-max_log_file_action=syslog
-
-If the value of the "max_log_file_action" option is set to "ignore", "rotate", or "suspend", or the line is commented out, ask the system administrator to indicate how the system takes appropriate action when an audit storage volume is full. If there is no evidence of appropriate action, this is a finding.</check-content></check></Rule></Group><Group id="V-230392"><title>SRG-OS-000047-GPOS-00023</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230392r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030060</version><title>The RHEL 8 audit system must take appropriate action when the audit storage volume is full.</title><description>&lt;VulnDiscussion&gt;It is critical that when RHEL 8 is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.
+If the value of the "disk_error_action" option is not "SYSLOG", "SINGLE", or "HALT", or the line is commented out, ask the system administrator to indicate how the system takes appropriate action when an audit process failure occurs. If there is no evidence of appropriate action, this is a finding.</check-content></check></Rule></Group><Group id="V-230392"><title>SRG-OS-000047-GPOS-00023</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230392r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030060</version><title>The RHEL 8 audit system must take appropriate action when the audit storage volume is full.</title><description>&lt;VulnDiscussion&gt;It is critical that when RHEL 8 is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.
When availability is an overriding concern, other approved actions in response to an audit failure are as follows:
@@ -3453,127 +3446,40 @@ $ sudo grep -w /usr/bin/su /etc/audit/audit.rules
-a always,exit -F path=/usr/bin/su -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-priv_change
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230413"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230413r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030200</version><title>The RHEL 8 audit system must be configured to audit any usage of the lremovexattr system call.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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). "Lremovexattr" is a system call that removes extended attributes. This is used for removal of extended attributes from symbolic links.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33057r567986_fix">Configure RHEL 8 to audit the execution of the "lremovexattr" system call, by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S lremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33057r567986_fix" /><check system="C-33082r567985_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify if RHEL 8 is configured to audit the execution of the "lremovexattr" system call, by running the following command:
-
-$ sudo grep -w lremovexattr /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S lremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S lremovexattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S lremovexattr -F auid=0 -k perm_mod
-
-If the command does not return all lines, or the lines are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230414"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230414r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030210</version><title>The RHEL 8 audit system must be configured to audit any usage of the removexattr system call.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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). "Removexattr" is a system call that removes extended attributes.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33058r567989_fix">Configure RHEL 8 to audit the execution of the "removexattr" system call, by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S removexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S removexattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33058r567989_fix" /><check system="C-33083r567988_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify if RHEL 8 is configured to audit the execution of the "removexattr" system call, by running the following command:
-
-$ sudo grep -w removexattr /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S removexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S removexattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S removexattr -F auid=0 -k perm_mod
-
-If the command does not return all lines, or the lines are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230415"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230415r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030220</version><title>The RHEL 8 audit system must be configured to audit any usage of the lsetxattr system call.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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). "Lsetxattr" is a system call used to set an extended attribute value. This is used to set extended attributes on a symbolic link.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33059r567992_fix">Configure RHEL 8 to audit the execution of the "lsetxattr" system call, by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S lsetxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33059r567992_fix" /><check system="C-33084r567991_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify if RHEL 8 is configured to audit the execution of the "lsetxattr" system call, by running the following command:
-
-$ sudo grep -w lsetxattr /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S lsetxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S lsetxattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S lsetxattr -F auid=0 -k perm_mod
-
-If the command does not return all lines, or the lines are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230416"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230416r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030230</version><title>The RHEL 8 audit system must be configured to audit any usage of the fsetxattr system call.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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). "Fsetxattr" is a system call used to set an extended attribute value. This is used to set extended attributes on a file.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The auid representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33060r567995_fix">Configure RHEL 8 to audit the execution of the "fsetxattr" system call, by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S fsetxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33060r567995_fix" /><check system="C-33085r567994_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify if RHEL 8 is configured to audit the execution of the "fsetxattr" system call, by running the following command:
-
-$ sudo grep -w fsetxattr /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S fsetxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S fsetxattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S fsetxattr -F auid=0 -k perm_mod
-
-If the command does not return all lines, or the lines are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230417"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230417r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030240</version><title>The RHEL 8 audit system must be configured to audit any usage of the fremovexattr system call.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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). "Fremovexattr" is a system call that removes extended attributes. This is used for removal of extended attributes from a file.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33061r567998_fix">Configure RHEL 8 to audit the execution of the "fremovexattr" system call by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
+If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230413"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230413r810463_rule" weight="10.0" severity="medium"><version>RHEL-08-030200</version><title>The RHEL 8 audit system must be configured to audit any usage of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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).
+
+"Setxattr" is a system call used to set an extended attribute value.
+"Fsetxattr" is a system call used to set an extended attribute value. This is used to set extended attributes on a file.
+"Lsetxattr" is a system call used to set an extended attribute value. This is used to set extended attributes on a symbolic link.
+"Removexattr" is a system call that removes extended attributes.
+"Fremovexattr" is a system call that removes extended attributes. This is used for removal of extended attributes from a file.
+"Lremovexattr" is a system call that removes extended attributes. This is used for removal of extended attributes from symbolic links.
+
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+
+The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000462-GPOS-00206, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000474-GPOS-00219, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33057r809294_fix">Configure RHEL 8 to audit the execution of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
--a always,exit -F arch=b32 -S fremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -k perm_mod
+-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod
+-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33061r567998_fix" /><check system="C-33086r567997_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify if RHEL 8 is configured to audit the execution of the "fremovexattr" system call, by running the following command:
+The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33057r809294_fix" /><check system="C-33082r809293_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify if RHEL 8 is configured to audit the execution of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls by running the following command:
-$ sudo grep -w fremovexattr /etc/audit/audit.rules
+$ sudo grep xattr /etc/audit/audit.rules
--a always,exit -F arch=b32 -S fremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b32 -S fremovexattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S fremovexattr -F auid=0 -k perm_mod
+-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod
+-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod
-If the command does not return all lines, or the lines are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230418"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230418r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030250</version><title>Successful/unsuccessful uses of the chage command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 command does not return an audit rule for "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" or any of the lines returned are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230418"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230418r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030250</version><title>Successful/unsuccessful uses of the chage command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "chage" command is used to change or view user password expiry information.
@@ -3605,31 +3511,7 @@ $ sudo grep -w chcon /etc/audit/audit.rules
-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid&gt;=1000 -F auid!=unset -k perm_mod
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230420"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230420r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030270</version><title>The RHEL 8 audit system must be configured to audit any usage of the setxattr system call.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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). "Setxattr" is a system call used to set an extended attribute value.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33064r568007_fix">Configure RHEL 8 to audit the execution of the "setxattr" system call, by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S setxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S setxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S setxattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S setxattr -F auid=0 -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33064r568007_fix" /><check system="C-33089r619871_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify if RHEL 8 is configured to audit the execution of the "setxattr" system call, by running the following command:
-
-$ sudo grep -w setxattr /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S setxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S setxattr -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
--a always,exit -F arch=b32 -S setxattr -F auid=0 -k perm_mod
--a always,exit -F arch=b64 -S setxattr -F auid=0 -k perm_mod
-
-If the command does not return all lines, or the lines are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230421"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230421r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030280</version><title>Successful/unsuccessful uses of the ssh-agent in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230421"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230421r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030280</version><title>Successful/unsuccessful uses of the ssh-agent in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "ssh-agent" is a program to hold private keys used for public key authentication.
@@ -3903,115 +3785,52 @@ $ sudo grep -w newgrp /etc/audit/audit.rules
-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid&gt;=1000 -F auid!=unset -k priv_cmd
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230438"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230438r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030360</version><title>Successful/unsuccessful uses of the init_module command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "init_module" command is used to load a kernel module.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33082r568061_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "init_module" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S init_module -F auid&gt;=1000 -F auid!=unset -k module_chng
--a always,exit -F arch=b64 -S init_module -F auid&gt;=1000 -F auid!=unset -k module_chng
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33082r568061_fix" /><check system="C-33107r568060_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "init_module" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w "init_module" /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S init_module -F auid&gt;=1000 -F auid!=unset -k module_chng
--a always,exit -F arch=b64 -S init_module -F auid&gt;=1000 -F auid!=unset -k module_chng
-
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230439"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230439r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030361</version><title>Successful/unsuccessful uses of the rename command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "rename" command will rename the specified files by replacing the first occurrence of expression in their name by replacement.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33083r568064_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "rename" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S rename -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S rename -F auid&gt;=1000 -F auid!=unset -k delete
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33083r568064_fix" /><check system="C-33108r568063_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "rename" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w "rename" /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S rename -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S rename -F auid&gt;=1000 -F auid!=unset -k delete
-
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230440"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230440r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030362</version><title>Successful/unsuccessful uses of the renameat command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "renameat" command renames a file, moving it between directories if required.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33084r568067_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "renameat" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S renameat -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S renameat -F auid&gt;=1000 -F auid!=unset -k delete
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33084r568067_fix" /><check system="C-33109r568066_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "renameat" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w "renameat" /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S renameat -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S renameat -F auid&gt;=1000 -F auid!=unset -k delete
-
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230441"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230441r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030363</version><title>Successful/unsuccessful uses of the rmdir command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "rmdir" command removes empty directories.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33085r568070_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "rmdir" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S rmdir -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S rmdir -F auid&gt;=1000 -F auid!=unset -k delete
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33085r568070_fix" /><check system="C-33110r568069_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "rmdir" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w "rmdir" /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S rmdir -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S rmdir -F auid&gt;=1000 -F auid!=unset -k delete
-
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230442"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230442r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030364</version><title>Successful/unsuccessful uses of the unlink command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "unlink" command deletes a name from the filesystem. If that name was the last link to a file and no processes have the file open, the file is deleted and the space it was using is made available for reuse.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33086r568073_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "unlink" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S unlink -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S unlink -F auid&gt;=1000 -F auid!=unset -k delete
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33086r568073_fix" /><check system="C-33111r568072_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "unlink" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w "unlink" /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S unlink -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S unlink -F auid&gt;=1000 -F auid!=unset -k delete
-
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230443"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230443r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030365</version><title>Successful/unsuccessful uses of the unlinkat command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "unlinkat" system call operates in exactly the same way as either "unlink" or "rmdir" except for the differences described in the manual page.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33087r568076_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "unlinkat" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S unlinkat -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S unlinkat -F auid&gt;=1000 -F auid!=unset -k delete
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33087r568076_fix" /><check system="C-33112r568075_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "unlinkat" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w "unlinkat" /etc/audit/audit.rules
+If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230438"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230438r810464_rule" weight="10.0" severity="medium"><version>RHEL-08-030360</version><title>Successful/unsuccessful uses of the init_module and finit_module system calls in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "init_module" and "finit_module" system calls are used to load a kernel module.
+
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+
+The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33082r810448_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "init_module" and "finit_module" system calls by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
+
+-a always,exit -F arch=b32 -S init_module,finit_module -F auid&gt;=1000 -F auid!=unset -k module_chng
+-a always,exit -F arch=b64 -S init_module,finit_module -F auid&gt;=1000 -F auid!=unset -k module_chng
+
+The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33082r810448_fix" /><check system="C-33107r810447_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record upon successful/unsuccessful attempts to use the "init_module" and "finit_module" system calls by using the following command to check the file system rules in "/etc/audit/audit.rules":
+
+$ sudo grep init_module /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S init_module,finit_module -F auid&gt;=1000 -F auid!=unset -k module_chng
+-a always,exit -F arch=b64 -S init_module,finit_module -F auid&gt;=1000 -F auid!=unset -k module_chng
+
+If the command does not return an audit rule for "init_module" and "finit_module" or any of the lines returned are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230439"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230439r810465_rule" weight="10.0" severity="medium"><version>RHEL-08-030361</version><title>Successful/unsuccessful uses of the rename, unlink, rmdir, renameat, and unlinkat system calls in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "rename" system call will rename the specified files by replacing the first occurrence of expression in their name by replacement.
+
+The "unlink" system call deletes a name from the filesystem. If that name was the last link to a file and no processes have the file open, the file is deleted and the space it was using is made available for reuse.
+The "rmdir" system call removes empty directories.
+The "renameat" system call renames a file, moving it between directories if required.
+The "unlinkat" system call operates in exactly the same way as either "unlink" or "rmdir" except for the differences described in the manual page.
+
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+
+The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. Performance can be helped, however, by combining syscalls into one rule whenever possible.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33083r809301_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "rename", "unlink", "rmdir", "renameat", and "unlinkat" system calls by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
--a always,exit -F arch=b32 -S unlinkat -F auid&gt;=1000 -F auid!=unset -k delete
--a always,exit -F arch=b64 -S unlinkat -F auid&gt;=1000 -F auid!=unset -k delete
+-a always,exit -F arch=b32 -S rename,unlink,rmdir,renameat,unlinkat -F auid&gt;=1000 -F auid!=unset -k delete
+-a always,exit -F arch=b64 -S rename,unlink,rmdir,renameat,unlinkat -F auid&gt;=1000 -F auid!=unset -k delete
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230444"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230444r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030370</version><title>Successful/unsuccessful uses of the gpasswd command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33083r809301_fix" /><check system="C-33108r810451_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record upon successful/unsuccessful attempts to use the "rename", "unlink", "rmdir", "renameat", and "unlinkat" system calls by using the following command to check the file system rules in "/etc/audit/audit.rules":
+
+$ sudo grep 'rename\|unlink\|rmdir' /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S rename,unlink,rmdir,renameat,unlinkat -F auid&gt;=1000 -F auid!=unset -k delete
+-a always,exit -F arch=b64 -S rename,unlink,rmdir,renameat,unlinkat -F auid&gt;=1000 -F auid!=unset -k delete
+
+If the command does not return an audit rule for "rename", "unlink", "rmdir", "renameat", and "unlinkat" or any of the lines returned are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230444"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230444r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030370</version><title>Successful/unsuccessful uses of the gpasswd command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "gpasswd" command is used to administer /etc/group and /etc/gshadow. Every group can have administrators, members and a password.
@@ -4027,24 +3846,6 @@ $ sudo grep -w gpasswd /etc/audit/audit.rules
-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-gpasswd
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230445"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230445r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030380</version><title>Successful/unsuccessful uses of the finit_module command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "finit_module" command is used to load a kernel module.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33089r568082_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "finit_module" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S finit_module -F auid&gt;=1000 -F auid!=unset -k module_chng
--a always,exit -F arch=b64 -S finit_module -F auid&gt;=1000 -F auid!=unset -k module_chng
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33089r568082_fix" /><check system="C-33114r568081_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "finit_module" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w "finit_module" /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S finit_module -F auid&gt;=1000 -F auid!=unset -k module_chng
--a always,exit -F arch=b64 -S finit_module -F auid&gt;=1000 -F auid!=unset -k module_chng
-
If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230446"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230446r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030390</version><title>Successful/unsuccessful uses of the delete_module command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "delete_module" command is used to unload a kernel module.
@@ -4095,277 +3896,87 @@ $ sudo grep -w chsh /etc/audit/audit.rules
-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid&gt;=1000 -F auid!=unset -k priv_cmd
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230449"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230449r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030420</version><title>Successful/unsuccessful uses of the truncate command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "truncate" and "ftruncate" functions are used to truncate a file to a specified length.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33093r568094_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "truncate" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33093r568094_fix" /><check system="C-33118r568093_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "truncate" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -iw truncate /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
-
-If the command does not return all lines, or the lines are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230450"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230450r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030430</version><title>Successful/unsuccessful uses of the openat system call in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "openat" system call opens a file specified by a relative pathname.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33094r568097_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "openat" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33094r568097_fix" /><check system="C-33119r568096_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "openat" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -iw openat /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
-
-If the command does not return all lines, or the lines are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230451"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230451r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030440</version><title>Successful/unsuccessful uses of the open system call in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "open system" call opens a file specified by a pathname. If the specified file does not exist, it may optionally be created by "open".
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33095r568100_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "open" system call by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33095r568100_fix" /><check system="C-33120r568099_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "open" system call by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -iw open /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
-
-If the command does not return all lines, or the lines are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230452"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230452r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030450</version><title>Successful/unsuccessful uses of the open_by_handle_at system call in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "name_to_handle_at" and "open_by_handle_at" system calls split the functionality of openat into two parts: "name_to_handle_at" returns an opaque handle that corresponds to a specified file; "open_by_handle_at" opens the file corresponding to a handle returned by a previous call to "name_to_handle_at" and returns an open file descriptor.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33096r568103_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "open_by_handle_at" system call by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33096r568103_fix" /><check system="C-33121r568102_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "open_by_handle_at" system call by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -iw open_by_handle_at /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
-
-If the command does not return all lines, or the lines are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230453"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230453r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030460</version><title>Successful/unsuccessful uses of the ftruncate command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "truncate" and "ftruncate" functions are used to truncate a file to a specified length.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33097r568106_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "ftruncate" command by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33097r568106_fix" /><check system="C-33122r568105_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "ftruncate" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -iw ftruncate /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
-
-If the command does not return all lines, or the lines are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230454"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230454r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030470</version><title>Successful/unsuccessful uses of the creat system call in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "creat" system call is used to open and possibly create a file or device.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33098r568109_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "creat" system call by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33098r568109_fix" /><check system="C-33123r568108_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "creat" system call by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -iw creat /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-
--a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
-
-If the command does not return all lines, or the lines are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230455"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230455r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030480</version><title>Successful/unsuccessful uses of the chown command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "chown" command is used to change file owner and group.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33099r568112_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chown" command by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S chown -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S chown -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33099r568112_fix" /><check system="C-33124r568111_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "chown" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w chown /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S chown -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S chown -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230456"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230456r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030490</version><title>Successful/unsuccessful uses of the chmod command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "chmod" command changes the file mode bits of each given file according to mode, which can be either a symbolic representation of changes to make, or an octal number representing the bit pattern for the new mode bits.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33100r568115_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chmod" command by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S chmod -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S chmod -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33100r568115_fix" /><check system="C-33125r568114_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "chmod" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w chmod /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S chmod -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S chmod -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230457"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230457r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030500</version><title>Successful/unsuccessful uses of the lchown system call in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "lchown" system call is used to change the ownership of the file specified by a path, which does not dereference symbolic links.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33101r568118_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "lchown" system call by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S lchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S lchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33101r568118_fix" /><check system="C-33126r568117_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "lchown" system call by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w lchown /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S lchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S lchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230458"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230458r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030510</version><title>Successful/unsuccessful uses of the fchownat system call in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "fchownat" system call is used to change ownership of a file relative to a directory file descriptor.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33102r568121_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "fchownat" system call by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S fchownat -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fchownat -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33102r568121_fix" /><check system="C-33127r568120_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "fchownat" system call by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w fchownat /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S fchownat -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fchownat -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230459"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230459r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030520</version><title>Successful/unsuccessful uses of the fchown system call in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "fchown" system call is used to change the ownership of a file referred to by the open file descriptor.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33103r568124_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "fchown" system call by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S fchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33103r568124_fix" /><check system="C-33128r568123_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "fchown" system call by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w fchown /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S fchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230460"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230460r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030530</version><title>Successful/unsuccessful uses of the fchmodat system call in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "fchmodat" system call is used to change permissions of a file relative to a directory file descriptor.
-
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
-
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33104r568127_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "fchmodat" system call by adding or updating the following lines to "/etc/audit/rules.d/audit.rules":
-
--a always,exit -F arch=b32 -S fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33104r568127_fix" /><check system="C-33129r568126_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "fchmodat" system call by performing the following command to check the file system rules in "/etc/audit/audit.rules":
-
-$ sudo grep -w fchmodat /etc/audit/audit.rules
-
--a always,exit -F arch=b32 -S fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_mod
-
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230461"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230461r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030540</version><title>Successful/unsuccessful uses of the fchmod system call in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "fchmod" system call is used to change permissions of a file.
+If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230449"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230449r810455_rule" weight="10.0" severity="medium"><version>RHEL-08-030420</version><title>Successful/unsuccessful uses of the truncate, ftruncate, creat, open, openat, and open_by_handle_at system calls in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "truncate" and "ftruncate" functions are used to truncate a file to a specified length.
+
+The "creat" system call is used to open and possibly create a file or device.
+The "open" system call opens a file specified by a pathname. If the specified file does not exist, it may optionally be created by "open".
+The "openat" system call opens a file specified by a relative pathname.
+The "name_to_handle_at" and "open_by_handle_at" system calls split the functionality of "openat" into two parts: "name_to_handle_at" returns an opaque handle that corresponds to a specified file; "open_by_handle_at" opens the file corresponding to a handle returned by a previous call to "name_to_handle_at" and returns an open file descriptor.
+
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+
+The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33093r809304_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" system calls by adding or updating the following rules in the "/etc/audit/rules.d/audit.rules" file:
-When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+-a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
+-a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
-Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33105r568130_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "fchmod" system call by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
+-a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
+-a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
--a always,exit -F arch=b32 -S fchmod -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fchmod -F auid&gt;=1000 -F auid!=unset -k perm_mod
+The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33093r809304_fix" /><check system="C-33118r810454_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record upon successful/unsuccessful attempts to use the "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" system calls by using the following command to check the file system rules in "/etc/audit/audit.rules":
+
+$ sudo grep 'open\|truncate\|creat' /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
+-a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access
+
+-a always,exit -F arch=b32 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
+-a always,exit -F arch=b64 -S truncate,ftruncate,creat,open,openat,open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access
+
+If the output does not produce rules containing "-F exit=-EPERM", this is a finding.
+If the output does not produce rules containing "-F exit=-EACCES", this is a finding.
+If the command does not return an audit rule for "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" or any of the lines returned are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230455"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230455r810459_rule" weight="10.0" severity="medium"><version>RHEL-08-030480</version><title>Successful/unsuccessful uses of the chown, fchown, fchownat, and lchown system calls in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "chown" command is used to change file owner and group.
+
+The "fchown" system call is used to change the ownership of a file referred to by the open file descriptor.
+The "fchownat" system call is used to change ownership of a file relative to a directory file descriptor.
+The "lchown" system call is used to change the ownership of the file specified by a path, which does not dereference symbolic links.
+
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+
+The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance can be helped, however, by combining syscalls into one rule whenever possible.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33099r809307_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chown", "fchown", "fchownat", and "lchown" system calls by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
-The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33105r568130_fix" /><check system="C-33130r568129_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record when successful/unsuccessful attempts to use the "fchmod" system call by performing the following command to check the file system rules in "/etc/audit/audit.rules":
+-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
-$ sudo grep -w fchmod /etc/audit/audit.rules
+The audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33099r809307_fix" /><check system="C-33124r810458_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record upon successful/unsuccessful attempts to use the "chown", "fchown", "fchownat" and "lchown" system calls by using the following command to check the file system rules in "/etc/audit/audit.rules":
+
+$ sudo grep chown /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid&gt;=1000 -F auid!=unset -k perm_mod
+
+If audit rules are not defined for "chown", "fchown", "fchownat", and "lchown" or any of the lines returned are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230456"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230456r810462_rule" weight="10.0" severity="medium"><version>RHEL-08-030490</version><title>Successful/unsuccessful uses of the chmod, fchmod, and fchmodat system calls in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "chmod" system call changes the file mode bits of each given file according to mode, which can be either a symbolic representation of changes to make, or an octal number representing the bit pattern for the new mode bits.
+
+The "fchmod" system call is used to change permissions of a file.
+The "fchmodat" system call is used to change permissions of a file relative to a directory file descriptor.
+
+When a user logs on, the AUID is set to the UID of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to "-1". The AUID representation is an unsigned 32-bit integer, which equals "4294967295". The audit system interprets "-1", "4294967295", and "unset" in the same way.
+
+The system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to use syscall rules only when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. Performance can be helped, however, by combining syscalls into one rule whenever possible.
+
+Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215, SRG-OS-000064-GPOS-00033, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000169</ident><fixtext fixref="F-33100r809310_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chmod", "fchmod", and "fchmodat" syscalls by adding or updating the following line to "/etc/audit/rules.d/audit.rules":
--a always,exit -F arch=b32 -S fchmod -F auid&gt;=1000 -F auid!=unset -k perm_mod
--a always,exit -F arch=b64 -S fchmod -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_mod
-If the command does not return a line, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230462"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230462r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030550</version><title>Successful/unsuccessful uses of the sudo command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 audit daemon must be restarted for the changes to take effect.</fixtext><fix id="F-33100r809310_fix" /><check system="C-33125r810461_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 generates an audit record upon successful/unsuccessful attempts to use the "chmod", "fchmod", and "fchmodat" syscalls by using the following command to check the file system rules in "/etc/audit/audit.rules":
+
+$ sudo grep chmod /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_mod
+-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_mod
+
+If the command does not return an audit rule for "chmod", "fchmod", and "fchmodat", or any of the lines returned are commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-230462"><title>SRG-OS-000062-GPOS-00031</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230462r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030550</version><title>Successful/unsuccessful uses of the sudo command in RHEL 8 must generate an audit record.</title><description>&lt;VulnDiscussion&gt;Without generating audit records that are specific to the security and mission needs 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 "sudo" command allows a permitted user to execute a command as the superuser or another user, as specified by the security policy.
@@ -4714,17 +4325,17 @@ $ sudo egrep '(\/usr\/sbin\/(audit|au))' /etc/aide.conf
/usr/sbin/rsyslogd p+i+n+u+g+s+b+acl+xattrs+sha512
/usr/sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512
-If any of the audit tools listed above do not have an appropriate selection line, ask the system administrator to indicate what cryptographic mechanisms are being used to protect the integrity of the audit tools. If there is no evidence of integrity protection, this is a finding.</check-content></check></Rule></Group><Group id="V-230476"><title>SRG-OS-000341-GPOS-00132</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230476r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-030660</version><title>RHEL 8 must allocate audit record storage capacity to store at least one week of audit records, when audit records are not immediately sent to a central audit record storage facility.</title><description>&lt;VulnDiscussion&gt;To ensure RHEL 8 systems have a sufficient storage capacity in which to write the audit logs, RHEL 8 needs to be able to allocate audit record storage capacity.
+If any of the audit tools listed above do not have an appropriate selection line, ask the system administrator to indicate what cryptographic mechanisms are being used to protect the integrity of the audit tools. If there is no evidence of integrity protection, this is a finding.</check-content></check></Rule></Group><Group id="V-230476"><title>SRG-OS-000341-GPOS-00132</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230476r809313_rule" weight="10.0" severity="medium"><version>RHEL-08-030660</version><title>RHEL 8 must allocate audit record storage capacity to store at least one week of audit records, when audit records are not immediately sent to a central audit record storage facility.</title><description>&lt;VulnDiscussion&gt;To ensure RHEL 8 systems have a sufficient storage capacity in which to write the audit logs, RHEL 8 needs to be able to allocate audit record storage capacity.
The task of allocating audit record storage capacity is usually performed during initial installation of RHEL 8.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001849</ident><fixtext fixref="F-33120r568175_fix">Allocate enough storage capacity for at least one week of audit records when audit records are not immediately sent to a central audit record storage facility.
If audit records are stored on a partition made specifically for audit records, resize the partition with sufficient space to contain one week of audit records.
-If audit records are not stored on a partition made specifically for audit records, a new partition with sufficient space will need be to be created.</fixtext><fix id="F-33120r568175_fix" /><check system="C-33145r568174_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 allocates audit record storage capacity to store at least one week of audit records when audit records are not immediately sent to a central audit record storage facility.
+If audit records are not stored on a partition made specifically for audit records, a new partition with sufficient space will need be to be created.</fixtext><fix id="F-33120r568175_fix" /><check system="C-33145r809312_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify RHEL 8 allocates audit record storage capacity to store at least one week of audit records when audit records are not immediately sent to a central audit record storage facility.
Determine to which partition the audit records are being written with the following command:
-$ sudo grep log_file /etc/audit/auditd.conf
+$ sudo grep -iw log_file /etc/audit/auditd.conf
log_file = /var/log/audit/audit.log
Check the size of the partition to which audit records are written (with the example being /var/log/audit/) with the following command:
@@ -5016,29 +4627,18 @@ $ sudo yum remove rsh-server</fixtext><fix id="F-33136r568223_fix" /><check syst
$ sudo yum list installed rsh-server
-If the rsh-server package is installed, this is a finding.</check-content></check></Rule></Group><Group id="V-230493"><title>SRG-OS-000095-GPOS-00049</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230493r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-040020</version><title>RHEL 8 must cover or disable the built-in or attached camera when not in use.</title><description>&lt;VulnDiscussion&gt;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.
+If the rsh-server package is installed, this is a finding.</check-content></check></Rule></Group><Group id="V-230493"><title>SRG-OS-000095-GPOS-00049</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230493r809316_rule" weight="10.0" severity="medium"><version>RHEL-08-040020</version><title>RHEL 8 must cover or disable the built-in or attached camera when not in use.</title><description>&lt;VulnDiscussion&gt;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.
Failing to disconnect from collaborative computing devices (i.e., cameras) can result in subsequent compromises of organizational information. Providing easy methods to physically disconnect from such devices after a collaborative computing session helps to ensure participants actually carry out the disconnect activity without having to go through complex and tedious procedures.
-Satisfies: SRG-OS-000095-GPOS-00049, SRG-OS-000370-GPOS-00155&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000381</ident><fixtext fixref="F-33137r568226_fix">Configure the operating system to disable the built-in or attached camera when not in use.
-
-First determine the driver being used by the camera with the following command:
+Satisfies: SRG-OS-000095-GPOS-00049, SRG-OS-000370-GPOS-00155&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000381</ident><fixtext fixref="F-33137r809315_fix">Configure the operating system to disable the built-in or attached camera when not in use.
-$ sudo dmesg | grep -i video
+Build or modify the "/etc/modprobe.d/blacklist.conf" file by using the following example:
-[ 44.630131] ACPI: Video Device [VGA]
-[ 46.655714] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/LNXVIDEO:00/input/input7
-[ 46.670133] videodev: Linux video capture interface: v2.00
-[ 47.226424] uvcvideo: Found UVC 1.00 device WebCam (0402:7675)
-[ 47.235752] usbcore: registered new interface driver uvcvideo
-[ 47.235756] USB Video Class driver (1.1.1)
-
-Next, build or modify the "/etc/modprobe.d/blacklist.conf" file by using the following example:
-
-##Disable WebCam
+install uvcvideo /bin/true
blacklist uvcvideo
-Reboot the system for the settings to take effect.</fixtext><fix id="F-33137r568226_fix" /><check system="C-33162r568225_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>If the device or operating system does not have a camera installed, this requirement is not applicable.
+Reboot the system for the settings to take effect.</fixtext><fix id="F-33137r809315_fix" /><check system="C-33162r809314_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>If the device or operating system does not have a camera installed, this requirement is not applicable.
This requirement is not applicable to mobile devices (smartphones and tablets), where the use of the camera is a local AO decision.
@@ -5050,24 +4650,21 @@ For a built-in camera, the camera must be protected by a camera cover (e.g., lap
If the camera is not disconnected, covered, or physically disabled, determine if it is being disabled via software with the following commands:
-Determine if the camera is disabled via blacklist with the following command:
+Verify the operating system disables the ability to load the uvcvideo kernel module.
-$ sudo grep blacklist /etc/modprobe.d/*
+$ sudo grep -r uvcvideo /etc/modprobe.d/* | grep "/bin/true"
-/etc/modprobe.d/blacklist.conf:blacklist uvcvideo
+install uvcvideo /bin/true
-Determine if a camera driver is in use with the following command:
+If the command does not return any output, or the line is commented out, and the collaborative computing device has not been authorized for use, this is a finding.
-$ sudo dmesg | grep -i video
+Verify the camera is disabled via blacklist with the following command:
-[ 44.630131] ACPI: Video Device [VGA]
-[ 46.655714] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/LNXVIDEO:00/input/input7
-[ 46.670133] videodev: Linux video capture interface: v2.00
-[ 47.226424] uvcvideo: Found UVC 1.00 device WebCam (0402:7675)
-[ 47.235752] usbcore: registered new interface driver uvcvideo
-[ 47.235756] USB Video Class driver (1.1.1)
+$ sudo grep -r uvcvideo /etc/modprobe.d/* | grep "blacklist"
+
+blacklist uvcvideo
-If the camera driver blacklist is missing, a camera driver is determined to be in use, and the collaborative computing device has not been authorized for use, this is a finding.</check-content></check></Rule></Group><Group id="V-230494"><title>SRG-OS-000095-GPOS-00049</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230494r792911_rule" weight="10.0" severity="low"><version>RHEL-08-040021</version><title>RHEL 8 must disable the asynchronous transfer mode (ATM) protocol.</title><description>&lt;VulnDiscussion&gt;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.
+If the command does not return any output or the output is not "blacklist uvcvideo", and the collaborative computing device has not been authorized for use, this is a finding.</check-content></check></Rule></Group><Group id="V-230494"><title>SRG-OS-000095-GPOS-00049</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230494r792911_rule" weight="10.0" severity="low"><version>RHEL-08-040021</version><title>RHEL 8 must disable the asynchronous transfer mode (ATM) protocol.</title><description>&lt;VulnDiscussion&gt;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.
Failing to disconnect unused protocols can result in a system compromise.
@@ -5270,25 +4867,16 @@ autofs.service - Automounts filesystems on demand
Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled)
Active: inactive (dead)
-If the "autofs" status is set to "active" and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content></check></Rule></Group><Group id="V-230503"><title>SRG-OS-000114-GPOS-00059</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230503r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-040080</version><title>RHEL 8 must be configured to disable USB mass storage.</title><description>&lt;VulnDiscussion&gt;USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity.
+If the "autofs" status is set to "active" and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content></check></Rule></Group><Group id="V-230503"><title>SRG-OS-000114-GPOS-00059</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230503r809319_rule" weight="10.0" severity="medium"><version>RHEL-08-040080</version><title>RHEL 8 must be configured to disable USB mass storage.</title><description>&lt;VulnDiscussion&gt;USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity.
-Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000778</ident><fixtext fixref="F-33147r568256_fix">Configure the operating system to disable the ability to use the USB Storage kernel module.
+Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000778</ident><fixtext fixref="F-33147r809318_fix">Configure the operating system to disable the ability to use the USB Storage kernel module and the ability to use USB mass storage devices.
-Create a file under "/etc/modprobe.d" with the following command:
-
-$ sudo touch /etc/modprobe.d/usb-storage.conf
-
-Add the following line to the created file:
+Add or update the following lines in the file "/etc/modprobe.d/blacklist.conf":
install usb-storage /bin/true
+blacklist usb-storage
-Configure the operating system to disable the ability to use USB mass storage devices.
-
-$ sudo vi /etc/modprobe.d/blacklist.conf
-
-Add or update the line:
-
-blacklist usb-storage</fixtext><fix id="F-33147r568256_fix" /><check system="C-33172r568255_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system disables the ability to load the USB Storage kernel module.
+Reboot the system for the settings to take effect.</fixtext><fix id="F-33147r809318_fix" /><check system="C-33172r809317_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system disables the ability to load the USB Storage kernel module.
$ sudo grep -r usb-storage /etc/modprobe.d/* | grep -i "/bin/true"
@@ -5304,19 +4892,28 @@ $ sudo grep usb-storage /etc/modprobe.d/* | grep -i "blacklist"
blacklist usb-storage
-If the command does not return any output or the output is not "blacklist usb-storage", and use of USB storage devices is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content></check></Rule></Group><Group id="V-230504"><title>SRG-OS-000297-GPOS-00115</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230504r627750_rule" weight="10.0" severity="medium"><version>RHEL-08-040090</version><title>A RHEL 8 firewall must employ a deny-all, allow-by-exception policy for allowing connections to other systems.</title><description>&lt;VulnDiscussion&gt;Failure to restrict network connectivity only to authorized systems permits inbound connections from malicious systems. It also permits outbound connections that may facilitate exfiltration of DoD data.
+If the command does not return any output or the output is not "blacklist usb-storage" and use of USB storage devices is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content></check></Rule></Group><Group id="V-230504"><title>SRG-OS-000297-GPOS-00115</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230504r809321_rule" weight="10.0" severity="medium"><version>RHEL-08-040090</version><title>A RHEL 8 firewall must employ a deny-all, allow-by-exception policy for allowing connections to other systems.</title><description>&lt;VulnDiscussion&gt;Failure to restrict network connectivity only to authorized systems permits inbound connections from malicious systems. It also permits outbound connections that may facilitate exfiltration of DoD data.
-RHEL 8 incorporates the "firewalld" daemon, which allows for many different configurations. One of these configurations is zones. Zones can be utilized to a deny-all, allow-by-exception approach. The default "drop" zone will drop all incoming network packets unless it is explicitly allowed by the configuration file or is related to an outgoing network connection.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002314</ident><fixtext fixref="F-33148r568259_fix">Configure the "firewalld" daemon to employ a deny-all, allow-by-exception with the following commands:
+RHEL 8 incorporates the "firewalld" daemon, which allows for many different configurations. One of these configurations is zones. Zones can be utilized to a deny-all, allow-by-exception approach. The default "drop" zone will drop all incoming network packets unless it is explicitly allowed by the configuration file or is related to an outgoing network connection.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002314</ident><fixtext fixref="F-33148r809320_fix">Configure the "firewalld" daemon to employ a deny-all, allow-by-exception with the following commands:
$ sudo firewall-cmd --permanent --new-zone=[custom]
$ sudo cp /usr/lib/firewalld/zones/drop.xml /etc/firewalld/zones/[custom].xml
-This will provide a clean configuration file to work with that employs a deny-all approach. Next, add the exceptions that are required for mission functionality.
+This will provide a clean configuration file to work with that employs a deny-all approach. Note: Add the exceptions that are required for mission functionality and update the short title in the xml file to match the [custom] zone name.
+Reload the firewall rules to make the new [custom] zone available to load:
+$ sudo firewall-cmd --reload
+
+Set the default zone to the new [custom] zone:
$ sudo firewall-cmd --set-default-zone=[custom]
-Note: This is a runtime and permanent change.</fixtext><fix id="F-33148r568259_fix" /><check system="C-33173r568258_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify "firewalld" is configured to employ a deny-all, allow-by-exception policy for allowing connections to other systems with the following commands:
+Note: This is a runtime and permanent change.
+Add any interfaces to the new [custom] zone:
+$ sudo firewall-cmd --permanent --zone=[custom] --change-interface=ens33
+
+Reload the firewall rules for changes to take effect:
+$ sudo firewall-cmd --reload</fixtext><fix id="F-33148r809320_fix" /><check system="C-33173r568258_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify "firewalld" is configured to employ a deny-all, allow-by-exception policy for allowing connections to other systems with the following commands:
$ sudo firewall-cmd --state
@@ -6467,22 +6064,13 @@ $ sudo egrep "[+]?acl" /etc/aide.conf
VarFile = OwnerMode+n+l+X+acl
-If the "acl" rule is not being used on all selection lines in the "/etc/aide.conf" file, is commented out, or ACLs are not being checked by another file integrity tool, this is a finding.</check-content></check></Rule></Group><Group id="V-230553"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230553r646886_rule" weight="10.0" severity="medium"><version>RHEL-08-040320</version><title>The graphical display manager must not be installed on RHEL 8 unless approved.</title><description>&lt;VulnDiscussion&gt;Internet services that are not required for system or application processes must not be active to decrease the attack surface of the system. Graphical display managers have a long history of security vulnerabilities and must not be used, unless approved and documented.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-33197r646885_fix">Document the requirement for a graphical user interface with the ISSO or reinstall the operating system without the graphical user interface. If reinstallation is not feasible, then continue with the following procedure:
+If the "acl" rule is not being used on all selection lines in the "/etc/aide.conf" file, is commented out, or ACLs are not being checked by another file integrity tool, this is a finding.</check-content></check></Rule></Group><Group id="V-230553"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-230553r809324_rule" weight="10.0" severity="medium"><version>RHEL-08-040320</version><title>The graphical display manager must not be installed on RHEL 8 unless approved.</title><description>&lt;VulnDiscussion&gt;Internet services that are not required for system or application processes must not be active to decrease the attack surface of the system. Graphical display managers have a long history of security vulnerabilities and must not be used, unless approved and documented.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-33197r809323_fix">Document the requirement for a graphical user interface with the ISSO or reinstall the operating system without the graphical user interface. If reinstallation is not feasible, then continue with the following procedure:
Open an SSH session and enter the following commands:
-$ sudo systemctl set-default multi-user.target
-
$ sudo yum remove xorg-x11-server-Xorg xorg-x11-server-common xorg-x11-server-utils xorg-x11-server-Xwayland
-A reboot is required for the changes to take effect.</fixtext><fix id="F-33197r646885_fix" /><check system="C-33222r646884_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that the system is configured to boot to the command line:
-
-$ systemctl get-default
-multi-user.target
-
-If 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, this is a finding.
-
-Verify that a graphical user interface is not installed:
+A reboot is required for the changes to take effect.</fixtext><fix id="F-33197r809323_fix" /><check system="C-33222r809322_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that a graphical user interface is not installed:
$ rpm -qa | grep xorg | grep server
@@ -6610,11 +6198,11 @@ $ sudo grep -iw 'ALL' /etc/sudoers /etc/sudoers.d/*
If the either of the following entries are returned, this is a finding:
ALL ALL=(ALL) ALL
-ALL ALL=(ALL:ALL) ALL</check-content></check></Rule></Group><Group id="V-237642"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-237642r646896_rule" weight="10.0" severity="medium"><version>RHEL-08-010383</version><title>RHEL 8 must use the invoking user's password for privilege escalation when using "sudo".</title><description>&lt;VulnDiscussion&gt;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. If the rootpw, targetpw, or runaspw flags are defined and not disabled, by default the operating system will prompt the invoking user for the "root" user password.
+ALL ALL=(ALL:ALL) ALL</check-content></check></Rule></Group><Group id="V-237642"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-237642r809326_rule" weight="10.0" severity="medium"><version>RHEL-08-010383</version><title>RHEL 8 must use the invoking user's password for privilege escalation when using "sudo".</title><description>&lt;VulnDiscussion&gt;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. If the rootpw, targetpw, or runaspw flags are defined and not disabled, by default the operating system will prompt the invoking user for the "root" user password.
For more information on each of the listed configurations, reference the sudoers(5) manual page.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002227</ident><fixtext fixref="F-40824r646895_fix">Define the following in the Defaults section of the /etc/sudoers file or a configuration file in the /etc/sudoers.d/ directory:
Defaults !targetpw
Defaults !rootpw
-Defaults !runaspw</fixtext><fix id="F-40824r646895_fix" /><check system="C-40861r646894_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that the sudoers security policy is configured to use the invoking user's password for privilege escalation.
+Defaults !runaspw</fixtext><fix id="F-40824r646895_fix" /><check system="C-40861r809325_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that the sudoers security policy is configured to use the invoking user's password for privilege escalation.
$ sudo egrep -i '(!rootpw|!targetpw|!runaspw)' /etc/sudoers /etc/sudoers.d/* | grep -v '#'
@@ -6622,10 +6210,11 @@ $ sudo egrep -i '(!rootpw|!targetpw|!runaspw)' /etc/sudoers /etc/sudoers.d/* | g
/etc/sudoers:Defaults !rootpw
/etc/sudoers:Defaults !runaspw
-If no results are returned, this is a finding
+If no results are returned, this is a finding.
+If results are returned from more than one file location, 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.</check-content></check></Rule></Group><Group id="V-237643"><title>SRG-OS-000373-GPOS-00156</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-237643r792980_rule" weight="10.0" severity="medium"><version>RHEL-08-010384</version><title>RHEL 8 must require re-authentication when using the "sudo" command.</title><description>&lt;VulnDiscussion&gt;Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
+If "Defaults !runaspw" is not defined, this is a finding.</check-content></check></Rule></Group><Group id="V-237643"><title>SRG-OS-000373-GPOS-00156</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-237643r809328_rule" weight="10.0" severity="medium"><version>RHEL-08-010384</version><title>RHEL 8 must require re-authentication when using the "sudo" command.</title><description>&lt;VulnDiscussion&gt;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 organization requires the user to re-authenticate when using the "sudo" command.
@@ -6635,11 +6224,13 @@ $ sudo visudo
Add or modify the following line:
Defaults timestamp_timeout=[value]
-Note: The "[value]" must be a number that is greater than or equal to "0".</fixtext><fix id="F-40825r646898_fix" /><check system="C-40862r792979_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system requires re-authentication when using the "sudo" command to elevate privileges.
+Note: The "[value]" must be a number that is greater than or equal to "0".</fixtext><fix id="F-40825r646898_fix" /><check system="C-40862r809327_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system requires re-authentication when using the "sudo" command to elevate privileges.
$ sudo grep -i 'timestamp_timeout' /etc/sudoers /etc/sudoers.d/*
/etc/sudoers:Defaults timestamp_timeout=0
+If results are returned from more than one file location, this is a finding.
+
If "timestamp_timeout" is set to a negative number, is commented out, or no results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-244519"><title>SRG-OS-000023-GPOS-00006</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244519r743806_rule" weight="10.0" severity="medium"><version>RHEL-08-010049</version><title>RHEL 8 must display a banner before granting local or remote access to the system via a graphical user logon.</title><description>&lt;VulnDiscussion&gt;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.
System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.
@@ -6670,19 +6261,7 @@ $ sudo grep banner-message-enable /etc/dconf/db/local.d/*
banner-message-enable=true
-If "banner-message-enable" is set to "false" or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-244520"><title>SRG-OS-000073-GPOS-00041</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244520r743809_rule" weight="10.0" severity="medium"><version>RHEL-08-010131</version><title>The RHEL 8 system-auth file must be configured to use a sufficient number of hashing rounds.</title><description>&lt;VulnDiscussion&gt;The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required level of entropy.
-
-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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000196</ident><fixtext fixref="F-47752r743808_fix">Configure RHEL 8 to encrypt all stored passwords with a strong cryptographic hash.
-
-Edit/modify the following line in the "etc/pam.d/system-auth" file and set "rounds" to a value no lower than "5000":
-
-password sufficient pam_unix.so sha512 rounds=5000</fixtext><fix id="F-47752r743808_fix" /><check system="C-47795r743807_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Check that a minimum number of hash rounds is configured by running the following command:
-
-$ sudo grep rounds /etc/pam.d/system-auth
-
-password sufficient pam_unix.so sha512 rounds=5000
-
-If "rounds" has a value below "5000", or is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-244521"><title>SRG-OS-000080-GPOS-00048</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244521r792982_rule" weight="10.0" severity="medium"><version>RHEL-08-010141</version><title>RHEL 8 operating systems booted with United Extensible Firmware Interface (UEFI) must require a unique superusers name upon booting into single-user mode and maintenance.</title><description>&lt;VulnDiscussion&gt;If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 8 and is designed to require a password to boot into single-user mode or make modifications to the boot menu.
+If "banner-message-enable" is set to "false" or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-244521"><title>SRG-OS-000080-GPOS-00048</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244521r792982_rule" weight="10.0" severity="medium"><version>RHEL-08-010141</version><title>RHEL 8 operating systems booted with United Extensible Firmware Interface (UEFI) must require a unique superusers name upon booting into single-user mode and maintenance.</title><description>&lt;VulnDiscussion&gt;If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 8 and is designed to require a password to boot into single-user mode or make modifications to the boot menu.
The GRUB 2 superuser account is an account of last resort. Establishing a unique username for this account hardens the boot loader against brute force attacks. Due to the nature of the superuser account database being distinct from the OS account database, this allows the use of a username that is not among those within the OS account database. Examples of non-unique superusers names are root, superuser, unlock, etc.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000213</ident><fixtext fixref="F-47753r743811_fix">Configure the system to have a unique name for the grub superusers account.
@@ -6730,21 +6309,21 @@ $ sudo grep sulogin-shell /usr/lib/systemd/system/emergency.service
ExecStart=-/usr/lib/systemd/systemd-sulogin-shell emergency
-If the "ExecStart" line is configured for anything other than "/usr/lib/systemd/systemd-sulogin-shell emergency", commented out, or missing, this is a finding.</check-content></check></Rule></Group><Group id="V-244524"><title>SRG-OS-000120-GPOS-00061</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244524r743821_rule" weight="10.0" severity="medium"><version>RHEL-08-010159</version><title>The RHEL 8 pam_unix.so module must be configured in the system-auth file to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.</title><description>&lt;VulnDiscussion&gt;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.
+If the "ExecStart" line is configured for anything other than "/usr/lib/systemd/systemd-sulogin-shell emergency", commented out, or missing, this is a finding.</check-content></check></Rule></Group><Group id="V-244524"><title>SRG-OS-000120-GPOS-00061</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244524r809331_rule" weight="10.0" severity="medium"><version>RHEL-08-010159</version><title>The RHEL 8 pam_unix.so module must be configured in the system-auth file to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.</title><description>&lt;VulnDiscussion&gt;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.
RHEL 8 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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000803</ident><fixtext fixref="F-47756r743820_fix">Configure RHEL 8 to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.
+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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000803</ident><fixtext fixref="F-47756r809330_fix">Configure RHEL 8 to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.
Edit/modify the following line in the "/etc/pam.d/system-auth" file to include the sha512 option for pam_unix.so:
-password sufficient pam_unix.so sha512 rounds=5000</fixtext><fix id="F-47756r743820_fix" /><check system="C-47799r743819_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that pam_unix.so module is configured to use sha512.
+password sufficient pam_unix.so sha512</fixtext><fix id="F-47756r809330_fix" /><check system="C-47799r809329_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that pam_unix.so module is configured to use sha512.
Check that pam_unix.so module is configured to use sha512 in /etc/pam.d/system-auth with the following command:
$ sudo grep password /etc/pam.d/system-auth | grep pam_unix
-password sufficient pam_unix.so sha512 rounds=5000
+password sufficient pam_unix.so sha512
If "sha512" is missing, or is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-244525"><title>SRG-OS-000163-GPOS-00072</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244525r743824_rule" weight="10.0" severity="medium"><version>RHEL-08-010201</version><title>The RHEL 8 SSH daemon must be configured with a timeout interval.</title><description>&lt;VulnDiscussion&gt;Terminating an idle SSH 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 SSH session will also free up resources committed by the managed network element.
@@ -6769,7 +6348,7 @@ $ sudo grep -i clientalive /etc/ssh/sshd_config
ClientAliveInterval 600
ClientAliveCountMax 0
-If "ClientAliveInterval" does not exist, does not have a value of "600" or less in "/etc/ssh/sshd_config", or is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-244526"><title>SRG-OS-000250-GPOS-00093</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244526r743827_rule" weight="10.0" severity="medium"><version>RHEL-08-010287</version><title>The RHEL 8 SSH daemon must be configured to use system-wide crypto policies.</title><description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
+If "ClientAliveInterval" does not exist, does not have a value of "600" or less in "/etc/ssh/sshd_config", or is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-244526"><title>SRG-OS-000250-GPOS-00093</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244526r809334_rule" weight="10.0" severity="medium"><version>RHEL-08-010287</version><title>The RHEL 8 SSH daemon must be configured to use system-wide crypto policies.</title><description>&lt;VulnDiscussion&gt;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.
@@ -6777,17 +6356,17 @@ Cryptographic mechanisms used for protecting the integrity of information includ
RHEL 8 incorporates system-wide crypto policies by default. The SSH configuration file has no effect on the ciphers, MACs, or algorithms unless specifically defined in the /etc/sysconfig/sshd file. The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/ directory.
-Satisfies: SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174, SRG-OS-000125-GPOS-00065&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001453</ident><fixtext fixref="F-47758r743826_fix">Configure the RHEL 8 SSH daemon to use system-wide crypto policies by adding the following line to /etc/sysconfig/sshd:
+Satisfies: SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174, SRG-OS-000125-GPOS-00065&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001453</ident><fixtext fixref="F-47758r809333_fix">Configure the RHEL 8 SSH daemon to use system-wide crypto policies by adding the following line to /etc/sysconfig/sshd:
-# crypto_policy=
+# CRYPTO_POLICY=
-A reboot is required for the changes to take effect.</fixtext><fix id="F-47758r743826_fix" /><check system="C-47801r743825_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that system-wide crypto policies are in effect:
+A reboot is required for the changes to take effect.</fixtext><fix id="F-47758r809333_fix" /><check system="C-47801r809332_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that system-wide crypto policies are in effect:
-$ sudo grep -i crypto_policy /etc/sysconfig/sshd
+$ sudo grep CRYPTO_POLICY /etc/sysconfig/sshd
-# crypto_policy=
+# CRYPTO_POLICY=
-If the "crypto_policy" is uncommented, this is a finding.</check-content></check></Rule></Group><Group id="V-244527"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244527r743830_rule" weight="10.0" severity="low"><version>RHEL-08-010472</version><title>RHEL 8 must have the packages required to use the hardware random number generator entropy gatherer service.</title><description>&lt;VulnDiscussion&gt;The most important characteristic of a random number generator is its randomness, namely its ability to deliver random numbers that are impossible to predict. Entropy in computer security is associated with the unpredictability of a source of randomness. The random source with high entropy tends to achieve a uniform distribution of random values. Random number generators are one of the most important building blocks of cryptosystems.
+If the "CRYPTO_POLICY " is uncommented, this is a finding.</check-content></check></Rule></Group><Group id="V-244527"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244527r743830_rule" weight="10.0" severity="low"><version>RHEL-08-010472</version><title>RHEL 8 must have the packages required to use the hardware random number generator entropy gatherer service.</title><description>&lt;VulnDiscussion&gt;The most important characteristic of a random number generator is its randomness, namely its ability to deliver random numbers that are impossible to predict. Entropy in computer security is associated with the unpredictability of a source of randomness. The random source with high entropy tends to achieve a uniform distribution of random values. Random number generators are one of the most important building blocks of cryptosystems.
The rngd service feeds random data from hardware device to kernel random device. Quality (non-predictable) random number generation is important for several security functions (i.e., ciphers).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-47759r743829_fix">Install the packages required to enabled the hardware random number generator entropy gatherer service with the following command:
@@ -6819,13 +6398,13 @@ $ sudo grep /var/tmp /etc/fstab
UUID=c274f65f /var/tmp xfs noatime,nobarrier 1 2
-If a separate entry for "/var/tmp" is not in use, this is a finding.</check-content></check></Rule></Group><Group id="V-244530"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244530r743839_rule" weight="10.0" severity="medium"><version>RHEL-08-010572</version><title>RHEL 8 must prevent files with the setuid and setgid bit set from being executed on the /boot/efi directory.</title><description>&lt;VulnDiscussion&gt;The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-47762r743838_fix">Configure the "/etc/fstab" to use the "nosuid" option on the /boot/efi directory.</fixtext><fix id="F-47762r743838_fix" /><check system="C-47805r743837_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>For systems that use BIOS, this is Not Applicable.
+If a separate entry for "/var/tmp" is not in use, this is a finding.</check-content></check></Rule></Group><Group id="V-244530"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244530r809336_rule" weight="10.0" severity="medium"><version>RHEL-08-010572</version><title>RHEL 8 must prevent files with the setuid and setgid bit set from being executed on the /boot/efi directory.</title><description>&lt;VulnDiscussion&gt;The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-47762r743838_fix">Configure the "/etc/fstab" to use the "nosuid" option on the /boot/efi directory.</fixtext><fix id="F-47762r743838_fix" /><check system="C-47805r809335_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>For systems that use BIOS, this is Not Applicable.
Verify the /boot/efi directory is mounted with the "nosuid" option with the following command:
$ sudo mount | grep '\s/boot/efi\s'
-/dev/sda1 on /boot/efi type xfs (rw,nosuid,relatime,seclabe,attr2,inode64,noquota)
+/dev/sda1 on /boot/efi type vfat (rw,nosuid,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro)
If the /boot/efi file system does not have the "nosuid" option set, this is a finding.</check-content></check></Rule></Group><Group id="V-244531"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244531r743842_rule" weight="10.0" severity="medium"><version>RHEL-08-010731</version><title>All RHEL 8 local interactive user home directory files must have mode 0750 or less permissive.</title><description>&lt;VulnDiscussion&gt;Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-47763r743841_fix">Set the mode on files and directories in the local interactive user home directory with the following command:
@@ -7114,7 +6693,7 @@ fapolicyd.service - File Access Policy Daemon
Loaded: loaded (/usr/lib/systemd/system/fapolicyd.service; enabled; vendor preset: disabled)
Active: active (running)
-If fapolicyd is not enabled and running, this is a finding.</check-content></check></Rule></Group><Group id="V-244546"><title>SRG-OS-000368-GPOS-00154</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244546r743887_rule" weight="10.0" severity="medium"><version>RHEL-08-040137</version><title>The RHEL 8 fapolicy module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.</title><description>&lt;VulnDiscussion&gt;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.
+If fapolicyd is not enabled and running, this is a finding.</check-content></check></Rule></Group><Group id="V-244546"><title>SRG-OS-000368-GPOS-00154</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244546r809339_rule" weight="10.0" severity="medium"><version>RHEL-08-040137</version><title>The RHEL 8 fapolicy module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.</title><description>&lt;VulnDiscussion&gt;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.
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. Verification of whitelisted software occurs prior to execution or at system startup.
@@ -7124,11 +6703,7 @@ RHEL 8 ships with many optional packages. One such package is a file access poli
Proceed with caution with enforcing the use of this daemon. Improper configuration may render the system non-functional. The "fapolicyd" API is not namespace aware and can cause issues when launching or running containers.
-Satisfies: SRG-OS-000368-GPOS-00154, SRG-OS-000370-GPOS-00155, SRG-OS-000480-GPOS-00232&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001764</ident><fixtext fixref="F-47778r743886_fix">Configure RHEL 8 to employ a deny-all, permit-by-exception application whitelisting policy with "fapolicyd" using the following command:
-
-Note: Running this command requires a root shell
-
-# mount | egrep '^tmpfs| ext4| ext3| xfs' | awk '{ printf "%s\n", $3 }' &gt;&gt; /etc/fapolicyd/fapolicyd.mounts
+Satisfies: SRG-OS-000368-GPOS-00154, SRG-OS-000370-GPOS-00155, SRG-OS-000480-GPOS-00232&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001764</ident><fixtext fixref="F-47778r809338_fix">Configure RHEL 8 to employ a deny-all, permit-by-exception application whitelisting policy with "fapolicyd".
With the "fapolicyd" installed and enabled, configure the daemon to function in permissive mode until the whitelist is built correctly to avoid system lockout. Do this by editing the "/etc/fapolicyd/fapolicyd.conf" file with the following line:
@@ -7138,7 +6713,7 @@ Build the whitelist in the "/etc/fapolicyd/fapolicyd.rules" file ensuring the la
Once it is determined the whitelist is built correctly, set the fapolicyd to enforcing mode by editing the "permissive" line in the /etc/fapolicyd/fapolicyd.conf file.
-permissive = 0</fixtext><fix id="F-47778r743886_fix" /><check system="C-47821r743885_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the RHEL 8 "fapolicyd" employs a deny-all, permit-by-exception policy.
+permissive = 0</fixtext><fix id="F-47778r809338_fix" /><check system="C-47821r809337_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the RHEL 8 "fapolicyd" employs a deny-all, permit-by-exception policy.
Check that "fapolicyd" is in enforcement mode with the following command:
@@ -7146,7 +6721,7 @@ $ sudo grep permissive /etc/fapolicyd/fapolicyd.conf
permissive = 0
-Check that fapolicyd employs a deny-all policy on system mounts with the following commands:
+Check that fapolicyd employs a deny-all policy on system mounts with the following command:
$ sudo tail /etc/fapolicyd/fapolicyd.rules
@@ -7154,18 +6729,7 @@ allow exe=/usr/bin/python3.7 : ftype=text/x-python
deny_audit perm=any pattern=ld_so : all
deny perm=any all : all
-$ sudo cat /etc/fapolicyd/fapolicyd.mounts
-
-/dev/shm
-/run
-/sys/fs/cgroup
-/
-/home
-/boot
-/run/user/42
-/run/user/1000
-
-If fapolicyd is not running in enforcement mode on all system mounts with a deny-all, permit-by-exception policy, this is a finding.</check-content></check></Rule></Group><Group id="V-244547"><title>SRG-OS-000378-GPOS-00163</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244547r743890_rule" weight="10.0" severity="medium"><version>RHEL-08-040139</version><title>RHEL 8 must have the USBGuard installed.</title><description>&lt;VulnDiscussion&gt;Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
+If fapolicyd is not running in enforcement mode with a deny-all, permit-by-exception policy, this is a finding.</check-content></check></Rule></Group><Group id="V-244547"><title>SRG-OS-000378-GPOS-00163</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-244547r743890_rule" weight="10.0" severity="medium"><version>RHEL-08-040139</version><title>RHEL 8 must have the USBGuard installed.</title><description>&lt;VulnDiscussion&gt;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.
A new feature that RHEL 8 provides is the USBGuard software framework. The USBguard-daemon is the main component of the USBGuard software framework. It runs as a service in the background and enforces the USB device authorization policy for all USB devices. The policy is defined by a set of rules using a rule language described in the usbguard-rules.conf file. The policy and the authorization state of USB devices can be modified during runtime using the usbguard tool.
@@ -7511,4 +7075,201 @@ $ sudo grep -r net.ipv4.conf.all.forwarding /etc/sysctl.d/*.conf
If "net.ipv4.conf.all.forwarding" is not set to "0", is missing or commented out, this is a finding.
-If the configuration file does not begin with "99-", this is a finding.</check-content></check></Rule></Group></Benchmark>
\ No newline at end of file
+If the configuration file does not begin with "99-", this is a finding.</check-content></check></Rule></Group><Group id="V-251706"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251706r809342_rule" weight="10.0" severity="high"><version>RHEL-08-010121</version><title>The RHEL 8 operating system must not have accounts configured with blank or null passwords.</title><description>&lt;VulnDiscussion&gt;If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-55097r809341_fix">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]</fixtext><fix id="F-55097r809341_fix" /><check system="C-55143r809340_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>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.</check-content></check></Rule></Group><Group id="V-251707"><title>SRG-OS-000259-GPOS-00100</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251707r809345_rule" weight="10.0" severity="medium"><version>RHEL-08-010331</version><title>RHEL 8 library directories must have mode 755 or less permissive.</title><description>&lt;VulnDiscussion&gt;If RHEL 8 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 RHEL 8 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals will be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001499</ident><fixtext fixref="F-55098r809344_fix">Configure the library directories to be protected from unauthorized access. Run the following command, replacing "[DIRECTORY]" with any library directory with a mode more permissive than 755.
+
+$ sudo chmod 755 [DIRECTORY]</fixtext><fix id="F-55098r809344_fix" /><check system="C-55144r809343_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the system-wide shared library directories within "/lib", "/lib64", "/usr/lib" and "/usr/lib64" have mode "755" or less permissive with the following command:
+
+$ sudo find /lib /lib64 /usr/lib /usr/lib64 -perm /022 -type d -exec stat -c "%n %a" '{}' \;
+
+If any system-wide shared library directories are found to be group-writable or world-writable, this is a finding.</check-content></check></Rule></Group><Group id="V-251708"><title>SRG-OS-000259-GPOS-00100</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251708r810012_rule" weight="10.0" severity="medium"><version>RHEL-08-010341</version><title>RHEL 8 library directories must be owned by root.</title><description>&lt;VulnDiscussion&gt;If RHEL 8 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 RHEL 8 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals will be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001499</ident><fixtext fixref="F-55099r809347_fix">Configure the system-wide shared library directories within (/lib, /lib64, /usr/lib and /usr/lib64) to be protected from unauthorized access.
+
+Run the following command, replacing "[DIRECTORY]" with any library directory not owned by "root".
+
+$ sudo chown root [DIRECTORY]</fixtext><fix id="F-55099r809347_fix" /><check system="C-55145r810011_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the system-wide shared library directories are owned by "root" with the following command:
+
+$ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -user root -type d -exec stat -c "%n %U" '{}' \;
+
+If any system-wide shared library directory is returned, this is a finding.</check-content></check></Rule></Group><Group id="V-251709"><title>SRG-OS-000259-GPOS-00100</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251709r810014_rule" weight="10.0" severity="medium"><version>RHEL-08-010351</version><title>RHEL 8 library directories must be group-owned by root or a system account.</title><description>&lt;VulnDiscussion&gt;If RHEL 8 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 RHEL 8 with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals will be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001499</ident><fixtext fixref="F-55100r809350_fix">Configure the system-wide shared library directories (/lib, /lib64, /usr/lib and /usr/lib64) to be protected from unauthorized access.
+
+Run the following command, replacing "[DIRECTORY]" with any library directory not group-owned by "root".
+
+$ sudo chgrp root [DIRECTORY]</fixtext><fix id="F-55100r809350_fix" /><check system="C-55146r810013_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>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" '{}' \;
+
+If any system-wide shared library directory is returned and is not group-owned by a required system account, this is a finding.</check-content></check></Rule></Group><Group id="V-251710"><title>SRG-OS-000445-GPOS-00199</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251710r809354_rule" weight="10.0" severity="medium"><version>RHEL-08-010359</version><title>The RHEL 8 operating system must use a file integrity tool to verify correct operation of all security functions.</title><description>&lt;VulnDiscussion&gt;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 the RHEL 8 operating system performing security function verification/testing and/or systems and environments that require this functionality.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002696</ident><fixtext fixref="F-55101r809353_fix">Install the AIDE package by running the following command:
+
+$ sudo yum install aide</fixtext><fix id="F-55101r809353_fix" /><check system="C-55147r809352_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that Advanced Intrusion Detection Environment (AIDE) is installed and verifies the correct operation of all security functions.
+
+Check that the AIDE package is installed with the following command:
+
+$ sudo rpm -q aide
+
+aide-0.16-14.el8.x86_64
+
+If AIDE is not installed, ask the System Administrator how file integrity checks are performed on the system.
+
+If there is no application installed to perform integrity checks, this is a finding.</check-content></check></Rule></Group><Group id="V-251711"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251711r810015_rule" weight="10.0" severity="medium"><version>RHEL-08-010379</version><title>RHEL 8 must specify the default "include" directory for the /etc/sudoers file.</title><description>&lt;VulnDiscussion&gt;The "sudo" command allows authorized users to run programs (including shells) as other users, system users, and root. The "/etc/sudoers" file is used to configure authorized "sudo" users as well as the programs they are allowed to run. Some configuration options in the "/etc/sudoers" file allow configured users to run programs without re-authenticating. Use of these configuration options makes it easier for one compromised account to be used to compromise other accounts.
+
+It is possible to include other sudoers files from within the sudoers file currently being parsed using the #include and #includedir directives. When sudo reaches this line it will suspend processing of the current file (/etc/sudoers) and switch to the specified file/directory. Once the end of the included file(s) is reached, the rest of /etc/sudoers will be processed. Files that are included may themselves include other files. A hard limit of 128 nested include files is enforced to prevent include file loops.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-55102r809356_fix">Configure the /etc/sudoers file to only include the /etc/sudoers.d directory.
+
+Edit the /etc/sudoers file with the following command:
+
+$ sudo visudo
+
+Add or modify the following line:
+#includedir /etc/sudoers.d</fixtext><fix id="F-55102r809356_fix" /><check system="C-55148r809355_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system specifies only the default "include" directory for the /etc/sudoers file with the following command:
+
+$ sudo grep include /etc/sudoers
+
+#includedir /etc/sudoers.d
+
+If the results are not "/etc/sudoers.d" or additional files or directories are specified, this is a finding.
+
+Verify the operating system does not have nested "include" files or directories within the /etc/sudoers.d directory with the following command:
+
+$ sudo grep include /etc/sudoers.d/*
+
+If results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-251712"><title>SRG-OS-000373-GPOS-00156</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251712r810017_rule" weight="10.0" severity="medium"><version>RHEL-08-010385</version><title>The RHEL 8 operating system must not be configured to bypass password requirements for privilege escalation.</title><description>&lt;VulnDiscussion&gt;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.
+
+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002038</ident><fixtext fixref="F-55103r810016_fix">Configure the operating system to require users to supply a password for privilege escalation.
+
+Check the configuration of the "/etc/ pam.d/sudo" file with the following command:
+$ sudo vi /etc/pam.d/sudo
+
+Remove any occurrences of "pam_succeed_if" in the file.</fixtext><fix id="F-55103r810016_fix" /><check system="C-55149r809358_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system is not be 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.</check-content></check></Rule></Group><Group id="V-251713"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251713r810407_rule" weight="10.0" severity="medium"><version>RHEL-08-020101</version><title>RHEL 8 must ensure the password complexity module is enabled in the system-auth file.</title><description>&lt;VulnDiscussion&gt;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. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.
+
+RHEL 8 uses "pwquality" as a mechanism to enforce password complexity. This is set in both:
+/etc/pam.d/password-auth
+/etc/pam.d/system-auth&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-55104r810406_fix">Configure the operating system to use "pwquality" to enforce password complexity rules.
+
+Add the following line to the "/etc/pam.d/system-auth" file(or modify the line to have the required value):
+
+password required pam_pwquality.so</fixtext><fix id="F-55104r810406_fix" /><check system="C-55150r810405_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system uses "pwquality" to enforce the password complexity rules.
+
+Check for the use of "pwquality" in the system-auth file with the following command:
+
+$ sudo cat /etc/pam.d/system-auth | grep pam_pwquality
+
+password required pam_pwquality.so
+
+If the command does not return a line containing the value "pam_pwquality.so", or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-251714"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251714r810410_rule" weight="10.0" severity="medium"><version>RHEL-08-020102</version><title>RHEL 8 systems below version 8.4 must ensure the password complexity module in the system-auth file is configured for three retries or less.</title><description>&lt;VulnDiscussion&gt;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. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.
+
+RHEL 8 uses "pwquality" as a mechanism to enforce password complexity. This is set in both:
+/etc/pam.d/password-auth
+/etc/pam.d/system-auth
+
+By limiting the number of attempts to meet the pwquality module complexity requirements before returning with an error, the system will audit abnormal attempts at password changes.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-55105r810408_fix">Configure the operating system to limit the "pwquality" retry option to 3.
+
+Add the following line to the "/etc/pam.d/system-auth" file (or modify the line to have the required value):
+
+password required pam_pwquality.so retry=3</fixtext><fix id="F-55105r810408_fix" /><check system="C-55151r810409_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Note: This requirement applies to RHEL versions 8.0 through 8.3. If the system is RHEL version 8.4 or newer, this requirement is not applicable.
+
+Verify the operating system is configured to limit the "pwquality" retry option to 3.
+
+Check for the use of the "pwquality" retry option in the system-auth file with the following command:
+
+$ sudo cat /etc/pam.d/system-auth | grep pam_pwquality
+
+password required pam_pwquality.so retry=3
+
+If the value of "retry" is set to "0" or greater than "3", this is a finding.</check-content></check></Rule></Group><Group id="V-251715"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251715r810412_rule" weight="10.0" severity="medium"><version>RHEL-08-020103</version><title>RHEL 8 systems below version 8.4 must ensure the password complexity module in the password-auth file is configured for three retries or less.</title><description>&lt;VulnDiscussion&gt;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. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.
+
+RHEL 8 uses "pwquality" as a mechanism to enforce password complexity. This is set in both:
+/etc/pam.d/password-auth
+/etc/pam.d/system-auth
+
+By limiting the number of attempts to meet the pwquality module complexity requirements before returning with an error, the system will audit abnormal attempts at password changes.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-55106r810411_fix">Configure the operating system to limit the "pwquality" retry option to 3.
+
+Add the following line to the "/etc/pam.d/password-auth" file (or modify the line to have the required value):
+
+password required pam_pwquality.so retry=3</fixtext><fix id="F-55106r810411_fix" /><check system="C-55152r809367_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Note: This requirement applies to RHEL versions 8.0 through 8.3. If the system is RHEL version 8.4 or newer, this requirement is not applicable.
+
+Verify the operating system is configured to limit the "pwquality" retry option to 3.
+
+Check for the use of the "pwquality" retry option in the password-auth file with the following command:
+
+$ sudo cat /etc/pam.d/password-auth | grep pam_pwquality
+
+password required pam_pwquality.so retry=3
+
+If the value of "retry" is set to "0" or greater than "3", this is a finding.</check-content></check></Rule></Group><Group id="V-251716"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251716r809372_rule" weight="10.0" severity="medium"><version>RHEL-08-020104</version><title>RHEL 8 systems, version 8.4 and above, must ensure the password complexity module is configured for three retries or less.</title><description>&lt;VulnDiscussion&gt;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. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.
+
+RHEL 8 utilizes "pwquality" as a mechanism to enforce password complexity. This is set in both:
+/etc/pam.d/password-auth
+/etc/pam.d/system-auth
+By limiting the number of attempts to meet the pwquality module complexity requirements before returning with an error, the system will audit abnormal attempts at password changes.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-55107r809371_fix">Configure the operating system to limit the "pwquality" retry option to 3.
+
+Add the following line to the "/etc/security/pwquality.conf" file(or modify the line to have the required value):
+
+retry = 3</fixtext><fix id="F-55107r809371_fix" /><check system="C-55153r809370_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Note: This requirement applies to RHEL versions 8.4 or newer. If the system is RHEL below version 8.4, this requirement is not applicable.
+
+Verify the operating system is configured to limit the "pwquality" retry option to 3.
+
+Check for the use of the "pwquality" retry option with the following command:
+
+$ sudo grep retry /etc/security/pwquality.conf
+
+retry = 3
+
+If the value of "retry" is set to "0" or greater than "3", is commented out or missing, this is a finding.
+
+Check for the use of the "pwquality" retry option in the system-auth and password-auth files with the following command:
+
+$ sudo grep retry /etc/pam.d/system-auth /etc/pam.d/password-auth
+
+If the command returns any results, this is a finding.</check-content></check></Rule></Group><Group id="V-251717"><title>SRG-OS-000077-GPOS-00045</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251717r810415_rule" weight="10.0" severity="medium"><version>RHEL-08-020221</version><title>RHEL 8 must be configured in the system-auth file to prohibit password reuse for a minimum of five generations.</title><description>&lt;VulnDiscussion&gt;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 reuse their password consecutively when that password has exceeded its defined lifetime, the end result is a password that is not changed per policy requirements.
+
+RHEL 8 uses "pwhistory" consecutively as a mechanism to prohibit password reuse. This is set in both:
+/etc/pam.d/password-auth
+/etc/pam.d/system-auth.
+
+Note that manual changes to the listed files may be overwritten by the "authselect" program.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000200</ident><fixtext fixref="F-55108r809374_fix">Configure the operating system in the system-auth file to prohibit password reuse for a minimum of five generations.
+
+Add the following line in "/etc/pam.d/system-auth" (or modify the line to have the required value):
+
+password required pam_pwhistory.so use_authtok remember=5 retry=3</fixtext><fix id="F-55108r809374_fix" /><check system="C-55154r809373_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify the operating system is configured in the system-auth file to prohibit password reuse for a minimum of five generations.
+
+Check for the value of the "remember" argument in "/etc/pam.d/password-auth" with the following command:
+
+$ sudo grep -i remember /etc/pam.d/password-auth
+
+password required pam_pwhistory.so use_authtok remember=5 retry=3
+
+If the line containing "pam_pwhistory.so" does not have the "remember" module argument set, is commented out, or the value of the "remember" module argument is set to less than "5", this is a finding.</check-content></check></Rule></Group><Group id="V-251718"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-251718r809378_rule" weight="10.0" severity="medium"><version>RHEL-08-040321</version><title>The graphical display manager must not be the default target on RHEL 8 unless approved.</title><description>&lt;VulnDiscussion&gt;Internet services that are not required for system or application processes must not be active to decrease the attack surface of the system. Graphical display managers have a long history of security vulnerabilities and must not be used, unless approved and documented.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat Enterprise Linux 8</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat Enterprise Linux 8</dc:subject><dc:identifier>2921</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-55109r809377_fix">Document the requirement for a graphical user interface with the ISSO or reinstall the operating system without the graphical user interface. If reinstallation is not feasible, then continue with the following procedure:
+
+Open an SSH session and enter the following commands:
+
+$ sudo systemctl set-default multi-user.target
+
+A reboot is required for the changes to take effect.</fixtext><fix id="F-55109r809377_fix" /><check system="C-55155r809376_chk"><check-content-ref href="Red_Hat_Enterprise_Linux_8_STIG.xml" name="M" /><check-content>Verify that the system is configured to boot to the command line:
+
+$ systemctl get-default
+multi-user.target
+
+If 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, this is a finding.</check-content></check></Rule></Group></Benchmark>
\ No newline at end of file
diff --git a/tests/data/profile_stability/rhel8/stig.profile b/tests/data/profile_stability/rhel8/stig.profile
index b5621425b96..9c157b7134d 100644
--- a/tests/data/profile_stability/rhel8/stig.profile
+++ b/tests/data/profile_stability/rhel8/stig.profile
@@ -1,7 +1,7 @@
title: DISA STIG for Red Hat Enterprise Linux 8
description: 'This profile contains configuration checks that align to the
- DISA STIG for Red Hat Enterprise Linux 8 V1R4.
+ DISA STIG for Red Hat Enterprise Linux 8 V1R5.
In addition to being applicable to Red Hat Enterprise Linux 8, DISA recognizes
@@ -23,7 +23,7 @@ description: 'This profile contains configuration checks that align to the
- Red Hat Containers with a Red Hat Enterprise Linux 8 image'
extends: null
metadata:
- version: V1R4
+ version: V1R5
SMEs:
- mab879
- ggbecker
diff --git a/tests/data/profile_stability/rhel8/stig_gui.profile b/tests/data/profile_stability/rhel8/stig_gui.profile
index 31221ed632c..470669753f5 100644
--- a/tests/data/profile_stability/rhel8/stig_gui.profile
+++ b/tests/data/profile_stability/rhel8/stig_gui.profile
@@ -1,7 +1,7 @@
title: DISA STIG with GUI for Red Hat Enterprise Linux 8
description: 'This profile contains configuration checks that align to the
- DISA STIG with GUI for Red Hat Enterprise Linux 8 V1R4.
+ DISA STIG with GUI for Red Hat Enterprise Linux 8 V1R5.
In addition to being applicable to Red Hat Enterprise Linux 8, DISA recognizes
@@ -34,7 +34,7 @@ description: 'This profile contains configuration checks that align to the
standard DISA STIG for Red Hat Enterprise Linux 8 profile.'
extends: null
metadata:
- version: V1R4
+ version: V1R5
SMEs:
- mab879
- ggbecker