File: disa-stig-ubuntu2204-v2r3-xccdf-manual.xml

package info (click to toggle)
scap-security-guide 0.1.78-1
links: PTS, VCS
area: main
in suites: forky, sid
size: 114,600 kB
sloc: xml: 245,305; sh: 84,381; python: 33,093; makefile: 27
file content (3180 lines) | stat: -rw-r--r-- 610,224 bytes
<?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="CAN_Ubuntu_22-04_LTS_STIG" xml:lang="en" xmlns="http://checklists.nist.gov/xccdf/1.1"><status date="2024-11-25">accepted</status><title>Canonical Ubuntu 22.04 LTS 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: 3 Benchmark Date: 30 Jan 2025</plain-text><plain-text id="generator">3.5</plain-text><plain-text id="conventionsVersion">1.10.0</plain-text><version>2</version><Profile id="MAC-1_Classified"><title>I - Mission Critical Classified</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-260469" selected="true" /><select idref="V-260470" selected="true" /><select idref="V-260471" selected="true" /><select idref="V-260472" selected="true" /><select idref="V-260473" selected="true" /><select idref="V-260474" selected="true" /><select idref="V-260475" selected="true" /><select idref="V-260476" selected="true" /><select idref="V-260477" selected="true" /><select idref="V-260478" selected="true" /><select idref="V-260479" selected="true" /><select idref="V-260480" selected="true" /><select idref="V-260481" selected="true" /><select idref="V-260482" selected="true" /><select idref="V-260483" selected="true" /><select idref="V-260484" selected="true" /><select idref="V-260485" selected="true" /><select idref="V-260486" selected="true" /><select idref="V-260487" selected="true" /><select idref="V-260488" selected="true" /><select idref="V-260489" selected="true" /><select idref="V-260490" selected="true" /><select idref="V-260491" selected="true" /><select idref="V-260492" selected="true" /><select idref="V-260493" selected="true" /><select idref="V-260494" selected="true" /><select idref="V-260495" selected="true" /><select idref="V-260496" selected="true" /><select idref="V-260497" selected="true" /><select idref="V-260498" selected="true" /><select idref="V-260499" selected="true" /><select idref="V-260500" selected="true" /><select idref="V-260501" selected="true" /><select idref="V-260502" selected="true" /><select idref="V-260503" selected="true" /><select idref="V-260504" selected="true" /><select idref="V-260505" selected="true" /><select idref="V-260506" selected="true" /><select idref="V-260507" selected="true" /><select idref="V-260508" selected="true" /><select idref="V-260509" selected="true" /><select idref="V-260510" selected="true" /><select idref="V-260511" selected="true" /><select idref="V-260512" selected="true" /><select idref="V-260513" selected="true" /><select idref="V-260514" selected="true" /><select idref="V-260515" selected="true" /><select idref="V-260516" selected="true" /><select idref="V-260517" selected="true" /><select idref="V-260518" selected="true" /><select idref="V-260519" selected="true" /><select idref="V-260520" selected="true" /><select idref="V-260521" selected="true" /><select idref="V-260522" selected="true" /><select idref="V-260523" selected="true" /><select idref="V-260524" selected="true" /><select idref="V-260525" selected="true" /><select idref="V-260526" selected="true" /><select idref="V-260527" selected="true" /><select idref="V-260528" selected="true" /><select idref="V-260529" selected="true" /><select idref="V-260530" selected="true" /><select idref="V-260531" selected="true" /><select idref="V-260532" selected="true" /><select idref="V-260533" selected="true" /><select idref="V-260534" selected="true" /><select idref="V-260535" selected="true" /><select idref="V-260536" selected="true" /><select idref="V-260537" selected="true" /><select idref="V-260538" selected="true" /><select idref="V-260539" selected="true" /><select idref="V-260540" selected="true" /><select idref="V-260541" selected="true" /><select idref="V-260542" selected="true" /><select idref="V-260543" selected="true" /><select idref="V-260545" selected="true" /><select idref="V-260546" selected="true" /><select idref="V-260547" selected="true" /><select idref="V-260548" selected="true" /><select idref="V-260549" selected="true" /><select idref="V-260550" selected="true" /><select idref="V-260552" selected="true" /><select idref="V-260553" selected="true" /><select idref="V-260554" selected="true" /><select idref="V-260555" selected="true" /><select idref="V-260556" selected="true" /><select idref="V-260557" selected="true" /><select idref="V-260558" selected="true" /><select idref="V-260559" selected="true" /><select idref="V-260560" selected="true" /><select idref="V-260561" selected="true" /><select idref="V-260562" selected="true" /><select idref="V-260563" selected="true" /><select idref="V-260564" selected="true" /><select idref="V-260565" selected="true" /><select idref="V-260566" selected="true" /><select idref="V-260567" selected="true" /><select idref="V-260569" selected="true" /><select idref="V-260570" selected="true" /><select idref="V-260571" selected="true" /><select idref="V-260572" selected="true" /><select idref="V-260573" selected="true" /><select idref="V-260574" selected="true" /><select idref="V-260575" selected="true" /><select idref="V-260576" selected="true" /><select idref="V-260577" selected="true" /><select idref="V-260578" selected="true" /><select idref="V-260579" selected="true" /><select idref="V-260580" selected="true" /><select idref="V-260581" selected="true" /><select idref="V-260582" selected="true" /><select idref="V-260583" selected="true" /><select idref="V-260584" selected="true" /><select idref="V-260585" selected="true" /><select idref="V-260586" selected="true" /><select idref="V-260587" selected="true" /><select idref="V-260588" selected="true" /><select idref="V-260589" selected="true" /><select idref="V-260590" selected="true" /><select idref="V-260591" selected="true" /><select idref="V-260592" selected="true" /><select idref="V-260593" selected="true" /><select idref="V-260594" selected="true" /><select idref="V-260595" selected="true" /><select idref="V-260596" selected="true" /><select idref="V-260597" selected="true" /><select idref="V-260598" selected="true" /><select idref="V-260599" selected="true" /><select idref="V-260600" selected="true" /><select idref="V-260601" selected="true" /><select idref="V-260602" selected="true" /><select idref="V-260603" selected="true" /><select idref="V-260604" selected="true" /><select idref="V-260605" selected="true" /><select idref="V-260606" selected="true" /><select idref="V-260607" selected="true" /><select idref="V-260608" selected="true" /><select idref="V-260609" selected="true" /><select idref="V-260610" selected="true" /><select idref="V-260611" selected="true" /><select idref="V-260612" selected="true" /><select idref="V-260613" selected="true" /><select idref="V-260614" selected="true" /><select idref="V-260615" selected="true" /><select idref="V-260616" selected="true" /><select idref="V-260617" selected="true" /><select idref="V-260618" selected="true" /><select idref="V-260619" selected="true" /><select idref="V-260620" selected="true" /><select idref="V-260621" selected="true" /><select idref="V-260622" selected="true" /><select idref="V-260623" selected="true" /><select idref="V-260624" selected="true" /><select idref="V-260625" selected="true" /><select idref="V-260626" selected="true" /><select idref="V-260627" selected="true" /><select idref="V-260628" selected="true" /><select idref="V-260629" selected="true" /><select idref="V-260630" selected="true" /><select idref="V-260631" selected="true" /><select idref="V-260632" selected="true" /><select idref="V-260633" selected="true" /><select idref="V-260634" selected="true" /><select idref="V-260635" selected="true" /><select idref="V-260636" selected="true" /><select idref="V-260637" selected="true" /><select idref="V-260638" selected="true" /><select idref="V-260639" selected="true" /><select idref="V-260640" selected="true" /><select idref="V-260641" selected="true" /><select idref="V-260642" selected="true" /><select idref="V-260643" selected="true" /><select idref="V-260644" selected="true" /><select idref="V-260645" selected="true" /><select idref="V-260646" selected="true" /><select idref="V-260647" selected="true" /><select idref="V-260648" selected="true" /><select idref="V-260649" selected="true" /><select idref="V-260650" selected="true" /></Profile><Profile id="MAC-1_Public"><title>I - Mission Critical Public</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-260469" selected="true" /><select idref="V-260470" selected="true" /><select idref="V-260471" selected="true" /><select idref="V-260472" selected="true" /><select idref="V-260473" selected="true" /><select idref="V-260474" selected="true" /><select idref="V-260475" selected="true" /><select idref="V-260476" selected="true" /><select idref="V-260477" selected="true" /><select idref="V-260478" selected="true" /><select idref="V-260479" selected="true" /><select idref="V-260480" selected="true" /><select idref="V-260481" selected="true" /><select idref="V-260482" selected="true" /><select idref="V-260483" selected="true" /><select idref="V-260484" selected="true" /><select idref="V-260485" selected="true" /><select idref="V-260486" selected="true" /><select idref="V-260487" selected="true" /><select idref="V-260488" selected="true" /><select idref="V-260489" selected="true" /><select idref="V-260490" selected="true" /><select idref="V-260491" selected="true" /><select idref="V-260492" selected="true" /><select idref="V-260493" selected="true" /><select idref="V-260494" selected="true" /><select idref="V-260495" selected="true" /><select idref="V-260496" selected="true" /><select idref="V-260497" selected="true" /><select idref="V-260498" selected="true" /><select idref="V-260499" selected="true" /><select idref="V-260500" selected="true" /><select idref="V-260501" selected="true" /><select idref="V-260502" selected="true" /><select idref="V-260503" selected="true" /><select idref="V-260504" selected="true" /><select idref="V-260505" selected="true" /><select idref="V-260506" selected="true" /><select idref="V-260507" selected="true" /><select idref="V-260508" selected="true" /><select idref="V-260509" selected="true" /><select idref="V-260510" selected="true" /><select idref="V-260511" selected="true" /><select idref="V-260512" selected="true" /><select idref="V-260513" selected="true" /><select idref="V-260514" selected="true" /><select idref="V-260515" selected="true" /><select idref="V-260516" selected="true" /><select idref="V-260517" selected="true" /><select idref="V-260518" selected="true" /><select idref="V-260519" selected="true" /><select idref="V-260520" selected="true" /><select idref="V-260521" selected="true" /><select idref="V-260522" selected="true" /><select idref="V-260523" selected="true" /><select idref="V-260524" selected="true" /><select idref="V-260525" selected="true" /><select idref="V-260526" selected="true" /><select idref="V-260527" selected="true" /><select idref="V-260528" selected="true" /><select idref="V-260529" selected="true" /><select idref="V-260530" selected="true" /><select idref="V-260531" selected="true" /><select idref="V-260532" selected="true" /><select idref="V-260533" selected="true" /><select idref="V-260534" selected="true" /><select idref="V-260535" selected="true" /><select idref="V-260536" selected="true" /><select idref="V-260537" selected="true" /><select idref="V-260538" selected="true" /><select idref="V-260539" selected="true" /><select idref="V-260540" selected="true" /><select idref="V-260541" selected="true" /><select idref="V-260542" selected="true" /><select idref="V-260543" selected="true" /><select idref="V-260545" selected="true" /><select idref="V-260546" selected="true" /><select idref="V-260547" selected="true" /><select idref="V-260548" selected="true" /><select idref="V-260549" selected="true" /><select idref="V-260550" selected="true" /><select idref="V-260552" selected="true" /><select idref="V-260553" selected="true" /><select idref="V-260554" selected="true" /><select idref="V-260555" selected="true" /><select idref="V-260556" selected="true" /><select idref="V-260557" selected="true" /><select idref="V-260558" selected="true" /><select idref="V-260559" selected="true" /><select idref="V-260560" selected="true" /><select idref="V-260561" selected="true" /><select idref="V-260562" selected="true" /><select idref="V-260563" selected="true" /><select idref="V-260564" selected="true" /><select idref="V-260565" selected="true" /><select idref="V-260566" selected="true" /><select idref="V-260567" selected="true" /><select idref="V-260569" selected="true" /><select idref="V-260570" selected="true" /><select idref="V-260571" selected="true" /><select idref="V-260572" selected="true" /><select idref="V-260573" selected="true" /><select idref="V-260574" selected="true" /><select idref="V-260575" selected="true" /><select idref="V-260576" selected="true" /><select idref="V-260577" selected="true" /><select idref="V-260578" selected="true" /><select idref="V-260579" selected="true" /><select idref="V-260580" selected="true" /><select idref="V-260581" selected="true" /><select idref="V-260582" selected="true" /><select idref="V-260583" selected="true" /><select idref="V-260584" selected="true" /><select idref="V-260585" selected="true" /><select idref="V-260586" selected="true" /><select idref="V-260587" selected="true" /><select idref="V-260588" selected="true" /><select idref="V-260589" selected="true" /><select idref="V-260590" selected="true" /><select idref="V-260591" selected="true" /><select idref="V-260592" selected="true" /><select idref="V-260593" selected="true" /><select idref="V-260594" selected="true" /><select idref="V-260595" selected="true" /><select idref="V-260596" selected="true" /><select idref="V-260597" selected="true" /><select idref="V-260598" selected="true" /><select idref="V-260599" selected="true" /><select idref="V-260600" selected="true" /><select idref="V-260601" selected="true" /><select idref="V-260602" selected="true" /><select idref="V-260603" selected="true" /><select idref="V-260604" selected="true" /><select idref="V-260605" selected="true" /><select idref="V-260606" selected="true" /><select idref="V-260607" selected="true" /><select idref="V-260608" selected="true" /><select idref="V-260609" selected="true" /><select idref="V-260610" selected="true" /><select idref="V-260611" selected="true" /><select idref="V-260612" selected="true" /><select idref="V-260613" selected="true" /><select idref="V-260614" selected="true" /><select idref="V-260615" selected="true" /><select idref="V-260616" selected="true" /><select idref="V-260617" selected="true" /><select idref="V-260618" selected="true" /><select idref="V-260619" selected="true" /><select idref="V-260620" selected="true" /><select idref="V-260621" selected="true" /><select idref="V-260622" selected="true" /><select idref="V-260623" selected="true" /><select idref="V-260624" selected="true" /><select idref="V-260625" selected="true" /><select idref="V-260626" selected="true" /><select idref="V-260627" selected="true" /><select idref="V-260628" selected="true" /><select idref="V-260629" selected="true" /><select idref="V-260630" selected="true" /><select idref="V-260631" selected="true" /><select idref="V-260632" selected="true" /><select idref="V-260633" selected="true" /><select idref="V-260634" selected="true" /><select idref="V-260635" selected="true" /><select idref="V-260636" selected="true" /><select idref="V-260637" selected="true" /><select idref="V-260638" selected="true" /><select idref="V-260639" selected="true" /><select idref="V-260640" selected="true" /><select idref="V-260641" selected="true" /><select idref="V-260642" selected="true" /><select idref="V-260643" selected="true" /><select idref="V-260644" selected="true" /><select idref="V-260645" selected="true" /><select idref="V-260646" selected="true" /><select idref="V-260647" selected="true" /><select idref="V-260648" selected="true" /><select idref="V-260649" selected="true" /><select idref="V-260650" selected="true" /></Profile><Profile id="MAC-1_Sensitive"><title>I - Mission Critical Sensitive</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-260469" selected="true" /><select idref="V-260470" selected="true" /><select idref="V-260471" selected="true" /><select idref="V-260472" selected="true" /><select idref="V-260473" selected="true" /><select idref="V-260474" selected="true" /><select idref="V-260475" selected="true" /><select idref="V-260476" selected="true" /><select idref="V-260477" selected="true" /><select idref="V-260478" selected="true" /><select idref="V-260479" selected="true" /><select idref="V-260480" selected="true" /><select idref="V-260481" selected="true" /><select idref="V-260482" selected="true" /><select idref="V-260483" selected="true" /><select idref="V-260484" selected="true" /><select idref="V-260485" selected="true" /><select idref="V-260486" selected="true" /><select idref="V-260487" selected="true" /><select idref="V-260488" selected="true" /><select idref="V-260489" selected="true" /><select idref="V-260490" selected="true" /><select idref="V-260491" selected="true" /><select idref="V-260492" selected="true" /><select idref="V-260493" selected="true" /><select idref="V-260494" selected="true" /><select idref="V-260495" selected="true" /><select idref="V-260496" selected="true" /><select idref="V-260497" selected="true" /><select idref="V-260498" selected="true" /><select idref="V-260499" selected="true" /><select idref="V-260500" selected="true" /><select idref="V-260501" selected="true" /><select idref="V-260502" selected="true" /><select idref="V-260503" selected="true" /><select idref="V-260504" selected="true" /><select idref="V-260505" selected="true" /><select idref="V-260506" selected="true" /><select idref="V-260507" selected="true" /><select idref="V-260508" selected="true" /><select idref="V-260509" selected="true" /><select idref="V-260510" selected="true" /><select idref="V-260511" selected="true" /><select idref="V-260512" selected="true" /><select idref="V-260513" selected="true" /><select idref="V-260514" selected="true" /><select idref="V-260515" selected="true" /><select idref="V-260516" selected="true" /><select idref="V-260517" selected="true" /><select idref="V-260518" selected="true" /><select idref="V-260519" selected="true" /><select idref="V-260520" selected="true" /><select idref="V-260521" selected="true" /><select idref="V-260522" selected="true" /><select idref="V-260523" selected="true" /><select idref="V-260524" selected="true" /><select idref="V-260525" selected="true" /><select idref="V-260526" selected="true" /><select idref="V-260527" selected="true" /><select idref="V-260528" selected="true" /><select idref="V-260529" selected="true" /><select idref="V-260530" selected="true" /><select idref="V-260531" selected="true" /><select idref="V-260532" selected="true" /><select idref="V-260533" selected="true" /><select idref="V-260534" selected="true" /><select idref="V-260535" selected="true" /><select idref="V-260536" selected="true" /><select idref="V-260537" selected="true" /><select idref="V-260538" selected="true" /><select idref="V-260539" selected="true" /><select idref="V-260540" selected="true" /><select idref="V-260541" selected="true" /><select idref="V-260542" selected="true" /><select idref="V-260543" selected="true" /><select idref="V-260545" selected="true" /><select idref="V-260546" selected="true" /><select idref="V-260547" selected="true" /><select idref="V-260548" selected="true" /><select idref="V-260549" selected="true" /><select idref="V-260550" selected="true" /><select idref="V-260552" selected="true" /><select idref="V-260553" selected="true" /><select idref="V-260554" selected="true" /><select idref="V-260555" selected="true" /><select idref="V-260556" selected="true" /><select idref="V-260557" selected="true" /><select idref="V-260558" selected="true" /><select idref="V-260559" selected="true" /><select idref="V-260560" selected="true" /><select idref="V-260561" selected="true" /><select idref="V-260562" selected="true" /><select idref="V-260563" selected="true" /><select idref="V-260564" selected="true" /><select idref="V-260565" selected="true" /><select idref="V-260566" selected="true" /><select idref="V-260567" selected="true" /><select idref="V-260569" selected="true" /><select idref="V-260570" selected="true" /><select idref="V-260571" selected="true" /><select idref="V-260572" selected="true" /><select idref="V-260573" selected="true" /><select idref="V-260574" selected="true" /><select idref="V-260575" selected="true" /><select idref="V-260576" selected="true" /><select idref="V-260577" selected="true" /><select idref="V-260578" selected="true" /><select idref="V-260579" selected="true" /><select idref="V-260580" selected="true" /><select idref="V-260581" selected="true" /><select idref="V-260582" selected="true" /><select idref="V-260583" selected="true" /><select idref="V-260584" selected="true" /><select idref="V-260585" selected="true" /><select idref="V-260586" selected="true" /><select idref="V-260587" selected="true" /><select idref="V-260588" selected="true" /><select idref="V-260589" selected="true" /><select idref="V-260590" selected="true" /><select idref="V-260591" selected="true" /><select idref="V-260592" selected="true" /><select idref="V-260593" selected="true" /><select idref="V-260594" selected="true" /><select idref="V-260595" selected="true" /><select idref="V-260596" selected="true" /><select idref="V-260597" selected="true" /><select idref="V-260598" selected="true" /><select idref="V-260599" selected="true" /><select idref="V-260600" selected="true" /><select idref="V-260601" selected="true" /><select idref="V-260602" selected="true" /><select idref="V-260603" selected="true" /><select idref="V-260604" selected="true" /><select idref="V-260605" selected="true" /><select idref="V-260606" selected="true" /><select idref="V-260607" selected="true" /><select idref="V-260608" selected="true" /><select idref="V-260609" selected="true" /><select idref="V-260610" selected="true" /><select idref="V-260611" selected="true" /><select idref="V-260612" selected="true" /><select idref="V-260613" selected="true" /><select idref="V-260614" selected="true" /><select idref="V-260615" selected="true" /><select idref="V-260616" selected="true" /><select idref="V-260617" selected="true" /><select idref="V-260618" selected="true" /><select idref="V-260619" selected="true" /><select idref="V-260620" selected="true" /><select idref="V-260621" selected="true" /><select idref="V-260622" selected="true" /><select idref="V-260623" selected="true" /><select idref="V-260624" selected="true" /><select idref="V-260625" selected="true" /><select idref="V-260626" selected="true" /><select idref="V-260627" selected="true" /><select idref="V-260628" selected="true" /><select idref="V-260629" selected="true" /><select idref="V-260630" selected="true" /><select idref="V-260631" selected="true" /><select idref="V-260632" selected="true" /><select idref="V-260633" selected="true" /><select idref="V-260634" selected="true" /><select idref="V-260635" selected="true" /><select idref="V-260636" selected="true" /><select idref="V-260637" selected="true" /><select idref="V-260638" selected="true" /><select idref="V-260639" selected="true" /><select idref="V-260640" selected="true" /><select idref="V-260641" selected="true" /><select idref="V-260642" selected="true" /><select idref="V-260643" selected="true" /><select idref="V-260644" selected="true" /><select idref="V-260645" selected="true" /><select idref="V-260646" selected="true" /><select idref="V-260647" selected="true" /><select idref="V-260648" selected="true" /><select idref="V-260649" selected="true" /><select idref="V-260650" selected="true" /></Profile><Profile id="MAC-2_Classified"><title>II - Mission Support Classified</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-260469" selected="true" /><select idref="V-260470" selected="true" /><select idref="V-260471" selected="true" /><select idref="V-260472" selected="true" /><select idref="V-260473" selected="true" /><select idref="V-260474" selected="true" /><select idref="V-260475" selected="true" /><select idref="V-260476" selected="true" /><select idref="V-260477" selected="true" /><select idref="V-260478" selected="true" /><select idref="V-260479" selected="true" /><select idref="V-260480" selected="true" /><select idref="V-260481" selected="true" /><select idref="V-260482" selected="true" /><select idref="V-260483" selected="true" /><select idref="V-260484" selected="true" /><select idref="V-260485" selected="true" /><select idref="V-260486" selected="true" /><select idref="V-260487" selected="true" /><select idref="V-260488" selected="true" /><select idref="V-260489" selected="true" /><select idref="V-260490" selected="true" /><select idref="V-260491" selected="true" /><select idref="V-260492" selected="true" /><select idref="V-260493" selected="true" /><select idref="V-260494" selected="true" /><select idref="V-260495" selected="true" /><select idref="V-260496" selected="true" /><select idref="V-260497" selected="true" /><select idref="V-260498" selected="true" /><select idref="V-260499" selected="true" /><select idref="V-260500" selected="true" /><select idref="V-260501" selected="true" /><select idref="V-260502" selected="true" /><select idref="V-260503" selected="true" /><select idref="V-260504" selected="true" /><select idref="V-260505" selected="true" /><select idref="V-260506" selected="true" /><select idref="V-260507" selected="true" /><select idref="V-260508" selected="true" /><select idref="V-260509" selected="true" /><select idref="V-260510" selected="true" /><select idref="V-260511" selected="true" /><select idref="V-260512" selected="true" /><select idref="V-260513" selected="true" /><select idref="V-260514" selected="true" /><select idref="V-260515" selected="true" /><select idref="V-260516" selected="true" /><select idref="V-260517" selected="true" /><select idref="V-260518" selected="true" /><select idref="V-260519" selected="true" /><select idref="V-260520" selected="true" /><select idref="V-260521" selected="true" /><select idref="V-260522" selected="true" /><select idref="V-260523" selected="true" /><select idref="V-260524" selected="true" /><select idref="V-260525" selected="true" /><select idref="V-260526" selected="true" /><select idref="V-260527" selected="true" /><select idref="V-260528" selected="true" /><select idref="V-260529" selected="true" /><select idref="V-260530" selected="true" /><select idref="V-260531" selected="true" /><select idref="V-260532" selected="true" /><select idref="V-260533" selected="true" /><select idref="V-260534" selected="true" /><select idref="V-260535" selected="true" /><select idref="V-260536" selected="true" /><select idref="V-260537" selected="true" /><select idref="V-260538" selected="true" /><select idref="V-260539" selected="true" /><select idref="V-260540" selected="true" /><select idref="V-260541" selected="true" /><select idref="V-260542" selected="true" /><select idref="V-260543" selected="true" /><select idref="V-260545" selected="true" /><select idref="V-260546" selected="true" /><select idref="V-260547" selected="true" /><select idref="V-260548" selected="true" /><select idref="V-260549" selected="true" /><select idref="V-260550" selected="true" /><select idref="V-260552" selected="true" /><select idref="V-260553" selected="true" /><select idref="V-260554" selected="true" /><select idref="V-260555" selected="true" /><select idref="V-260556" selected="true" /><select idref="V-260557" selected="true" /><select idref="V-260558" selected="true" /><select idref="V-260559" selected="true" /><select idref="V-260560" selected="true" /><select idref="V-260561" selected="true" /><select idref="V-260562" selected="true" /><select idref="V-260563" selected="true" /><select idref="V-260564" selected="true" /><select idref="V-260565" selected="true" /><select idref="V-260566" selected="true" /><select idref="V-260567" selected="true" /><select idref="V-260569" selected="true" /><select idref="V-260570" selected="true" /><select idref="V-260571" selected="true" /><select idref="V-260572" selected="true" /><select idref="V-260573" selected="true" /><select idref="V-260574" selected="true" /><select idref="V-260575" selected="true" /><select idref="V-260576" selected="true" /><select idref="V-260577" selected="true" /><select idref="V-260578" selected="true" /><select idref="V-260579" selected="true" /><select idref="V-260580" selected="true" /><select idref="V-260581" selected="true" /><select idref="V-260582" selected="true" /><select idref="V-260583" selected="true" /><select idref="V-260584" selected="true" /><select idref="V-260585" selected="true" /><select idref="V-260586" selected="true" /><select idref="V-260587" selected="true" /><select idref="V-260588" selected="true" /><select idref="V-260589" selected="true" /><select idref="V-260590" selected="true" /><select idref="V-260591" selected="true" /><select idref="V-260592" selected="true" /><select idref="V-260593" selected="true" /><select idref="V-260594" selected="true" /><select idref="V-260595" selected="true" /><select idref="V-260596" selected="true" /><select idref="V-260597" selected="true" /><select idref="V-260598" selected="true" /><select idref="V-260599" selected="true" /><select idref="V-260600" selected="true" /><select idref="V-260601" selected="true" /><select idref="V-260602" selected="true" /><select idref="V-260603" selected="true" /><select idref="V-260604" selected="true" /><select idref="V-260605" selected="true" /><select idref="V-260606" selected="true" /><select idref="V-260607" selected="true" /><select idref="V-260608" selected="true" /><select idref="V-260609" selected="true" /><select idref="V-260610" selected="true" /><select idref="V-260611" selected="true" /><select idref="V-260612" selected="true" /><select idref="V-260613" selected="true" /><select idref="V-260614" selected="true" /><select idref="V-260615" selected="true" /><select idref="V-260616" selected="true" /><select idref="V-260617" selected="true" /><select idref="V-260618" selected="true" /><select idref="V-260619" selected="true" /><select idref="V-260620" selected="true" /><select idref="V-260621" selected="true" /><select idref="V-260622" selected="true" /><select idref="V-260623" selected="true" /><select idref="V-260624" selected="true" /><select idref="V-260625" selected="true" /><select idref="V-260626" selected="true" /><select idref="V-260627" selected="true" /><select idref="V-260628" selected="true" /><select idref="V-260629" selected="true" /><select idref="V-260630" selected="true" /><select idref="V-260631" selected="true" /><select idref="V-260632" selected="true" /><select idref="V-260633" selected="true" /><select idref="V-260634" selected="true" /><select idref="V-260635" selected="true" /><select idref="V-260636" selected="true" /><select idref="V-260637" selected="true" /><select idref="V-260638" selected="true" /><select idref="V-260639" selected="true" /><select idref="V-260640" selected="true" /><select idref="V-260641" selected="true" /><select idref="V-260642" selected="true" /><select idref="V-260643" selected="true" /><select idref="V-260644" selected="true" /><select idref="V-260645" selected="true" /><select idref="V-260646" selected="true" /><select idref="V-260647" selected="true" /><select idref="V-260648" selected="true" /><select idref="V-260649" selected="true" /><select idref="V-260650" selected="true" /></Profile><Profile id="MAC-2_Public"><title>II - Mission Support Public</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-260469" selected="true" /><select idref="V-260470" selected="true" /><select idref="V-260471" selected="true" /><select idref="V-260472" selected="true" /><select idref="V-260473" selected="true" /><select idref="V-260474" selected="true" /><select idref="V-260475" selected="true" /><select idref="V-260476" selected="true" /><select idref="V-260477" selected="true" /><select idref="V-260478" selected="true" /><select idref="V-260479" selected="true" /><select idref="V-260480" selected="true" /><select idref="V-260481" selected="true" /><select idref="V-260482" selected="true" /><select idref="V-260483" selected="true" /><select idref="V-260484" selected="true" /><select idref="V-260485" selected="true" /><select idref="V-260486" selected="true" /><select idref="V-260487" selected="true" /><select idref="V-260488" selected="true" /><select idref="V-260489" selected="true" /><select idref="V-260490" selected="true" /><select idref="V-260491" selected="true" /><select idref="V-260492" selected="true" /><select idref="V-260493" selected="true" /><select idref="V-260494" selected="true" /><select idref="V-260495" selected="true" /><select idref="V-260496" selected="true" /><select idref="V-260497" selected="true" /><select idref="V-260498" selected="true" /><select idref="V-260499" selected="true" /><select idref="V-260500" selected="true" /><select idref="V-260501" selected="true" /><select idref="V-260502" selected="true" /><select idref="V-260503" selected="true" /><select idref="V-260504" selected="true" /><select idref="V-260505" selected="true" /><select idref="V-260506" selected="true" /><select idref="V-260507" selected="true" /><select idref="V-260508" selected="true" /><select idref="V-260509" selected="true" /><select idref="V-260510" selected="true" /><select idref="V-260511" selected="true" /><select idref="V-260512" selected="true" /><select idref="V-260513" selected="true" /><select idref="V-260514" selected="true" /><select idref="V-260515" selected="true" /><select idref="V-260516" selected="true" /><select idref="V-260517" selected="true" /><select idref="V-260518" selected="true" /><select idref="V-260519" selected="true" /><select idref="V-260520" selected="true" /><select idref="V-260521" selected="true" /><select idref="V-260522" selected="true" /><select idref="V-260523" selected="true" /><select idref="V-260524" selected="true" /><select idref="V-260525" selected="true" /><select idref="V-260526" selected="true" /><select idref="V-260527" selected="true" /><select idref="V-260528" selected="true" /><select idref="V-260529" selected="true" /><select idref="V-260530" selected="true" /><select idref="V-260531" selected="true" /><select idref="V-260532" selected="true" /><select idref="V-260533" selected="true" /><select idref="V-260534" selected="true" /><select idref="V-260535" selected="true" /><select idref="V-260536" selected="true" /><select idref="V-260537" selected="true" /><select idref="V-260538" selected="true" /><select idref="V-260539" selected="true" /><select idref="V-260540" selected="true" /><select idref="V-260541" selected="true" /><select idref="V-260542" selected="true" /><select idref="V-260543" selected="true" /><select idref="V-260545" selected="true" /><select idref="V-260546" selected="true" /><select idref="V-260547" selected="true" /><select idref="V-260548" selected="true" /><select idref="V-260549" selected="true" /><select idref="V-260550" selected="true" /><select idref="V-260552" selected="true" /><select idref="V-260553" selected="true" /><select idref="V-260554" selected="true" /><select idref="V-260555" selected="true" /><select idref="V-260556" selected="true" /><select idref="V-260557" selected="true" /><select idref="V-260558" selected="true" /><select idref="V-260559" selected="true" /><select idref="V-260560" selected="true" /><select idref="V-260561" selected="true" /><select idref="V-260562" selected="true" /><select idref="V-260563" selected="true" /><select idref="V-260564" selected="true" /><select idref="V-260565" selected="true" /><select idref="V-260566" selected="true" /><select idref="V-260567" selected="true" /><select idref="V-260569" selected="true" /><select idref="V-260570" selected="true" /><select idref="V-260571" selected="true" /><select idref="V-260572" selected="true" /><select idref="V-260573" selected="true" /><select idref="V-260574" selected="true" /><select idref="V-260575" selected="true" /><select idref="V-260576" selected="true" /><select idref="V-260577" selected="true" /><select idref="V-260578" selected="true" /><select idref="V-260579" selected="true" /><select idref="V-260580" selected="true" /><select idref="V-260581" selected="true" /><select idref="V-260582" selected="true" /><select idref="V-260583" selected="true" /><select idref="V-260584" selected="true" /><select idref="V-260585" selected="true" /><select idref="V-260586" selected="true" /><select idref="V-260587" selected="true" /><select idref="V-260588" selected="true" /><select idref="V-260589" selected="true" /><select idref="V-260590" selected="true" /><select idref="V-260591" selected="true" /><select idref="V-260592" selected="true" /><select idref="V-260593" selected="true" /><select idref="V-260594" selected="true" /><select idref="V-260595" selected="true" /><select idref="V-260596" selected="true" /><select idref="V-260597" selected="true" /><select idref="V-260598" selected="true" /><select idref="V-260599" selected="true" /><select idref="V-260600" selected="true" /><select idref="V-260601" selected="true" /><select idref="V-260602" selected="true" /><select idref="V-260603" selected="true" /><select idref="V-260604" selected="true" /><select idref="V-260605" selected="true" /><select idref="V-260606" selected="true" /><select idref="V-260607" selected="true" /><select idref="V-260608" selected="true" /><select idref="V-260609" selected="true" /><select idref="V-260610" selected="true" /><select idref="V-260611" selected="true" /><select idref="V-260612" selected="true" /><select idref="V-260613" selected="true" /><select idref="V-260614" selected="true" /><select idref="V-260615" selected="true" /><select idref="V-260616" selected="true" /><select idref="V-260617" selected="true" /><select idref="V-260618" selected="true" /><select idref="V-260619" selected="true" /><select idref="V-260620" selected="true" /><select idref="V-260621" selected="true" /><select idref="V-260622" selected="true" /><select idref="V-260623" selected="true" /><select idref="V-260624" selected="true" /><select idref="V-260625" selected="true" /><select idref="V-260626" selected="true" /><select idref="V-260627" selected="true" /><select idref="V-260628" selected="true" /><select idref="V-260629" selected="true" /><select idref="V-260630" selected="true" /><select idref="V-260631" selected="true" /><select idref="V-260632" selected="true" /><select idref="V-260633" selected="true" /><select idref="V-260634" selected="true" /><select idref="V-260635" selected="true" /><select idref="V-260636" selected="true" /><select idref="V-260637" selected="true" /><select idref="V-260638" selected="true" /><select idref="V-260639" selected="true" /><select idref="V-260640" selected="true" /><select idref="V-260641" selected="true" /><select idref="V-260642" selected="true" /><select idref="V-260643" selected="true" /><select idref="V-260644" selected="true" /><select idref="V-260645" selected="true" /><select idref="V-260646" selected="true" /><select idref="V-260647" selected="true" /><select idref="V-260648" selected="true" /><select idref="V-260649" selected="true" /><select idref="V-260650" selected="true" /></Profile><Profile id="MAC-2_Sensitive"><title>II - Mission Support Sensitive</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-260469" selected="true" /><select idref="V-260470" selected="true" /><select idref="V-260471" selected="true" /><select idref="V-260472" selected="true" /><select idref="V-260473" selected="true" /><select idref="V-260474" selected="true" /><select idref="V-260475" selected="true" /><select idref="V-260476" selected="true" /><select idref="V-260477" selected="true" /><select idref="V-260478" selected="true" /><select idref="V-260479" selected="true" /><select idref="V-260480" selected="true" /><select idref="V-260481" selected="true" /><select idref="V-260482" selected="true" /><select idref="V-260483" selected="true" /><select idref="V-260484" selected="true" /><select idref="V-260485" selected="true" /><select idref="V-260486" selected="true" /><select idref="V-260487" selected="true" /><select idref="V-260488" selected="true" /><select idref="V-260489" selected="true" /><select idref="V-260490" selected="true" /><select idref="V-260491" selected="true" /><select idref="V-260492" selected="true" /><select idref="V-260493" selected="true" /><select idref="V-260494" selected="true" /><select idref="V-260495" selected="true" /><select idref="V-260496" selected="true" /><select idref="V-260497" selected="true" /><select idref="V-260498" selected="true" /><select idref="V-260499" selected="true" /><select idref="V-260500" selected="true" /><select idref="V-260501" selected="true" /><select idref="V-260502" selected="true" /><select idref="V-260503" selected="true" /><select idref="V-260504" selected="true" /><select idref="V-260505" selected="true" /><select idref="V-260506" selected="true" /><select idref="V-260507" selected="true" /><select idref="V-260508" selected="true" /><select idref="V-260509" selected="true" /><select idref="V-260510" selected="true" /><select idref="V-260511" selected="true" /><select idref="V-260512" selected="true" /><select idref="V-260513" selected="true" /><select idref="V-260514" selected="true" /><select idref="V-260515" selected="true" /><select idref="V-260516" selected="true" /><select idref="V-260517" selected="true" /><select idref="V-260518" selected="true" /><select idref="V-260519" selected="true" /><select idref="V-260520" selected="true" /><select idref="V-260521" selected="true" /><select idref="V-260522" selected="true" /><select idref="V-260523" selected="true" /><select idref="V-260524" selected="true" /><select idref="V-260525" selected="true" /><select idref="V-260526" selected="true" /><select idref="V-260527" selected="true" /><select idref="V-260528" selected="true" /><select idref="V-260529" selected="true" /><select idref="V-260530" selected="true" /><select idref="V-260531" selected="true" /><select idref="V-260532" selected="true" /><select idref="V-260533" selected="true" /><select idref="V-260534" selected="true" /><select idref="V-260535" selected="true" /><select idref="V-260536" selected="true" /><select idref="V-260537" selected="true" /><select idref="V-260538" selected="true" /><select idref="V-260539" selected="true" /><select idref="V-260540" selected="true" /><select idref="V-260541" selected="true" /><select idref="V-260542" selected="true" /><select idref="V-260543" selected="true" /><select idref="V-260545" selected="true" /><select idref="V-260546" selected="true" /><select idref="V-260547" selected="true" /><select idref="V-260548" selected="true" /><select idref="V-260549" selected="true" /><select idref="V-260550" selected="true" /><select idref="V-260552" selected="true" /><select idref="V-260553" selected="true" /><select idref="V-260554" selected="true" /><select idref="V-260555" selected="true" /><select idref="V-260556" selected="true" /><select idref="V-260557" selected="true" /><select idref="V-260558" selected="true" /><select idref="V-260559" selected="true" /><select idref="V-260560" selected="true" /><select idref="V-260561" selected="true" /><select idref="V-260562" selected="true" /><select idref="V-260563" selected="true" /><select idref="V-260564" selected="true" /><select idref="V-260565" selected="true" /><select idref="V-260566" selected="true" /><select idref="V-260567" selected="true" /><select idref="V-260569" selected="true" /><select idref="V-260570" selected="true" /><select idref="V-260571" selected="true" /><select idref="V-260572" selected="true" /><select idref="V-260573" selected="true" /><select idref="V-260574" selected="true" /><select idref="V-260575" selected="true" /><select idref="V-260576" selected="true" /><select idref="V-260577" selected="true" /><select idref="V-260578" selected="true" /><select idref="V-260579" selected="true" /><select idref="V-260580" selected="true" /><select idref="V-260581" selected="true" /><select idref="V-260582" selected="true" /><select idref="V-260583" selected="true" /><select idref="V-260584" selected="true" /><select idref="V-260585" selected="true" /><select idref="V-260586" selected="true" /><select idref="V-260587" selected="true" /><select idref="V-260588" selected="true" /><select idref="V-260589" selected="true" /><select idref="V-260590" selected="true" /><select idref="V-260591" selected="true" /><select idref="V-260592" selected="true" /><select idref="V-260593" selected="true" /><select idref="V-260594" selected="true" /><select idref="V-260595" selected="true" /><select idref="V-260596" selected="true" /><select idref="V-260597" selected="true" /><select idref="V-260598" selected="true" /><select idref="V-260599" selected="true" /><select idref="V-260600" selected="true" /><select idref="V-260601" selected="true" /><select idref="V-260602" selected="true" /><select idref="V-260603" selected="true" /><select idref="V-260604" selected="true" /><select idref="V-260605" selected="true" /><select idref="V-260606" selected="true" /><select idref="V-260607" selected="true" /><select idref="V-260608" selected="true" /><select idref="V-260609" selected="true" /><select idref="V-260610" selected="true" /><select idref="V-260611" selected="true" /><select idref="V-260612" selected="true" /><select idref="V-260613" selected="true" /><select idref="V-260614" selected="true" /><select idref="V-260615" selected="true" /><select idref="V-260616" selected="true" /><select idref="V-260617" selected="true" /><select idref="V-260618" selected="true" /><select idref="V-260619" selected="true" /><select idref="V-260620" selected="true" /><select idref="V-260621" selected="true" /><select idref="V-260622" selected="true" /><select idref="V-260623" selected="true" /><select idref="V-260624" selected="true" /><select idref="V-260625" selected="true" /><select idref="V-260626" selected="true" /><select idref="V-260627" selected="true" /><select idref="V-260628" selected="true" /><select idref="V-260629" selected="true" /><select idref="V-260630" selected="true" /><select idref="V-260631" selected="true" /><select idref="V-260632" selected="true" /><select idref="V-260633" selected="true" /><select idref="V-260634" selected="true" /><select idref="V-260635" selected="true" /><select idref="V-260636" selected="true" /><select idref="V-260637" selected="true" /><select idref="V-260638" selected="true" /><select idref="V-260639" selected="true" /><select idref="V-260640" selected="true" /><select idref="V-260641" selected="true" /><select idref="V-260642" selected="true" /><select idref="V-260643" selected="true" /><select idref="V-260644" selected="true" /><select idref="V-260645" selected="true" /><select idref="V-260646" selected="true" /><select idref="V-260647" selected="true" /><select idref="V-260648" selected="true" /><select idref="V-260649" selected="true" /><select idref="V-260650" selected="true" /></Profile><Profile id="MAC-3_Classified"><title>III - Administrative Classified</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-260469" selected="true" /><select idref="V-260470" selected="true" /><select idref="V-260471" selected="true" /><select idref="V-260472" selected="true" /><select idref="V-260473" selected="true" /><select idref="V-260474" selected="true" /><select idref="V-260475" selected="true" /><select idref="V-260476" selected="true" /><select idref="V-260477" selected="true" /><select idref="V-260478" selected="true" /><select idref="V-260479" selected="true" /><select idref="V-260480" selected="true" /><select idref="V-260481" selected="true" /><select idref="V-260482" selected="true" /><select idref="V-260483" selected="true" /><select idref="V-260484" selected="true" /><select idref="V-260485" selected="true" /><select idref="V-260486" selected="true" /><select idref="V-260487" selected="true" /><select idref="V-260488" selected="true" /><select idref="V-260489" selected="true" /><select idref="V-260490" selected="true" /><select idref="V-260491" selected="true" /><select idref="V-260492" selected="true" /><select idref="V-260493" selected="true" /><select idref="V-260494" selected="true" /><select idref="V-260495" selected="true" /><select idref="V-260496" selected="true" /><select idref="V-260497" selected="true" /><select idref="V-260498" selected="true" /><select idref="V-260499" selected="true" /><select idref="V-260500" selected="true" /><select idref="V-260501" selected="true" /><select idref="V-260502" selected="true" /><select idref="V-260503" selected="true" /><select idref="V-260504" selected="true" /><select idref="V-260505" selected="true" /><select idref="V-260506" selected="true" /><select idref="V-260507" selected="true" /><select idref="V-260508" selected="true" /><select idref="V-260509" selected="true" /><select idref="V-260510" selected="true" /><select idref="V-260511" selected="true" /><select idref="V-260512" selected="true" /><select idref="V-260513" selected="true" /><select idref="V-260514" selected="true" /><select idref="V-260515" selected="true" /><select idref="V-260516" selected="true" /><select idref="V-260517" selected="true" /><select idref="V-260518" selected="true" /><select idref="V-260519" selected="true" /><select idref="V-260520" selected="true" /><select idref="V-260521" selected="true" /><select idref="V-260522" selected="true" /><select idref="V-260523" selected="true" /><select idref="V-260524" selected="true" /><select idref="V-260525" selected="true" /><select idref="V-260526" selected="true" /><select idref="V-260527" selected="true" /><select idref="V-260528" selected="true" /><select idref="V-260529" selected="true" /><select idref="V-260530" selected="true" /><select idref="V-260531" selected="true" /><select idref="V-260532" selected="true" /><select idref="V-260533" selected="true" /><select idref="V-260534" selected="true" /><select idref="V-260535" selected="true" /><select idref="V-260536" selected="true" /><select idref="V-260537" selected="true" /><select idref="V-260538" selected="true" /><select idref="V-260539" selected="true" /><select idref="V-260540" selected="true" /><select idref="V-260541" selected="true" /><select idref="V-260542" selected="true" /><select idref="V-260543" selected="true" /><select idref="V-260545" selected="true" /><select idref="V-260546" selected="true" /><select idref="V-260547" selected="true" /><select idref="V-260548" selected="true" /><select idref="V-260549" selected="true" /><select idref="V-260550" selected="true" /><select idref="V-260552" selected="true" /><select idref="V-260553" selected="true" /><select idref="V-260554" selected="true" /><select idref="V-260555" selected="true" /><select idref="V-260556" selected="true" /><select idref="V-260557" selected="true" /><select idref="V-260558" selected="true" /><select idref="V-260559" selected="true" /><select idref="V-260560" selected="true" /><select idref="V-260561" selected="true" /><select idref="V-260562" selected="true" /><select idref="V-260563" selected="true" /><select idref="V-260564" selected="true" /><select idref="V-260565" selected="true" /><select idref="V-260566" selected="true" /><select idref="V-260567" selected="true" /><select idref="V-260569" selected="true" /><select idref="V-260570" selected="true" /><select idref="V-260571" selected="true" /><select idref="V-260572" selected="true" /><select idref="V-260573" selected="true" /><select idref="V-260574" selected="true" /><select idref="V-260575" selected="true" /><select idref="V-260576" selected="true" /><select idref="V-260577" selected="true" /><select idref="V-260578" selected="true" /><select idref="V-260579" selected="true" /><select idref="V-260580" selected="true" /><select idref="V-260581" selected="true" /><select idref="V-260582" selected="true" /><select idref="V-260583" selected="true" /><select idref="V-260584" selected="true" /><select idref="V-260585" selected="true" /><select idref="V-260586" selected="true" /><select idref="V-260587" selected="true" /><select idref="V-260588" selected="true" /><select idref="V-260589" selected="true" /><select idref="V-260590" selected="true" /><select idref="V-260591" selected="true" /><select idref="V-260592" selected="true" /><select idref="V-260593" selected="true" /><select idref="V-260594" selected="true" /><select idref="V-260595" selected="true" /><select idref="V-260596" selected="true" /><select idref="V-260597" selected="true" /><select idref="V-260598" selected="true" /><select idref="V-260599" selected="true" /><select idref="V-260600" selected="true" /><select idref="V-260601" selected="true" /><select idref="V-260602" selected="true" /><select idref="V-260603" selected="true" /><select idref="V-260604" selected="true" /><select idref="V-260605" selected="true" /><select idref="V-260606" selected="true" /><select idref="V-260607" selected="true" /><select idref="V-260608" selected="true" /><select idref="V-260609" selected="true" /><select idref="V-260610" selected="true" /><select idref="V-260611" selected="true" /><select idref="V-260612" selected="true" /><select idref="V-260613" selected="true" /><select idref="V-260614" selected="true" /><select idref="V-260615" selected="true" /><select idref="V-260616" selected="true" /><select idref="V-260617" selected="true" /><select idref="V-260618" selected="true" /><select idref="V-260619" selected="true" /><select idref="V-260620" selected="true" /><select idref="V-260621" selected="true" /><select idref="V-260622" selected="true" /><select idref="V-260623" selected="true" /><select idref="V-260624" selected="true" /><select idref="V-260625" selected="true" /><select idref="V-260626" selected="true" /><select idref="V-260627" selected="true" /><select idref="V-260628" selected="true" /><select idref="V-260629" selected="true" /><select idref="V-260630" selected="true" /><select idref="V-260631" selected="true" /><select idref="V-260632" selected="true" /><select idref="V-260633" selected="true" /><select idref="V-260634" selected="true" /><select idref="V-260635" selected="true" /><select idref="V-260636" selected="true" /><select idref="V-260637" selected="true" /><select idref="V-260638" selected="true" /><select idref="V-260639" selected="true" /><select idref="V-260640" selected="true" /><select idref="V-260641" selected="true" /><select idref="V-260642" selected="true" /><select idref="V-260643" selected="true" /><select idref="V-260644" selected="true" /><select idref="V-260645" selected="true" /><select idref="V-260646" selected="true" /><select idref="V-260647" selected="true" /><select idref="V-260648" selected="true" /><select idref="V-260649" selected="true" /><select idref="V-260650" selected="true" /></Profile><Profile id="MAC-3_Public"><title>III - Administrative Public</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-260469" selected="true" /><select idref="V-260470" selected="true" /><select idref="V-260471" selected="true" /><select idref="V-260472" selected="true" /><select idref="V-260473" selected="true" /><select idref="V-260474" selected="true" /><select idref="V-260475" selected="true" /><select idref="V-260476" selected="true" /><select idref="V-260477" selected="true" /><select idref="V-260478" selected="true" /><select idref="V-260479" selected="true" /><select idref="V-260480" selected="true" /><select idref="V-260481" selected="true" /><select idref="V-260482" selected="true" /><select idref="V-260483" selected="true" /><select idref="V-260484" selected="true" /><select idref="V-260485" selected="true" /><select idref="V-260486" selected="true" /><select idref="V-260487" selected="true" /><select idref="V-260488" selected="true" /><select idref="V-260489" selected="true" /><select idref="V-260490" selected="true" /><select idref="V-260491" selected="true" /><select idref="V-260492" selected="true" /><select idref="V-260493" selected="true" /><select idref="V-260494" selected="true" /><select idref="V-260495" selected="true" /><select idref="V-260496" selected="true" /><select idref="V-260497" selected="true" /><select idref="V-260498" selected="true" /><select idref="V-260499" selected="true" /><select idref="V-260500" selected="true" /><select idref="V-260501" selected="true" /><select idref="V-260502" selected="true" /><select idref="V-260503" selected="true" /><select idref="V-260504" selected="true" /><select idref="V-260505" selected="true" /><select idref="V-260506" selected="true" /><select idref="V-260507" selected="true" /><select idref="V-260508" selected="true" /><select idref="V-260509" selected="true" /><select idref="V-260510" selected="true" /><select idref="V-260511" selected="true" /><select idref="V-260512" selected="true" /><select idref="V-260513" selected="true" /><select idref="V-260514" selected="true" /><select idref="V-260515" selected="true" /><select idref="V-260516" selected="true" /><select idref="V-260517" selected="true" /><select idref="V-260518" selected="true" /><select idref="V-260519" selected="true" /><select idref="V-260520" selected="true" /><select idref="V-260521" selected="true" /><select idref="V-260522" selected="true" /><select idref="V-260523" selected="true" /><select idref="V-260524" selected="true" /><select idref="V-260525" selected="true" /><select idref="V-260526" selected="true" /><select idref="V-260527" selected="true" /><select idref="V-260528" selected="true" /><select idref="V-260529" selected="true" /><select idref="V-260530" selected="true" /><select idref="V-260531" selected="true" /><select idref="V-260532" selected="true" /><select idref="V-260533" selected="true" /><select idref="V-260534" selected="true" /><select idref="V-260535" selected="true" /><select idref="V-260536" selected="true" /><select idref="V-260537" selected="true" /><select idref="V-260538" selected="true" /><select idref="V-260539" selected="true" /><select idref="V-260540" selected="true" /><select idref="V-260541" selected="true" /><select idref="V-260542" selected="true" /><select idref="V-260543" selected="true" /><select idref="V-260545" selected="true" /><select idref="V-260546" selected="true" /><select idref="V-260547" selected="true" /><select idref="V-260548" selected="true" /><select idref="V-260549" selected="true" /><select idref="V-260550" selected="true" /><select idref="V-260552" selected="true" /><select idref="V-260553" selected="true" /><select idref="V-260554" selected="true" /><select idref="V-260555" selected="true" /><select idref="V-260556" selected="true" /><select idref="V-260557" selected="true" /><select idref="V-260558" selected="true" /><select idref="V-260559" selected="true" /><select idref="V-260560" selected="true" /><select idref="V-260561" selected="true" /><select idref="V-260562" selected="true" /><select idref="V-260563" selected="true" /><select idref="V-260564" selected="true" /><select idref="V-260565" selected="true" /><select idref="V-260566" selected="true" /><select idref="V-260567" selected="true" /><select idref="V-260569" selected="true" /><select idref="V-260570" selected="true" /><select idref="V-260571" selected="true" /><select idref="V-260572" selected="true" /><select idref="V-260573" selected="true" /><select idref="V-260574" selected="true" /><select idref="V-260575" selected="true" /><select idref="V-260576" selected="true" /><select idref="V-260577" selected="true" /><select idref="V-260578" selected="true" /><select idref="V-260579" selected="true" /><select idref="V-260580" selected="true" /><select idref="V-260581" selected="true" /><select idref="V-260582" selected="true" /><select idref="V-260583" selected="true" /><select idref="V-260584" selected="true" /><select idref="V-260585" selected="true" /><select idref="V-260586" selected="true" /><select idref="V-260587" selected="true" /><select idref="V-260588" selected="true" /><select idref="V-260589" selected="true" /><select idref="V-260590" selected="true" /><select idref="V-260591" selected="true" /><select idref="V-260592" selected="true" /><select idref="V-260593" selected="true" /><select idref="V-260594" selected="true" /><select idref="V-260595" selected="true" /><select idref="V-260596" selected="true" /><select idref="V-260597" selected="true" /><select idref="V-260598" selected="true" /><select idref="V-260599" selected="true" /><select idref="V-260600" selected="true" /><select idref="V-260601" selected="true" /><select idref="V-260602" selected="true" /><select idref="V-260603" selected="true" /><select idref="V-260604" selected="true" /><select idref="V-260605" selected="true" /><select idref="V-260606" selected="true" /><select idref="V-260607" selected="true" /><select idref="V-260608" selected="true" /><select idref="V-260609" selected="true" /><select idref="V-260610" selected="true" /><select idref="V-260611" selected="true" /><select idref="V-260612" selected="true" /><select idref="V-260613" selected="true" /><select idref="V-260614" selected="true" /><select idref="V-260615" selected="true" /><select idref="V-260616" selected="true" /><select idref="V-260617" selected="true" /><select idref="V-260618" selected="true" /><select idref="V-260619" selected="true" /><select idref="V-260620" selected="true" /><select idref="V-260621" selected="true" /><select idref="V-260622" selected="true" /><select idref="V-260623" selected="true" /><select idref="V-260624" selected="true" /><select idref="V-260625" selected="true" /><select idref="V-260626" selected="true" /><select idref="V-260627" selected="true" /><select idref="V-260628" selected="true" /><select idref="V-260629" selected="true" /><select idref="V-260630" selected="true" /><select idref="V-260631" selected="true" /><select idref="V-260632" selected="true" /><select idref="V-260633" selected="true" /><select idref="V-260634" selected="true" /><select idref="V-260635" selected="true" /><select idref="V-260636" selected="true" /><select idref="V-260637" selected="true" /><select idref="V-260638" selected="true" /><select idref="V-260639" selected="true" /><select idref="V-260640" selected="true" /><select idref="V-260641" selected="true" /><select idref="V-260642" selected="true" /><select idref="V-260643" selected="true" /><select idref="V-260644" selected="true" /><select idref="V-260645" selected="true" /><select idref="V-260646" selected="true" /><select idref="V-260647" selected="true" /><select idref="V-260648" selected="true" /><select idref="V-260649" selected="true" /><select idref="V-260650" selected="true" /></Profile><Profile id="MAC-3_Sensitive"><title>III - Administrative Sensitive</title><description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description><select idref="V-260469" selected="true" /><select idref="V-260470" selected="true" /><select idref="V-260471" selected="true" /><select idref="V-260472" selected="true" /><select idref="V-260473" selected="true" /><select idref="V-260474" selected="true" /><select idref="V-260475" selected="true" /><select idref="V-260476" selected="true" /><select idref="V-260477" selected="true" /><select idref="V-260478" selected="true" /><select idref="V-260479" selected="true" /><select idref="V-260480" selected="true" /><select idref="V-260481" selected="true" /><select idref="V-260482" selected="true" /><select idref="V-260483" selected="true" /><select idref="V-260484" selected="true" /><select idref="V-260485" selected="true" /><select idref="V-260486" selected="true" /><select idref="V-260487" selected="true" /><select idref="V-260488" selected="true" /><select idref="V-260489" selected="true" /><select idref="V-260490" selected="true" /><select idref="V-260491" selected="true" /><select idref="V-260492" selected="true" /><select idref="V-260493" selected="true" /><select idref="V-260494" selected="true" /><select idref="V-260495" selected="true" /><select idref="V-260496" selected="true" /><select idref="V-260497" selected="true" /><select idref="V-260498" selected="true" /><select idref="V-260499" selected="true" /><select idref="V-260500" selected="true" /><select idref="V-260501" selected="true" /><select idref="V-260502" selected="true" /><select idref="V-260503" selected="true" /><select idref="V-260504" selected="true" /><select idref="V-260505" selected="true" /><select idref="V-260506" selected="true" /><select idref="V-260507" selected="true" /><select idref="V-260508" selected="true" /><select idref="V-260509" selected="true" /><select idref="V-260510" selected="true" /><select idref="V-260511" selected="true" /><select idref="V-260512" selected="true" /><select idref="V-260513" selected="true" /><select idref="V-260514" selected="true" /><select idref="V-260515" selected="true" /><select idref="V-260516" selected="true" /><select idref="V-260517" selected="true" /><select idref="V-260518" selected="true" /><select idref="V-260519" selected="true" /><select idref="V-260520" selected="true" /><select idref="V-260521" selected="true" /><select idref="V-260522" selected="true" /><select idref="V-260523" selected="true" /><select idref="V-260524" selected="true" /><select idref="V-260525" selected="true" /><select idref="V-260526" selected="true" /><select idref="V-260527" selected="true" /><select idref="V-260528" selected="true" /><select idref="V-260529" selected="true" /><select idref="V-260530" selected="true" /><select idref="V-260531" selected="true" /><select idref="V-260532" selected="true" /><select idref="V-260533" selected="true" /><select idref="V-260534" selected="true" /><select idref="V-260535" selected="true" /><select idref="V-260536" selected="true" /><select idref="V-260537" selected="true" /><select idref="V-260538" selected="true" /><select idref="V-260539" selected="true" /><select idref="V-260540" selected="true" /><select idref="V-260541" selected="true" /><select idref="V-260542" selected="true" /><select idref="V-260543" selected="true" /><select idref="V-260545" selected="true" /><select idref="V-260546" selected="true" /><select idref="V-260547" selected="true" /><select idref="V-260548" selected="true" /><select idref="V-260549" selected="true" /><select idref="V-260550" selected="true" /><select idref="V-260552" selected="true" /><select idref="V-260553" selected="true" /><select idref="V-260554" selected="true" /><select idref="V-260555" selected="true" /><select idref="V-260556" selected="true" /><select idref="V-260557" selected="true" /><select idref="V-260558" selected="true" /><select idref="V-260559" selected="true" /><select idref="V-260560" selected="true" /><select idref="V-260561" selected="true" /><select idref="V-260562" selected="true" /><select idref="V-260563" selected="true" /><select idref="V-260564" selected="true" /><select idref="V-260565" selected="true" /><select idref="V-260566" selected="true" /><select idref="V-260567" selected="true" /><select idref="V-260569" selected="true" /><select idref="V-260570" selected="true" /><select idref="V-260571" selected="true" /><select idref="V-260572" selected="true" /><select idref="V-260573" selected="true" /><select idref="V-260574" selected="true" /><select idref="V-260575" selected="true" /><select idref="V-260576" selected="true" /><select idref="V-260577" selected="true" /><select idref="V-260578" selected="true" /><select idref="V-260579" selected="true" /><select idref="V-260580" selected="true" /><select idref="V-260581" selected="true" /><select idref="V-260582" selected="true" /><select idref="V-260583" selected="true" /><select idref="V-260584" selected="true" /><select idref="V-260585" selected="true" /><select idref="V-260586" selected="true" /><select idref="V-260587" selected="true" /><select idref="V-260588" selected="true" /><select idref="V-260589" selected="true" /><select idref="V-260590" selected="true" /><select idref="V-260591" selected="true" /><select idref="V-260592" selected="true" /><select idref="V-260593" selected="true" /><select idref="V-260594" selected="true" /><select idref="V-260595" selected="true" /><select idref="V-260596" selected="true" /><select idref="V-260597" selected="true" /><select idref="V-260598" selected="true" /><select idref="V-260599" selected="true" /><select idref="V-260600" selected="true" /><select idref="V-260601" selected="true" /><select idref="V-260602" selected="true" /><select idref="V-260603" selected="true" /><select idref="V-260604" selected="true" /><select idref="V-260605" selected="true" /><select idref="V-260606" selected="true" /><select idref="V-260607" selected="true" /><select idref="V-260608" selected="true" /><select idref="V-260609" selected="true" /><select idref="V-260610" selected="true" /><select idref="V-260611" selected="true" /><select idref="V-260612" selected="true" /><select idref="V-260613" selected="true" /><select idref="V-260614" selected="true" /><select idref="V-260615" selected="true" /><select idref="V-260616" selected="true" /><select idref="V-260617" selected="true" /><select idref="V-260618" selected="true" /><select idref="V-260619" selected="true" /><select idref="V-260620" selected="true" /><select idref="V-260621" selected="true" /><select idref="V-260622" selected="true" /><select idref="V-260623" selected="true" /><select idref="V-260624" selected="true" /><select idref="V-260625" selected="true" /><select idref="V-260626" selected="true" /><select idref="V-260627" selected="true" /><select idref="V-260628" selected="true" /><select idref="V-260629" selected="true" /><select idref="V-260630" selected="true" /><select idref="V-260631" selected="true" /><select idref="V-260632" selected="true" /><select idref="V-260633" selected="true" /><select idref="V-260634" selected="true" /><select idref="V-260635" selected="true" /><select idref="V-260636" selected="true" /><select idref="V-260637" selected="true" /><select idref="V-260638" selected="true" /><select idref="V-260639" selected="true" /><select idref="V-260640" selected="true" /><select idref="V-260641" selected="true" /><select idref="V-260642" selected="true" /><select idref="V-260643" selected="true" /><select idref="V-260644" selected="true" /><select idref="V-260645" selected="true" /><select idref="V-260646" selected="true" /><select idref="V-260647" selected="true" /><select idref="V-260648" selected="true" /><select idref="V-260649" selected="true" /><select idref="V-260650" selected="true" /></Profile><Group id="V-260469"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260469r991589_rule" weight="10.0" severity="high"><version>UBTU-22-211015</version><title>Ubuntu 22.04 LTS must disable the x86 Ctrl-Alt-Delete key sequence.</title><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.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64106r953219_fix">Configure Ubuntu 22.04 LTS to disable the Ctrl-Alt-Delete sequence for the command line by using the following commands: 
 
     $ sudo systemctl disable ctrl-alt-del.target 
 
     $ sudo systemctl mask ctrl-alt-del.target 
 
Reload the daemon to take effect:  
 
     $ sudo systemctl daemon-reload</fixtext><fix id="F-64106r953219_fix" /><check system="C-64198r953218_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS is not configured to reboot the system when Ctrl-Alt-Delete is pressed by using the following command: 
 
     $ systemctl status ctrl-alt-del.target 
     ctrl-alt-del.target 
          Loaded: masked (Reason: Unit ctrl-alt-del.target is masked.) 
          Active: inactive (dead) 
 
If the "ctrl-alt-del.target" is not masked, this is a finding.</check-content></check></Rule></Group><Group id="V-260470"><title>SRG-OS-000080-GPOS-00048</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260470r958472_rule" weight="10.0" severity="high"><version>UBTU-22-212010</version><title>Ubuntu 22.04 LTS, when booted, must require authentication upon booting into single-user and maintenance modes.</title><description>&lt;VulnDiscussion&gt;To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access.   
  
Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.  
  
Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000213</ident><fixtext fixref="F-64107r953222_fix">Configure Ubuntu 22.04 LTS to require a password for authentication upon booting into single-user and maintenance modes.  
  
Generate an encrypted (grub) password for root by using the following command:  
  
     $ grub-mkpasswd-pbkdf2  
     Enter Password:  
     Reenter Password: 
     PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.03255F190F0E2F7B4F0D1C3216012309162F022A7A636771 
  
Using the hash from the output, modify the "/etc/grub.d/40_custom" file by using the following command to add a boot password:  
  
     $ sudo sed -i '$i set superusers=\"root\"\npassword_pbkdf2 root &lt;hash&gt;' /etc/grub.d/40_custom  
  
where &lt;hash&gt; is the hash generated by grub-mkpasswd-pbkdf2 command.  
  
Generate an updated "grub.conf" file with the new password by using the following command:  
  
     $ sudo update-grub</fixtext><fix id="F-64107r953222_fix" /><check system="C-64199r953221_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS requires a password for authentication upon booting into single-user and maintenance modes by using the following command:  
  
     $ sudo grep -i password /boot/grub/grub.cfg  
  
     password_pbkdf2 root grub.pbkdf2.sha512.10000.03255F190F0E2F7B4F0D1C3216012309162F022A7A636771 
  
If the root password entry does not begin with "password_pbkdf2", this is a finding.</check-content></check></Rule></Group><Group id="V-260471"><title>SRG-OS-000254-GPOS-00095</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260471r991555_rule" weight="10.0" severity="medium"><version>UBTU-22-212015</version><title>Ubuntu 22.04 LTS must initiate session audits at system startup.</title><description>&lt;VulnDiscussion&gt;If auditing is enabled late in the startup process, the actions of some startup processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001464</ident><fixtext fixref="F-64108r953225_fix">Configure Ubuntu 22.04 LTS to produce audit records at system startup.   
  
Edit the "/etc/default/grub" file and add "audit=1" to the "GRUB_CMDLINE_LINUX" option.  
  
To update the grub config file, run:  
  
     $ sudo update-grub</fixtext><fix id="F-64108r953225_fix" /><check system="C-64200r953224_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that Ubuntu 22.04 LTS enables auditing at system startup in grub by using the following command:
  
     $ grep "^\s*linux" /boot/grub/grub.cfg 
 
     linux   /vmlinuz-5.15.0-89-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro audit=1 
          linux   /vmlinuz-5.15.0-89-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro audit=1 
          linux   /vmlinuz-5.15.0-89-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro single nomodeset dis_ucode_ldr audit=1 
          linux   /vmlinuz-5.15.0-83-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro audit=1 
          linux   /vmlinuz-5.15.0-83-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro single nomodeset dis_ucode_ldr audit=1 
 
If any linux lines do not contain "audit=1", this is a finding.</check-content></check></Rule></Group><Group id="V-260472"><title>SRG-OS-000138-GPOS-00069</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260472r958524_rule" weight="10.0" severity="low"><version>UBTU-22-213010</version><title>Ubuntu 22.04 LTS must restrict access to the kernel message buffer.</title><description>&lt;VulnDiscussion&gt;Restricting access to the kernel message buffer limits access only to root. This prevents attackers from gaining additional system information as a nonprivileged user.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001090</ident><fixtext fixref="F-64109r953228_fix">Configure Ubuntu 22.04 LTS to restrict access to the kernel message buffer. 
 
Add or modify the following line in the "/etc/sysctl.conf" file: 
 
kernel.dmesg_restrict = 1 
 
Remove any configurations that conflict with the above from the following locations:  
 
/run/sysctl.d/ 
/etc/sysctl.d/ 
/usr/local/lib/sysctl.d/ 
/usr/lib/sysctl.d/ 
/lib/sysctl.d/ 
/etc/sysctl.conf 
 
Reload settings from all system configuration files by using the following command: 
 
     $ sudo sysctl --system</fixtext><fix id="F-64109r953228_fix" /><check system="C-64201r953227_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS is configured to restrict access to the kernel message buffer by using the following command: 
 
     $ sysctl kernel.dmesg_restrict 
     kernel.dmesg_restrict = 1 
 
If "kernel.dmesg_restrict" is not set to "1" or is missing, this is a finding. 
 
Verify that there are no configurations that enable the kernel dmesg function: 
 
     $ sudo grep -ir kernel.dmesg_restrict /run/sysctl.d/* /etc/sysctl.d/* /usr/local/lib/sysctl.d/* /usr/lib/sysctl.d/* /lib/sysctl.d/* /etc/sysctl.conf 2&gt; /dev/null 
     /etc/sysctl.d/10-kernel-hardening.conf:kernel.dmesg_restrict = 1 
 
If "kernel.dmesg_restrict" is not set to "1", is commented out, is missing, or conflicting results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260473"><title>SRG-OS-000184-GPOS-00078</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260473r1044782_rule" weight="10.0" severity="medium"><version>UBTU-22-213015</version><title>Ubuntu 22.04 LTS must disable kernel core dumps so that it can fail to a secure state if system initialization fails, shutdown fails or aborts fail.</title><description>&lt;VulnDiscussion&gt;Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps may consume a considerable amount of disk space and may result in denial of service by exhausting the available space on the target file system partition.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001190</ident><fixtext fixref="F-64110r1044781_fix">If kernel core dumps are not required, disable and mask "kdump-tools.service" by using the following command:

$ sudo systemctl mask kdump-tools --now

If kernel core dumps are required, document the need with the ISSO.</fixtext><fix id="F-64110r1044781_fix" /><check system="C-64202r1044780_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that kernel core dumps are disabled unless needed by using the following command:

$ systemctl status kdump-tools.service
kdump-tools.service
Loaded: masked (Reason: Unit kdump-tools.service is masked.)
Active: inactive (dead)

If "kdump-tools.service" is not masked and inactive, ask the system administrator (SA) if the use of the service is required and documented with the information system security officer (ISSO).

If the service is active and is not documented, this is a finding.</check-content></check></Rule></Group><Group id="V-260474"><title>SRG-OS-000433-GPOS-00193</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260474r958928_rule" weight="10.0" severity="medium"><version>UBTU-22-213020</version><title>Ubuntu 22.04 LTS must implement address space layout randomization to protect its memory from unauthorized code execution.</title><description>&lt;VulnDiscussion&gt;Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in prohibited memory locations. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism.  
  
Examples of attacks are buffer overflow attacks.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002824</ident><fixtext fixref="F-64111r953234_fix">Remove the "kernel.randomize_va_space" entry found in the "/etc/sysctl.conf" file or any file located in the "/etc/sysctl.d/" directory.  
 
Reload the system configuration files for the changes to take effect by using the following command: 
 
     $ sudo sysctl --system</fixtext><fix id="F-64111r953234_fix" /><check system="C-64203r953233_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS implements address space layout randomization (ASLR) by using the following command:  
  
     $ sysctl kernel.randomize_va_space 
     kernel.randomize_va_space = 2 
  
If no output is returned, verify the kernel parameter "randomize_va_space" is set to "2" by using the following command:  
  
     $ cat /proc/sys/kernel/randomize_va_space 
     2 
  
If "kernel.randomize_va_space" is not set to "2", this is a finding.  
  
Verify that a saved value of the "kernel.randomize_va_space" variable is not defined.  
  
     $ sudo grep -ER "^kernel.randomize_va_space=[^2]" /etc/sysctl.conf /etc/sysctl.d 
  
If this returns a result, this is a finding.</check-content></check></Rule></Group><Group id="V-260475"><title>SRG-OS-000433-GPOS-00192</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260475r958928_rule" weight="10.0" severity="medium"><version>UBTU-22-213025</version><title>Ubuntu 22.04 LTS must implement nonexecutable data to protect its memory from unauthorized code execution.</title><description>&lt;VulnDiscussion&gt;Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism.  
  
Examples of attacks are buffer overflow attacks.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002824</ident><fixtext fixref="F-64112r953237_fix">Configure Ubuntu 22.04 LTS to enable NX.  
  
If the installed CPU is hardware capable of NX protection, check if the system's BIOS/UEFI setup configuration permits toggling the "NX bit" or "no execution bit", and set it to "enabled".</fixtext><fix id="F-64112r953237_fix" /><check system="C-64204r953236_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the NX (no-execution) bit flag is set on the system by using the following command:  
 
     $ sudo dmesg | grep -i "execute disable" 
     [    0.000000] NX (Execute Disable) protection: active  
 
If "dmesg" does not show "NX (Execute Disable) protection: active", check the hardware capabilities of the installed CPU by using the following command:   
  
     $ grep flags /proc/cpuinfo | grep -o nx | sort -u 
     nx  
  
If no output is returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260476"><title>SRG-OS-000366-GPOS-00153</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260476r1015003_rule" weight="10.0" severity="low"><version>UBTU-22-214010</version><title>Ubuntu 22.04 LTS must be configured so that the Advance Package Tool (APT) prevents the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization.</title><description>&lt;VulnDiscussion&gt;Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor.
  
Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization.
  
Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DOD certificates for this purpose; however, the certificate used to verify the software must be from an approved certificate authority (CA).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-003992</ident><ident system="http://cyber.mil/cci">CCI-001749</ident><fixtext fixref="F-64113r953240_fix">Configure APT to prevent the installation of patches, service packs, device drivers, or Ubuntu operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization.  
  
Add or modify the following line in any file under the "/etc/apt/apt.conf.d/" directory: 
 
APT::Get::AllowUnauthenticated "false";</fixtext><fix id="F-64113r953240_fix" /><check system="C-64205r953239_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that APT is configured to prevent the installation of patches, service packs, device drivers, or Ubuntu operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization by using the following command:  
  
     $ grep -i allowunauthenticated /etc/apt/apt.conf.d/* 
     /etc/apt/apt.conf.d/01-vendor-ubuntu:APT::Get::AllowUnauthenticated "false"; 
  
If "APT::Get::AllowUnauthenticated" is not set to "false", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260477"><title>SRG-OS-000437-GPOS-00194</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260477r1044773_rule" weight="10.0" severity="medium"><version>UBTU-22-214015</version><title>Ubuntu 22.04 LTS must be configured so that the Advance Package Tool (APT) removes all software components after updated versions have been installed.</title><description>&lt;VulnDiscussion&gt;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.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002617</ident><fixtext fixref="F-64114r1044772_fix">Configure APT to remove all software components after updated versions have been installed.  
  
Add or modify the following lines in the "/etc/apt/apt.conf.d/50unattended-upgrades" file:  
 
Unattended-Upgrade::Remove-Unused-Kernel-Packages "true"; 
Unattended-Upgrade::Remove-Unused-Dependencies "true";</fixtext><fix id="F-64114r1044772_fix" /><check system="C-64206r1044771_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify APT is configured to remove all software components after updated versions have been installed by using the following command:  
  
     $ grep -i remove-unused /etc/apt/apt.conf.d/50unattended-upgrades 
     Unattended-Upgrade::Remove-Unused-Kernel-Packages "true"; 
     Unattended-Upgrade::Remove-Unused-Dependencies "true"; 
  
If "Unattended-Upgrade::Remove-Unused-Kernel-Packages" and "Unattended-Upgrade::Remove-Unused-Dependencies" are not set to "true", are commented out, or are missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260478"><title>SRG-OS-000480-GPOS-00225</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260478r991587_rule" weight="10.0" severity="medium"><version>UBTU-22-215010</version><title>Ubuntu 22.04 LTS must have the "libpam-pwquality" package installed.</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.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64115r953246_fix">Install the "pam_pwquality" package by using the following command: 
  
     $ sudo apt-get install libpam-pwquality</fixtext><fix id="F-64115r953246_fix" /><check system="C-64207r953245_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS has the "libpam-pwquality" package installed with  the following command:  
  
     $ dpkg -l | grep libpam-pwquality 
     ii     libpam-pwquality:amd64     1.4.4-1build2     amd64     PAM module to check password strength 
  
If "libpam-pwquality" is not installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260479"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260479r991589_rule" weight="10.0" severity="low"><version>UBTU-22-215015</version><title>Ubuntu 22.04 LTS must have the "chrony" package installed.</title><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.  

Organizations must consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64116r953249_fix">Install the "chrony" network time protocol package using the following command: 
 
     $ sudo apt-get install chrony</fixtext><fix id="F-64116r953249_fix" /><check system="C-64208r953248_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the "chrony" package is installed using the following command: 
  
     $ dpkg -l | grep chrony 
     ii     chrony     4.2-2ubuntu2     amd64     Versatile implementation of the Network Time Protocol 
 
If the "chrony" package is not installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260480"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260480r991589_rule" weight="10.0" severity="low"><version>UBTU-22-215020</version><title>Ubuntu 22.04 LTS must not have the "systemd-timesyncd" package installed.</title><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.

Organizations must consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64117r953252_fix">The "systemd-timesyncd" package will be uninstalled as part of the "chrony" package install. The remaining configuration files for "systemd-timesyncd" must be purged from the operating system: 
 
     $ sudo dpkg -P --force-all systemd-timesyncd</fixtext><fix id="F-64117r953252_fix" /><check system="C-64209r953251_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the "systemd-timesyncd" package is not installed by using the following command: 
 
     $ dpkg -l | grep systemd-timesyncd 
 
If the "systemd-timesyncd" package is installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260481"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260481r991589_rule" weight="10.0" severity="low"><version>UBTU-22-215025</version><title>Ubuntu 22.04 LTS must not have the "ntp" package installed.</title><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.  

Organizations must consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64118r953255_fix">Uninstall the "ntp" package by using the following command: 
 
     $ sudo dpkg -P --force-all ntp</fixtext><fix id="F-64118r953255_fix" /><check system="C-64210r953254_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the "ntp" package is not installed by using the following command: 
 
     $ dpkg -l | grep ntp 
 
If the "ntp" package is installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260482"><title>SRG-OS-000095-GPOS-00049</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260482r958478_rule" weight="10.0" severity="high"><version>UBTU-22-215030</version><title>Ubuntu 22.04 LTS must not have the "rsh-server" package installed.</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.  
  
Remote Shell (RSH) is a client/server application protocol that provides an unencrypted remote access service, which does not provide for the confidentiality and integrity of user passwords or the remote session. If users were allowed to login to a system using RSH, the privileged user passwords and communications could be compromised. 
 
Removing the "rsh-server" package decreases the risk of accidental or intentional activation of the RSH 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000381</ident><fixtext fixref="F-64119r953258_fix">Remove the "rsh-server" package by using the following command:  
 
     $ sudo apt-get remove rsh-server</fixtext><fix id="F-64119r953258_fix" /><check system="C-64211r953257_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the "rsh-server" package is not installed by using the following command:  
  
     $ dpkg -l | grep rsh-server 
  
If the "rsh-server" package is installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260483"><title>SRG-OS-000074-GPOS-00042</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260483r987796_rule" weight="10.0" severity="high"><version>UBTU-22-215035</version><title>Ubuntu 22.04 LTS must not have the "telnet" package installed.</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 are often overlooked and therefore, may remain unsecure. They increase the risk to the platform by providing additional attack vectors. 
 
Telnet is a client/server application protocol that provides an unencrypted remote access service, which does not provide for the confidentiality and integrity of user passwords or the remote session. If users were allowed to login to a system using Telnet, the privileged user passwords and communications could be compromised. 
 
Removing the "telnetd" package decreases the risk of accidental or intentional activation of the Telnet 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000197</ident><fixtext fixref="F-64120r953261_fix">Remove the "telnetd" package by using the following command:  
  
     $ sudo apt-get remove telnetd</fixtext><fix id="F-64120r953261_fix" /><check system="C-64212r953260_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the "telnetd" package is not installed on Ubuntu 22.04 LTS by using the following command:  
 
     $ dpkg -l | grep telnetd 
 
If the "telnetd" package is installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260484"><title>SRG-OS-000185-GPOS-00079</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260484r958552_rule" weight="10.0" severity="medium"><version>UBTU-22-231010</version><title>Ubuntu 22.04 LTS must implement cryptographic mechanisms to prevent unauthorized disclosure and modification of all information that requires protection at rest.</title><description>&lt;VulnDiscussion&gt;Operating 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001199</ident><ident system="http://cyber.mil/cci">CCI-002475</ident><ident system="http://cyber.mil/cci">CCI-002476</ident><fixtext fixref="F-64121r953264_fix">To encrypt an entire partition, dedicate a partition for encryption in the partition layout.  
  
Note: Encrypting a partition in an already-installed system is more difficult because it will need to be resized and existing partitions changed.</fixtext><fix id="F-64121r953264_fix" /><check system="C-64213r953263_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS prevents unauthorized disclosure or modification of all information requiring at-rest protection by using disk encryption.   
 
Note: If there is a documented and approved reason for not having data-at-rest encryption, this requirement is not applicable. 
  
Determine the partition layout for the system by using the following command:  
  
     $ sudo fdisk -l 
 
     ... 
     Device               Start               End        Sectors       Size  Type 
     /dev/sda1         2048      2203647       2201600          1G  EFI System 
     /dev/sda2  2203648      6397951       4194304          2G  Linux filesystem 
     /dev/sda3  6397952  536868863  530470912  252.9G  Linux filesystem 
     ... 
  
Verify the system partitions are all encrypted by using the following command:  
 
     # more /etc/crypttab 
 
Every persistent disk partition present must have an entry in the file.   
  
If any partitions other than the boot partition or pseudo file systems (such as /proc or /sys) are not listed, this is a finding.</check-content></check></Rule></Group><Group id="V-260485"><title>SRG-OS-000258-GPOS-00099</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260485r991559_rule" weight="10.0" severity="medium"><version>UBTU-22-232010</version><title>Ubuntu 22.04 LTS must have directories that contain system commands set to a mode of "755" or less permissive.</title><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.  
  
Operating 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 has in order to make access decisions regarding the deletion of audit tools.  
  
Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001495</ident><fixtext fixref="F-64122r953267_fix">Configure Ubuntu 22.04 LTS commands directories to be protected from unauthorized access. Run the following command:  
  
     $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type d -exec chmod -R 755 '{}' \;</fixtext><fix id="F-64122r953267_fix" /><check system="C-64214r953266_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the system commands directories have mode "755" or less permissive by using the following command:  
  
     $ find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type d -exec stat -c "%n %a" '{}' \;  
  
If any directories are found to be group-writable or world-writable, this is a finding.</check-content></check></Rule></Group><Group id="V-260486"><title>SRG-OS-000259-GPOS-00100</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260486r991560_rule" weight="10.0" severity="medium"><version>UBTU-22-232015</version><title>Ubuntu 22.04 LTS must have system commands set to a mode of "755" or less permissive.</title><description>&lt;VulnDiscussion&gt;If Ubuntu 22.04 LTS 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 Ubuntu 22.04 LTS 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 must 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001499</ident><fixtext fixref="F-64123r953270_fix">Configure Ubuntu 22.04 LTS commands to be protected from unauthorized access. Run the following command:  
  
     $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type f -exec chmod 755 '{}' \;</fixtext><fix id="F-64123r953270_fix" /><check system="C-64215r953269_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the system commands contained in the following directories have mode "755" or less permissive by using the following command:  
  
     $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type f -exec stat -c "%n %a" '{}' \; 
  
If any files are found to be group-writable or world-writable, this is a finding.</check-content></check></Rule></Group><Group id="V-260487"><title>SRG-OS-000259-GPOS-00100</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260487r991560_rule" weight="10.0" severity="medium"><version>UBTU-22-232020</version><title>Ubuntu 22.04 LTS library files must have mode "755" or less permissive.</title><description>&lt;VulnDiscussion&gt;If the operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.  
  
This requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001499</ident><fixtext fixref="F-64124r953273_fix">Configure the library files to be protected from unauthorized access. Run the following command:  
 
     $ sudo find /lib /lib64 /usr/lib -perm /022 -type f -exec chmod 755 '{}' \;</fixtext><fix id="F-64124r953273_fix" /><check system="C-64216r953272_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the systemwide shared library files contained in the directories "/lib", "/lib64", and "/usr/lib" have mode "755" or less permissive by using the following command:  
  
     $ sudo find /lib /lib64 /usr/lib -perm /022 -type f -exec stat -c "%n %a" '{}' \; 
 
If any files are found to be group-writable or world-writable, this is a finding.</check-content></check></Rule></Group><Group id="V-260488"><title>SRG-OS-000206-GPOS-00084</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260488r958566_rule" weight="10.0" severity="medium"><version>UBTU-22-232025</version><title>Ubuntu 22.04 LTS must configure the "/var/log" directory to have mode "755" or less permissive.</title><description>&lt;VulnDiscussion&gt;Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.  
  
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001314</ident><fixtext fixref="F-64125r953276_fix">Configure the "/var/log" directory to have permissions of "0755" by using the following command:  
 
     $ sudo chmod 0755 /var/log</fixtext><fix id="F-64125r953276_fix" /><check system="C-64217r953275_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the "/var/log" directory has mode of "755" or less permissive by using the following command: 
 
Note: If rsyslog is active and enabled on the operating system, this requirement is not applicable. 
 
     $ stat -c "%n %a" /var/log 
     /var/log 755 
 
If a value of "755" or less permissive is not returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260489"><title>SRG-OS-000205-GPOS-00083</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260489r958564_rule" weight="10.0" severity="medium"><version>UBTU-22-232026</version><title>Ubuntu 22.04 LTS must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.</title><description>&lt;VulnDiscussion&gt;Any operating system providing too much information in error messages risks compromising the data and security of the structure, and content of error messages needs to be carefully considered by the organization.  
  
Organizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers. 
 
The /var/log/btmp, /var/log/wtmp, and /var/log/lastlog files have group write and global read permissions to allow for the lastlog function to perform. Limiting the permissions beyond this configuration will result in the failure of functions that rely on the lastlog database.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001312</ident><fixtext fixref="F-64126r953279_fix">Configure Ubuntu 22.04 LTS to set permissions of all log files under the "/var/log" directory to "640" or more restricted by using the following command: 
 
Note: The btmp, wtmp, and lastlog files are excluded. Refer to the Discussion for details. 
 
     $ sudo find /var/log -perm /137 ! -name '*[bw]tmp' ! -name '*lastlog' -type f -exec chmod 640 '{}' \;</fixtext><fix id="F-64126r953279_fix" /><check system="C-64218r953278_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS has all system log files under the "/var/log" directory with a permission set to "640" or less permissive by using the following command: 
 
Note: The btmp, wtmp, and lastlog files are excluded. Refer to the Discussion for details. 
 
     $ sudo find /var/log -perm /137 ! -name '*[bw]tmp' ! -name '*lastlog' -type f -exec stat -c "%n %a" {} \; 
 
If the command displays any output, this is a finding.</check-content></check></Rule></Group><Group id="V-260490"><title>SRG-OS-000205-GPOS-00083</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260490r1014781_rule" weight="10.0" severity="medium"><version>UBTU-22-232027</version><title>Ubuntu 22.04 LTS must generate system journal entries without revealing information that could be exploited by adversaries.</title><description>&lt;VulnDiscussion&gt;Any operating system providing too much information in error messages risks compromising the data and security of the structure, and content of error messages needs to be carefully considered by the organization.  
  
Organizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001312</ident><fixtext fixref="F-64127r1014780_fix">Configure Ubuntu 22.04 LTS to set the appropriate permissions to the files and directories used by the systemd journal: 
 
Add or modify the following lines in the "/etc/tmpfiles.d/systemd.conf" file: 
z /run/log/journal 2750 root systemd-journal - - 
Z /run/log/journal/%m ~2750 root systemd-journal - - 
z /var/log/journal 2750 root systemd-journal - - 
z /var/log/journal/%m 2750 root systemd-journal - - 
z /var/log/journal/%m/system.journal 0750 root systemd-journal - - 
 
Restart the system for the changes to take effect.</fixtext><fix id="F-64127r1014780_fix" /><check system="C-64219r1014779_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the /run/log/journal and /var/log/journal directories have permissions set to "2750" or less permissive by using the following command:

$ sudo find /run/log/journal /var/log/journal -type d -exec stat -c "%n %a" {} \;
/run/log/journal 2750
/var/log/journal 2750
/var/log/journal/3b018e681c904487b11671b9c1987cce 2750 
 
If any output returned has a permission set greater than "2750", this is a finding. 
 
Verify all files in the /run/log/journal and /var/log/journal directories have permissions set to "640" or less permissive by using the following command: 
 
     $ sudo find /run/log/journal /var/log/journal  -type f -exec stat -c "%n %a" {} \; 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000003c7a-0006073f8d1c0fec.journal 640 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/system.journal 640
     /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000.journal 640 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000@bdedf14602ff4081a77dc7a6debc8626-00000000000062a6-00060b4b414b617a.journal 640
     /var/log/journal/3b018e681c904487b11671b9c1987cce 
 
If any output returned has a permission set greater than "640", this is a finding.</check-content></check></Rule></Group><Group id="V-260491"><title>SRG-OS-000206-GPOS-00084</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260491r958566_rule" weight="10.0" severity="medium"><version>UBTU-22-232030</version><title>Ubuntu 22.04 LTS must configure "/var/log/syslog" file with mode "640" or less permissive.</title><description>&lt;VulnDiscussion&gt;Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.  
  
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001314</ident><fixtext fixref="F-64128r953285_fix">Configure Ubuntu 22.04 LTS to have permissions of "640" for the "/var/log/syslog" file by using the following command:  
  
     $ sudo chmod 0640 /var/log/syslog</fixtext><fix id="F-64128r953285_fix" /><check system="C-64220r953284_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that Ubuntu 22.04 LTS configures the "/var/log/syslog" file with mode "640" or less permissive by using the following command:  
  
     $ stat -c "%n %a" /var/log/syslog  
     /var/log/syslog 640  
  
If a value of "640" or less permissive is not returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260492"><title>SRG-OS-000256-GPOS-00097</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260492r991557_rule" weight="10.0" severity="medium"><version>UBTU-22-232035</version><title>Ubuntu 22.04 LTS must configure audit tools with a mode of "755" or less permissive.</title><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.  
  
Operating 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 in order to make access decisions regarding the access to audit tools.  
  
Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.

Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001493</ident><ident system="http://cyber.mil/cci">CCI-001494</ident><fixtext fixref="F-64129r953288_fix">Configure the audit tools on Ubuntu 22.04 LTS to be protected from unauthorized access by setting the correct permissive mode using the following command:  
  
     $ sudo chmod 755 &lt;audit_tool_name&gt;  
  
Replace "&lt;audit_tool_name&gt;" with the audit tool that does not have the correct permissions.</fixtext><fix id="F-64129r953288_fix" /><check system="C-64221r953287_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS configures the audit tools to have a file permission of "755" or less to prevent unauthorized access by using the following command:  
  
     $ stat -c "%n %a" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/audispd* /sbin/augenrules 
     /sbin/auditctl 755 
     /sbin/aureport 755 
     /sbin/ausearch 755 
     /sbin/autrace 755 
     /sbin/auditd 755 
     /sbin/audispd-zos-remote 755 
     /sbin/augenrules 755 
  
If any of the audit tools have a mode more permissive than "0755", this is a finding.</check-content></check></Rule></Group><Group id="V-260493"><title>SRG-OS-000258-GPOS-00099</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260493r991559_rule" weight="10.0" severity="medium"><version>UBTU-22-232040</version><title>Ubuntu 22.04 LTS must have directories that contain system commands owned by "root".</title><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.  
  
Operating 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 has in order to make access decisions regarding the deletion of audit tools.  
  
Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001495</ident><fixtext fixref="F-64130r953291_fix">Configure Ubuntu 22.04 LTS commands directories to be protected from unauthorized access. Run the following command:  
  
     $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type d -exec chown root '{}' \;</fixtext><fix id="F-64130r953291_fix" /><check system="C-64222r953290_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the system commands directories are owned by "root" by using the following command:  
  
     $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type d -exec stat -c "%n %U" '{}' \; 
  
If any system commands directories are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260494"><title>SRG-OS-000258-GPOS-00099</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260494r991559_rule" weight="10.0" severity="medium"><version>UBTU-22-232045</version><title>Ubuntu 22.04 LTS must have directories that contain system commands group-owned by "root".</title><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.  
  
Operating 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 has in order to make access decisions regarding the deletion of audit tools.  
  
Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001495</ident><fixtext fixref="F-64131r953294_fix">Configure Ubuntu 22.04 LTS commands directories to be protected from unauthorized access. Run the following command:  
  
     $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type d -exec chgrp root '{}' \;</fixtext><fix id="F-64131r953294_fix" /><check system="C-64223r953293_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the system commands directories are group-owned by "root" by using the following command:  
  
     $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type d -exec stat -c "%n %G" '{}' \; 
  
If any system commands directories are returned that are not Set Group ID up on execution (SGID) files and owned by a privileged account, this is a finding.</check-content></check></Rule></Group><Group id="V-260495"><title>SRG-OS-000259-GPOS-00100</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260495r991560_rule" weight="10.0" severity="medium"><version>UBTU-22-232050</version><title>Ubuntu 22.04 LTS must have system commands owned by "root" or a system account.</title><description>&lt;VulnDiscussion&gt;If Ubuntu 22.04 LTS 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 Ubuntu 22.04 LTS 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 must 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001499</ident><fixtext fixref="F-64132r953297_fix">Configure Ubuntu 22.04 LTS commands and their respective parent directories to be protected from unauthorized access. Run the following command, replacing "&lt;command_name&gt;" with any system command not owned by "root" or a required system account:  
  
     $ sudo chown root &lt;command_name&gt;</fixtext><fix id="F-64132r953297_fix" /><check system="C-64224r953296_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the system commands contained in the following directories are owned by "root", or a required system account, by using the following command:  
  
     $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type f -exec stat -c "%n %U" '{}' \; 
  
If any system commands are returned and are not owned by a required system account, this is a finding.</check-content></check></Rule></Group><Group id="V-260496"><title>SRG-OS-000259-GPOS-00100</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260496r991560_rule" weight="10.0" severity="medium"><version>UBTU-22-232055</version><title>Ubuntu 22.04 LTS must have system commands group-owned by "root" or a system account.</title><description>&lt;VulnDiscussion&gt;If Ubuntu 22.04 LTS 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 Ubuntu 22.04 LTS 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 must 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001499</ident><fixtext fixref="F-64133r953300_fix">Configure Ubuntu 22.04 LTS commands to be protected from unauthorized access.

 Run the following command, replacing "&lt;command_name&gt;" with any system command not group-owned by "root" or a required system account:  
  
     $ sudo chgrp root &lt;command_name&gt;</fixtext><fix id="F-64133r953300_fix" /><check system="C-64225r953299_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the system commands contained in the following directories are group-owned by "root" or a required system account by using the following command:  
  
     $ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type f ! -perm /2000 -exec stat -c "%n %G" '{}' \; 
  
If any system commands are returned that are not Set Group ID upon execution (SGID) files and group-owned by a required system account, this is a finding.</check-content></check></Rule></Group><Group id="V-260497"><title>SRG-OS-000259-GPOS-00100</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260497r991560_rule" weight="10.0" severity="medium"><version>UBTU-22-232060</version><title>Ubuntu 22.04 LTS library directories must be owned by "root".</title><description>&lt;VulnDiscussion&gt;If the operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.  
  
This requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001499</ident><fixtext fixref="F-64134r953303_fix">Configure the library files and their respective parent directories to be protected from unauthorized access. Run the following command:  
  
     $ sudo find /lib /usr/lib /lib64 ! -user root -type d -exec chown root '{}' \;</fixtext><fix id="F-64134r953303_fix" /><check system="C-64226r953302_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the systemwide shared library directories "/lib", "/lib64", and "/usr/lib" are owned by "root" by using the following command:  
  
     $ sudo find /lib /usr/lib /lib64 ! -user root -type d -exec stat -c "%n %U" '{}' \; 
  
If any systemwide library directory is returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260498"><title>SRG-OS-000259-GPOS-00100</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260498r991560_rule" weight="10.0" severity="medium"><version>UBTU-22-232065</version><title>Ubuntu 22.04 LTS library directories must be group-owned by "root".</title><description>&lt;VulnDiscussion&gt;If the operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.  
  
This requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001499</ident><fixtext fixref="F-64135r953306_fix">Configure Ubuntu 22.04 LTS library directories to be protected from unauthorized access. Run the following command:  
  
     $ sudo find /lib /usr/lib /lib64 ! -group root -type d -exec chgrp root '{}' \;</fixtext><fix id="F-64135r953306_fix" /><check system="C-64227r953305_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the systemwide library directories "/lib", "/lib64", and "/usr/lib" are group-owned by "root" by using the following command:  
  
     $ sudo find /lib /usr/lib /lib64 ! -group root -type d -exec stat -c "%n %G" '{}' \; 
  
If any systemwide shared library directory is returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260499"><title>SRG-OS-000259-GPOS-00100</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260499r991560_rule" weight="10.0" severity="medium"><version>UBTU-22-232070</version><title>Ubuntu 22.04 LTS library files must be owned by "root".</title><description>&lt;VulnDiscussion&gt;If the operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.  
  
This requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001499</ident><fixtext fixref="F-64136r953309_fix">Configure Ubuntu 22.04 LTS library files to be protected from unauthorized access. Run the following command:  
  
     $ sudo find /lib /usr/lib /lib64 ! -user root -type f -exec chown root '{}' \;</fixtext><fix id="F-64136r953309_fix" /><check system="C-64228r953308_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the systemwide shared library files contained in the directories "/lib", "/lib64", and "/usr/lib" are owned by "root" by using the following command:  
  
     $ sudo find /lib /usr/lib /lib64 ! -user root -type f -exec stat -c "%n %U" '{}' \;  
  
If any systemwide library file is returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260500"><title>SRG-OS-000259-GPOS-00100</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260500r991560_rule" weight="10.0" severity="medium"><version>UBTU-22-232075</version><title>Ubuntu 22.04 LTS library files must be group-owned by "root".</title><description>&lt;VulnDiscussion&gt;If the operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.  
  
This requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001499</ident><fixtext fixref="F-64137r953312_fix">Configure Ubuntu 22.04 LTS library files to be protected from unauthorized access. 

Run the following command, replacing "&lt;command_name&gt;" with any system command not group-owned by "root" or a required system account:  
  
     $ sudo chgrp root &lt;command_name&gt;</fixtext><fix id="F-64137r953312_fix" /><check system="C-64229r953311_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the systemwide library files contained in the directories "/lib", "/lib64", and "/usr/lib" are group-owned by "root", or a required system account, by using the following command:  
  
     $ sudo find /lib /usr/lib /lib64 ! -group root -type f -exec stat -c "%n %G" '{}' \;  
  
If any systemwide shared library file is returned and is not group-owned by a required system account, this is a finding.</check-content></check></Rule></Group><Group id="V-260501"><title>SRG-OS-000206-GPOS-00084</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260501r958566_rule" weight="10.0" severity="medium"><version>UBTU-22-232080</version><title>Ubuntu 22.04 LTS must configure the directories used by the system journal to be owned by "root".</title><description>&lt;VulnDiscussion&gt;Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.  
  
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001314</ident><fixtext fixref="F-64138r953315_fix">Configure Ubuntu 22.04 LTS to set the appropriate ownership to the directories used by the systemd journal: 
 
Add or modify the following lines in the "/usr/lib/tmpfiles.d/systemd.conf" file: 
 
z /run/log/journal 2640 root systemd-journal - - 
z /var/log/journal 2640 root systemd-journal - - 
 
Restart the system for the changes to take effect.</fixtext><fix id="F-64138r953315_fix" /><check system="C-64230r953314_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the /run/log/journal and /var/log/journal directories are owned by "root" by using the following command: 
 
     $ sudo find /run/log/journal /var/log/journal  -type d -exec stat -c "%n %U" {} \; 
     /run/log/journal root 
     /var/log/journal root 
     /var/log/journal/3b018e681c904487b11671b9c1987cce root 
 
If any output returned is not owned by "root", this is a finding.</check-content></check></Rule></Group><Group id="V-260502"><title>SRG-OS-000206-GPOS-00084</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260502r958566_rule" weight="10.0" severity="medium"><version>UBTU-22-232085</version><title>Ubuntu 22.04 LTS must configure the directories used by the system journal to be group-owned by "systemd-journal".</title><description>&lt;VulnDiscussion&gt;Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.  
  
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001314</ident><fixtext fixref="F-64139r953318_fix">Configure Ubuntu 22.04 LTS to set the appropriate group-ownership to the directories used by the systemd journal: 
 
Add or modify the following lines in the "/usr/lib/tmpfiles.d/systemd.conf" file: 
 
z /run/log/journal 2640 root systemd-journal - - 
z /var/log/journal 2640 root systemd-journal - - 
 
Restart the system for the changes to take effect.</fixtext><fix id="F-64139r953318_fix" /><check system="C-64231r953317_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the /run/log/journal and /var/log/journal directories are group-owned by "systemd-journal" by using the following command: 
 
     $ sudo find /run/log/journal /var/log/journal  -type d -exec stat -c "%n %G" {} \; 
     /run/log/journal systemd-journal 
     /var/log/journal systemd-journal 
     /var/log/journal/3b018e681c904487b11671b9c1987cce systemd-journal 
 
If any output returned is not group-owned by "systemd-journal", this is a finding.</check-content></check></Rule></Group><Group id="V-260503"><title>SRG-OS-000206-GPOS-00084</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260503r958566_rule" weight="10.0" severity="medium"><version>UBTU-22-232090</version><title>Ubuntu 22.04 LTS must configure the files used by the system journal to be owned by "root".</title><description>&lt;VulnDiscussion&gt;Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.  
  
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001314</ident><fixtext fixref="F-64140r953321_fix">Configure Ubuntu 22.04 LTS to set the appropriate ownership to the files used by the systemd journal: 
 
Add or modify the following lines in the "/usr/lib/tmpfiles.d/systemd.conf" file: 
 
Z /run/log/journal/%m ~2640 root systemd-journal - - 
z /var/log/journal/%m 2640 root systemd-journal - - 
z /var/log/journal/%m/system.journal 0640 root systemd-journal - - 
 
Restart the system for the changes to take effect.</fixtext><fix id="F-64140r953321_fix" /><check system="C-64232r953320_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the /run/log/journal and /var/log/journal files are owned by "root" by using the following command: 
 
     $ sudo find /run/log/journal /var/log/journal  -type f -exec stat -c "%n %U" {} \; 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000003c7a-0006073f8d1c0fec.journal root 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/system.journal root 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000.journal root 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000@bdedf14602ff4081a77dc7a6debc8626-00000000000062a6-00060b4b414b617a.journal root 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000005301-000609a409
593.journal root 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000000001-000604dae53225ee.journal root 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000@bdedf14602ff4081a77dc7a6debc8626-000000000000083b-000604dae72c7e3b.journal root 
 
If any output returned is not owned by "root", this is a finding.</check-content></check></Rule></Group><Group id="V-260504"><title>SRG-OS-000206-GPOS-00084</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260504r958566_rule" weight="10.0" severity="medium"><version>UBTU-22-232095</version><title>Ubuntu 22.04 LTS must configure the files used by the system journal to be group-owned by "systemd-journal".</title><description>&lt;VulnDiscussion&gt;Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.  
  
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001314</ident><fixtext fixref="F-64141r953324_fix">Configure Ubuntu 22.04 LTS to set the appropriate group-ownership to the files used by the systemd journal: 
 
Add or modify the following line in the "/usr/lib/tmpfiles.d/systemd.conf" file: 
 
Z /run/log/journal/%m ~2640 root systemd-journal - - 
z /var/log/journal/%m 2640 root systemd-journal - - 
z /var/log/journal/%m/system.journal 0640 root systemd-journal - - 
 
Restart the system for the changes to take effect.</fixtext><fix id="F-64141r953324_fix" /><check system="C-64233r953323_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the /run/log/journal and /var/log/journal files are group-owned by "systemd-journal" by using the following command: 
 
     $ sudo find /run/log/journal /var/log/journal  -type f -exec stat -c "%n %G" {} \; 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000003c7a-0006073f8d1c0fec.journal systemd-journal 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/system.journal systemd-journal 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000.journal systemd-journal 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000@bdedf14602ff4081a77dc7a6debc8626-00000000000062a6-00060b4b414b617a.journal systemd-journal 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000005301-000609a409
593.journal systemd-journal 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000000001-000604dae53225ee.journal systemd-journal 
     /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000@bdedf14602ff4081a77dc7a6debc8626-000000000000083b-000604dae72c7e3b.journal systemd-journal 
 
If any output returned is not group-owned by "systemd-journal", this is a finding.</check-content></check></Rule></Group><Group id="V-260505"><title>SRG-OS-000206-GPOS-00084</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260505r958566_rule" weight="10.0" severity="medium"><version>UBTU-22-232100</version><title>Ubuntu 22.04 LTS must be configured so that the "journalctl" command is owned by "root".</title><description>&lt;VulnDiscussion&gt;Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, Personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.  
  
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001314</ident><fixtext fixref="F-64142r953327_fix">Configure "journalctl" to be owned by "root": 
 
     $ sudo chown root /usr/bin/journalctl</fixtext><fix id="F-64142r953327_fix" /><check system="C-64234r953326_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the "journalctl" command is owned by "root" by using the following command: 
 
     $ sudo find /usr/bin/journalctl -exec stat -c "%n %U" {} \; 
     /usr/bin/journalctl root 
 
If "journalctl" is not owned by "root", this is a finding.</check-content></check></Rule></Group><Group id="V-260506"><title>SRG-OS-000206-GPOS-00084</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260506r958566_rule" weight="10.0" severity="medium"><version>UBTU-22-232105</version><title>Ubuntu 22.04 LTS must be configured so that the "journalctl" command is group-owned by "root".</title><description>&lt;VulnDiscussion&gt;Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.  
  
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001314</ident><fixtext fixref="F-64143r953330_fix">Configure "journalctl" to be group-owned by "root": 
 
     $ sudo chown :root /usr/bin/journalctl</fixtext><fix id="F-64143r953330_fix" /><check system="C-64235r953329_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the "journalctl" command is group-owned by "root" by using the following command: 
 
     $ sudo find /usr/bin/journalctl -exec stat -c "%n %G" {} \; 
     /usr/bin/journalctl root 
 
If "journalctl" is not group-owned by "root", this is a finding.</check-content></check></Rule></Group><Group id="V-260507"><title>SRG-OS-000256-GPOS-00097</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260507r991557_rule" weight="10.0" severity="medium"><version>UBTU-22-232110</version><title>Ubuntu 22.04 LTS must configure audit tools to be owned by "root".</title><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.  
  
Operating 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 in order to make access decisions regarding the access to audit tools.  
  
Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.

Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001493</ident><ident system="http://cyber.mil/cci">CCI-001494</ident><fixtext fixref="F-64144r953333_fix">Configure the audit tools on Ubuntu 22.04 LTS to be protected from unauthorized access by setting the file owner as root using the following command:  
  
     $ sudo chown root &lt;audit_tool_name&gt;  
  
Replace "&lt;audit_tool_name&gt;" with each audit tool not owned by "root".</fixtext><fix id="F-64144r953333_fix" /><check system="C-64236r953332_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS configures the audit tools to be owned by "root" to prevent any unauthorized access with the following command:  
  
     $ stat -c "%n %U" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/audispd* /sbin/augenrules 
     /sbin/auditctl root 
     /sbin/aureport root 
     /sbin/ausearch root 
     /sbin/autrace root 
     /sbin/auditd root 
     /sbin/audispd-zos-remote root 
     /sbin/augenrules root 
 
If any of the audit tools are not owned by "root", this is a finding.</check-content></check></Rule></Group><Group id="V-260508"><title>SRG-OS-000206-GPOS-00084</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260508r958566_rule" weight="10.0" severity="medium"><version>UBTU-22-232120</version><title>Ubuntu 22.04 LTS must configure the "/var/log" directory to be owned by "root".</title><description>&lt;VulnDiscussion&gt;Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.  
  
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001314</ident><fixtext fixref="F-64145r953336_fix">Configure Ubuntu 22.04 LTS to have root own the "/var/log" directory by using the following command:  
  
     $ sudo chown root /var/log</fixtext><fix id="F-64145r953336_fix" /><check system="C-64237r953335_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS configures the "/var/log" directory to be owned by "root" by using the following command:  
  
     $ stat -c "%n %U" /var/log 
     /var/log root  
  
If the "/var/log" directory is not owned by "root", this is a finding.</check-content></check></Rule></Group><Group id="V-260509"><title>SRG-OS-000206-GPOS-00084</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260509r958566_rule" weight="10.0" severity="medium"><version>UBTU-22-232125</version><title>Ubuntu 22.04 LTS must configure the "/var/log" directory to be group-owned by "syslog".</title><description>&lt;VulnDiscussion&gt;Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.  
  
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001314</ident><fixtext fixref="F-64146r953339_fix">Configure Ubuntu 22.04 LTS to have syslog group-own the "/var/log" directory by using the following command:  
  
     $ sudo chgrp syslog /var/log</fixtext><fix id="F-64146r953339_fix" /><check system="C-64238r953338_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that Ubuntu 22.04 LTS configures the "/var/log" directory to be group-owned by "syslog" by using the following command:  
  
     $ stat -c "%n %G" /var/log 
     /var/log syslog  
  
If the "/var/log" directory is not group-owned by "syslog", this is a finding.</check-content></check></Rule></Group><Group id="V-260510"><title>SRG-OS-000206-GPOS-00084</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260510r958566_rule" weight="10.0" severity="medium"><version>UBTU-22-232130</version><title>Ubuntu 22.04 LTS must configure "/var/log/syslog" file to be owned by "syslog".</title><description>&lt;VulnDiscussion&gt;Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.  
  
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001314</ident><fixtext fixref="F-64147r953342_fix">Configure Ubuntu 22.04 LTS to have syslog own the "/var/log/syslog" file by using the following command:  
  
     $ sudo chown syslog /var/log/syslog</fixtext><fix id="F-64147r953342_fix" /><check system="C-64239r953341_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that Ubuntu 22.04 LTS configures the "/var/log/syslog" file to be owned by "syslog" by using the following command:  
  
     $ stat -c "%n %U" /var/log/syslog 
     /var/log/syslog  
  
If the "/var/log/syslog" file is not owned by "syslog", this is a finding.</check-content></check></Rule></Group><Group id="V-260511"><title>SRG-OS-000206-GPOS-00084</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260511r958566_rule" weight="10.0" severity="medium"><version>UBTU-22-232135</version><title>Ubuntu 22.04 LTS must configure the "/var/log/syslog" file to be group-owned by "adm".</title><description>&lt;VulnDiscussion&gt;Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the operating system or platform. Additionally, personally identifiable information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.  
  
The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001314</ident><fixtext fixref="F-64148r953345_fix">Configure Ubuntu 22.04 LTS to have adm group-own the "/var/log/syslog" file by using the following command:  
  
     $ sudo chgrp adm /var/log/syslog</fixtext><fix id="F-64148r953345_fix" /><check system="C-64240r953344_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that Ubuntu 22.04 LTS configures the "/var/log/syslog" file to be group-owned by "adm" by using the following command:  
  
     $ stat -c "%n %G" /var/log/syslog 
     /var/log/syslog adm  
  
If the "/var/log/syslog" file is not group-owned by "adm", this is a finding.</check-content></check></Rule></Group><Group id="V-260512"><title>SRG-OS-000205-GPOS-00083</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260512r958564_rule" weight="10.0" severity="medium"><version>UBTU-22-232140</version><title>Ubuntu 22.04 LTS must be configured so that the "journalctl" command is not accessible by unauthorized users.</title><description>&lt;VulnDiscussion&gt;Any operating system providing too much information in error messages risks compromising the data and security of the structure, and content of error messages needs to be carefully considered by the organization.  
  
Organizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001312</ident><fixtext fixref="F-64149r953348_fix">Configure "journalctl" to have a permission set of "740": 
 
     $ sudo chmod 740 /usr/bin/journalctl</fixtext><fix id="F-64149r953348_fix" /><check system="C-64241r953347_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the "journalctl" command has a permission set of "740" by using the following command: 
 
     $ sudo find /usr/bin/journalctl -exec stat -c "%n %a" {} \; 
     /usr/bin/journalctl 740 
 
If "journalctl" is not set to "740", this is a finding.</check-content></check></Rule></Group><Group id="V-260513"><title>SRG-OS-000138-GPOS-00069</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260513r958524_rule" weight="10.0" severity="medium"><version>UBTU-22-232145</version><title>Ubuntu 22.04 LTS must set a sticky bit on all public directories to prevent unauthorized and unintended information transferred via shared system resources.</title><description>&lt;VulnDiscussion&gt;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.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001090</ident><fixtext fixref="F-64150r953351_fix">Configure all public directories to have the sticky bit set to prevent unauthorized and unintended information transferred via shared system resources.  
  
Set the sticky bit on all public directories using the following command, replacing "&lt;public_directory_name&gt;" with any directory path missing the sticky bit:  
  
     $ sudo chmod +t  &lt;public_directory_name&gt;</fixtext><fix id="F-64150r953351_fix" /><check system="C-64242r953350_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that all public directories have the public sticky bit set by using the following command:   
  
     $ sudo find / -type d -perm -002 ! -perm -1000 
  
If any public directories are found missing the sticky bit, this is a finding.</check-content></check></Rule></Group><Group id="V-260514"><title>SRG-OS-000297-GPOS-00115</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260514r958672_rule" weight="10.0" severity="medium"><version>UBTU-22-251010</version><title>Ubuntu 22.04 LTS must have an application firewall installed in order to control remote access methods.</title><description>&lt;VulnDiscussion&gt;Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best.  
  
Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.  
  
Ubuntu 22.04 LTS functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002314</ident><fixtext fixref="F-64151r953354_fix">Install the Uncomplicated Firewall by using the following command:  
  
     $ sudo apt-get install ufw</fixtext><fix id="F-64151r953354_fix" /><check system="C-64243r953353_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the Uncomplicated Firewall is installed by using the following command:  
  
     $ dpkg -l | grep ufw 
     ii     ufw     0.36.1-4ubuntu0.1     all     program for managing a Netfilter firewall 
  
If the "ufw" package is not installed, ask the system administrator if another application firewall is installed.   
  
If no application firewall is installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260515"><title>SRG-OS-000297-GPOS-00115</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260515r958672_rule" weight="10.0" severity="medium"><version>UBTU-22-251015</version><title>Ubuntu 22.04 LTS must enable and run the Uncomplicated Firewall (ufw).</title><description>&lt;VulnDiscussion&gt;Remote access services, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best.  
  
Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.  
  
Ubuntu 22.04 LTS functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002314</ident><fixtext fixref="F-64152r953357_fix">Enable the ufw by using the following command:  
  
     $ sudo ufw enable</fixtext><fix id="F-64152r953357_fix" /><check system="C-64244r953356_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the ufw is enabled on the system with the following command:  
  
     $ sudo ufw status 
     Status: active 
  
If the above command returns the status as "inactive" or any type of error, this is a finding.</check-content></check></Rule></Group><Group id="V-260516"><title>SRG-OS-000480-GPOS-00232</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260516r991593_rule" weight="10.0" severity="medium"><version>UBTU-22-251020</version><title>Ubuntu 22.04 LTS must have an application firewall enabled.</title><description>&lt;VulnDiscussion&gt;Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Application firewalls limit which applications are allowed to communicate over the network.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64153r953360_fix">Enable and start the ufw by using the following command:  
  
     $ sudo systemctl enable ufw.service --now</fixtext><fix id="F-64153r953360_fix" /><check system="C-64245r953359_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the Uncomplicated Firewall (ufw) is enabled on the system with the following command:  
  
     $ systemctl status ufw.service | grep -i "active:" 
     Active: active (exited) since Thu 2022-12-25 00:00:01 NZTD; 365 days 11h ago 
  
If "ufw.service" is "inactive", this is a finding.  
  
If the ufw is not installed, ask the system administrator if another application firewall is installed. If no application firewall is installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260517"><title>SRG-OS-000420-GPOS-00186</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260517r958902_rule" weight="10.0" severity="medium"><version>UBTU-22-251025</version><title>Ubuntu 22.04 LTS must configure the Uncomplicated Firewall (ufw) to rate-limit impacted network interfaces.</title><description>&lt;VulnDiscussion&gt;Denial of service (DoS) is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity.  
  
This requirement addresses the configuration of the operating system to mitigate the impact of DoS attacks that have occurred or are ongoing on system availability. For each system, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or establishing memory partitions). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002385</ident><fixtext fixref="F-64154r953363_fix">Configure the application firewall to protect against or limit the effects of DoS attacks by ensuring Ubuntu 22.04 LTS is implementing rate-limiting measures on impacted network interfaces.  
  
For each service with a port listening to connections, run the following command, replacing "&lt;service_name&gt;" with the service that needs to be rate limited.  
  
     $ sudo ufw limit &lt;service_name&gt;  
  
Rate-limiting can also be done on an interface. An example of adding a rate limit on the "ens160" interface follows:  
  
     $ sudo ufw limit in on ens160</fixtext><fix id="F-64154r953363_fix" /><check system="C-64246r953362_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify an application firewall is configured to rate limit any connection to the system.  
  
Check all the services listening to the ports by using the following command:  
  
     $ ss -l46ut 
     Netid               State          Recv-Q          Send-Q                               Local Address:Port            Peer Address:Port               Process                 
     tcp                 LISTEN               0                     511                                           *:http                                          *:*  
     tcp                 LISTEN               0                     128                                           [::]:ssh                                        [::]:* 
     tcp                 LISTEN               0                     128                                           [::]:ipp                                        [::]:*  
     tcp                 LISTEN               0                     128                                           [::]:smtp                                    [::]:* 
 
  
For each entry, verify that the ufw is configured to rate limit the service ports by using the following command:  
  
     $ sudo ufw status  
     Status: active  
  
     To                           Action     From  
     --                             ------         ----  
     80/tcp                    LIMIT       Anywhere 
     25/tcp                    LIMIT       Anywhere 
     Anywhere            DENY       240.9.19.81 
     443                           LIMIT      Anywhere        
     22/tcp                     LIMIT      Anywhere     
     80/tcp (v6)            LIMIT      Anywhere 
     25/tcp (v6)            LIMIT      Anywhere                
     22/tcp (v6)            LIMIT      Anywhere (v6)  
 
     25                             DENY OUT    Anywhere 
     25 (v6)                    DENY OUT    Anywhere (v6) 
 
If any port with a state of "LISTEN" that does not have an action of "DENY", is not marked with the "LIMIT" action, this is a finding.</check-content></check></Rule></Group><Group id="V-260518"><title>SRG-OS-000096-GPOS-00050</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260518r958480_rule" weight="10.0" severity="medium"><version>UBTU-22-251030</version><title>Ubuntu 22.04 LTS must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.</title><description>&lt;VulnDiscussion&gt;To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.  
  
Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. 

To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000382</ident><fixtext fixref="F-64155r953366_fix">Add all ports, protocols, or services allowed by the PPSM CLSA by using the following command:  
  
     $ sudo ufw allow &lt;direction&gt; &lt;port/protocol/service&gt;  
  
Where the direction is "in" or "out" and the port is the one corresponding to the protocol or service allowed.  
  
To deny access to ports, protocols, or services, use:  
  
     $ sudo ufw deny &lt;direction&gt; &lt;port/protocol/service&gt;</fixtext><fix id="F-64155r953366_fix" /><check system="C-64247r953365_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Check the firewall configuration for any unnecessary or prohibited functions, ports, protocols, and/or services by using the following command: 
  
     $ sudo ufw show raw 
     Chain INPUT (policy ACCEPT 0 packets, 0 bytes)  
          pkts      bytes target     prot opt in     out     source               destination  
  
     Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)  
         pkts      bytes target     prot opt in     out     source               destination  
  
     Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)  
         pkts      bytes target     prot opt in     out     source               destination  
  
Ask the system administrator for the site or program PPSM CLSA. Verify the services allowed by the firewall match the PPSM CLSA.   
  
If there are any additional ports, protocols, or services that are not included in the PPSM CLSA, this is a finding.  
  
If there are any ports, protocols, or services that are prohibited by the PPSM CAL, this is a finding.</check-content></check></Rule></Group><Group id="V-260519"><title>SRG-OS-000355-GPOS-00143</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260519r1038944_rule" weight="10.0" severity="low"><version>UBTU-22-252010</version><title>Ubuntu 22.04 LTS must, for networked systems, compare internal information system clocks at least every 24 hours with a server synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).</title><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.  
  
Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network.  
  
Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). 
 
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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004923</ident><ident system="http://cyber.mil/cci">CCI-001891</ident><fixtext fixref="F-64156r953369_fix">Configure Ubuntu 22.04 LTS to compare the system clock at least every 24 hours to the authoritative time source. 
 
Add or modify the following line in the "/etc/chrony/chrony.conf" file: 
  
server [source] iburst maxpoll = 16  
  
Restart "chrony.service" for the changes to take effect by using the following command:  
  
     $ sudo systemctl restart chrony.service</fixtext><fix id="F-64156r953369_fix" /><check system="C-64248r953368_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS is configured to compare the system clock at least every 24 hours to the authoritative time source by using the following command: 
 
Note: If the system is not networked, this requirement is not applicable. 
 
     $ sudo grep maxpoll -ir /etc/chrony* 
     server tick.usno.navy.mil iburst maxpoll 16 
  
If the "maxpoll" option is set to a number greater than 16, the line is commented out, or is missing, this is a finding. 
  
Verify that the "chrony.conf" file is configured to an authoritative DOD time source by using the following command:  
  
     $ sudo grep -ir server /etc/chrony* 
     server tick.usno.navy.mil iburst maxpoll 16 
     server tock.usno.navy.mil iburst maxpoll 16 
     server ntp2.usno.navy.mil iburst maxpoll 16 
  
If "server" is not defined, is not set to an authoritative DOD time source, is commented out, or missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260520"><title>SRG-OS-000356-GPOS-00144</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260520r1044776_rule" weight="10.0" severity="low"><version>UBTU-22-252015</version><title>Ubuntu 22.04 LTS must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second.</title><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.  
  
Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider setting time periods for different types of systems (e.g., financial, legal, or mission-critical systems).  
  
Organizations should also consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). This requirement is related to the comparison done every 24 hours in SRG-OS-000355 because a comparison must be done to determine the time difference.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004926</ident><ident system="http://cyber.mil/cci">CCI-002046</ident><fixtext fixref="F-64157r1044775_fix">Configure chrony to synchronize the internal system clocks to the authoritative source when the time difference is greater than one second by doing the following:  
  
Edit the "/etc/chrony/chrony.conf" file and add:  
 
     makestep 1 -1 
 
Restart the chrony service:  
  
     $ sudo systemctl restart chrony.service</fixtext><fix id="F-64157r1044775_fix" /><check system="C-64249r1044774_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS synchronizes internal system clocks to the authoritative time source when the time difference is greater than one second.  
 
Note: If the system is not networked, this requirement is not applicable. 
 
Check the value of "makestep" by using the following command:  
  
     $ grep -ir makestep /etc/chrony* 
     makestep 1 -1 
 
If "makestep" is not set to "1 -1", is commented out, or is missing, this is a finding. 
 
Verify the NTP service is active and the system clock is synchronized with the authoritative time source: 
 
     $ timedatectl | grep -Ei '(synchronized|service)' 
     System clock synchronized: yes 
     NTP service: active 
 
If the NTP service is not active, this is a finding.

If the system clock is not synchronized, this is a finding.</check-content></check></Rule></Group><Group id="V-260521"><title>SRG-OS-000359-GPOS-00146</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260521r958788_rule" weight="10.0" severity="low"><version>UBTU-22-252020</version><title>Ubuntu 22.04 LTS must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC).</title><description>&lt;VulnDiscussion&gt;If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.  
  
Time stamps generated by the operating system include date and time. Time is commonly expressed in UTC or local time with an offset from UTC.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001890</ident><fixtext fixref="F-64158r953375_fix">To Configure Ubuntu 22.04 LTS time zone to use UTC, run the following command: 
  
     $ sudo timedatectl set-timezone Etc/UTC</fixtext><fix id="F-64158r953375_fix" /><check system="C-64250r953374_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the time zone is configured to use UTC by using the following command:  
  
     $ timedatectl status | grep -i "time zone" 
     Time zone: Etc/UTC (UTC, +0000) 
  
If "Time zone" is not set to UTC, this is a finding.</check-content></check></Rule></Group><Group id="V-260522"><title>SRG-OS-000142-GPOS-00071</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260522r958528_rule" weight="10.0" severity="medium"><version>UBTU-22-253010</version><title>Ubuntu 22.04 LTS must be configured to use TCP syncookies.</title><description>&lt;VulnDiscussion&gt;DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity.   
  
Managing excess capacity ensures that sufficient capacity is available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the susceptibility to some DoS attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001095</ident><fixtext fixref="F-64159r953378_fix">Configure Ubuntu 22.04 LTS to use TCP syncookies by using the following command:  
  
     $ sudo sysctl -w net.ipv4.tcp_syncookies = 1  
  
If "1" is not the system's default value, add or update the following line in "/etc/sysctl.conf":  
  
     net.ipv4.tcp_syncookies = 1</fixtext><fix id="F-64159r953378_fix" /><check system="C-64251r953377_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS is configured to use TCP syncookies by using the following command: 
 
     $ sysctl net.ipv4.tcp_syncookies 
     net.ipv4.tcp_syncookies = 1 
 
If the value is not "1", this is a finding. 
  
Check the saved value of TCP syncookies by using the following command:  
  
     $ sudo grep -ir net.ipv4.tcp_syncookies /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 2&gt; /dev/null 
 
If the "net.ipv4.tcp_syncookies" option is not set to "1", is commented out, or is missing, this is a finding. 
 
If conflicting results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260523"><title>SRG-OS-000423-GPOS-00187</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260523r958908_rule" weight="10.0" severity="high"><version>UBTU-22-255010</version><title>Ubuntu 22.04 LTS must have SSH installed.</title><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.

Satisfies: SRG-OS-000423-GPOS-00187, 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002418</ident><ident system="http://cyber.mil/cci">CCI-002420</ident><ident system="http://cyber.mil/cci">CCI-002422</ident><fixtext fixref="F-64160r953381_fix">Install the "ssh" meta-package by using the following command:  
  
     $ sudo apt install ssh</fixtext><fix id="F-64160r953381_fix" /><check system="C-64252r953380_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the SSH package is installed by using the following command:  
  
     $ sudo dpkg -l | grep openssh 
     ii     openssh-client     1:8.9p1-3ubuntu0.4     amd64     secure shell (SSH) client, for secure access to remote machines 
     ii  openssh-server     1:8.9p1-3ubuntu0.4     amd64     secure shell (SSH) server, for secure access from remote machines 
     ii  openssh-sftp-server     1:8.9p1-3ubuntu0.4     amd64     secure shell (SSH) sftp server module, for SFTP access from remote machines  
 
If the "openssh" server package is not installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260524"><title>SRG-OS-000423-GPOS-00187</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260524r958908_rule" weight="10.0" severity="high"><version>UBTU-22-255015</version><title>Ubuntu 22.04 LTS must use SSH to protect the confidentiality and integrity of transmitted information.</title><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.

Satisfies: SRG-OS-000423-GPOS-00187, 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002418</ident><ident system="http://cyber.mil/cci">CCI-002420</ident><ident system="http://cyber.mil/cci">CCI-002422</ident><fixtext fixref="F-64161r953384_fix">Enable and start the "ssh.service" by using the following command:  
  
     $ sudo systemctl enable ssh.service --now</fixtext><fix id="F-64161r953384_fix" /><check system="C-64253r953383_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the "ssh.service" is enabled and active by using the following commands:  
  
     $ sudo systemctl is-enabled ssh 
     enabled 
 
     $ sudo systemctl is-active ssh 
     active 
 
If "ssh.service" is not enabled and active, this is a finding.</check-content></check></Rule></Group><Group id="V-260525"><title>SRG-OS-000023-GPOS-00006</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260525r958390_rule" weight="10.0" severity="medium"><version>UBTU-22-255020</version><title>Ubuntu 22.04 LTS must display the Standard Mandatory DOD Notice and Consent Banner before granting any local or remote connection to the system.</title><description>&lt;VulnDiscussion&gt;Display of a standardized and approved use notification before granting access to the publicly accessible operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.  
  
System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.  
  
The banner must be formatted in accordance with applicable DOD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:  
  
"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.  
  
By using this IS (which includes any device attached to this IS), you consent to the following conditions:  
  
-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.  
  
-At any time, the USG may inspect and seize data stored on this IS.  
  
-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.  
  
-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.  
  
-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."  
  
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:  
  
"I've read (literal ampersand) consent to terms in IS user agreem't."

Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000048</ident><ident system="http://cyber.mil/cci">CCI-001384</ident><ident system="http://cyber.mil/cci">CCI-001385</ident><ident system="http://cyber.mil/cci">CCI-001386</ident><ident system="http://cyber.mil/cci">CCI-001387</ident><ident system="http://cyber.mil/cci">CCI-001388</ident><fixtext fixref="F-64162r953387_fix">Set the parameter Banner in "/etc/ssh/sshd_config" to point to the "/etc/issue.net" file:  
  
     $ sudo sed -i '/^Banner/d' /etc/ssh/sshd_config 
     $ sudo sed -i '$aBanner /etc/issue.net' /etc/ssh/sshd_config  
  
Replace the text in "/etc/issue.net" with the Standard Mandatory DOD Notice and Consent Banner:  
  
You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions:

-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. 
-At any time, the USG may inspect and seize data stored on this IS. 
-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. 
-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. 
-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.  
  
Restart the SSH daemon for the changes to take effect and then signal the SSH server to reload the configuration file:  
  
     $ sudo systemctl -s SIGHUP kill sshd</fixtext><fix id="F-64162r953387_fix" /><check system="C-64254r953386_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS displays the Standard Mandatory DOD Notice and Consent Banner before granting access to Ubuntu 22.04 LTS via an SSH logon by using the following command:  
  
     $ sudo /usr/sbin/sshd -dd 2&gt;&amp;1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH 'banner' 
     /etc/ssh/sshd_config:Banner /etc/issue.net 
  
The command will return the banner option along with the name of the file that contains the SSH banner. If the line is commented out, missing, or conflicting results are returned, this is a finding. 
  
Verify the specified banner file matches the Standard Mandatory DOD Notice and Consent Banner exactly:  
  
     $ cat /etc/issue.net  
     You are accessing a U.S. Government (USG) Information System (IS) that is 
     provided for USG-authorized use only. By using this IS (which includes any 
     device attached to this IS), you consent to the following conditions: 
     -The USG routinely intercepts and monitors communications on this IS for 
     purposes including, but not limited to, penetration testing, COMSEC monitoring, 
     network operations and defense, personnel misconduct (PM), law enforcement 
     (LE), and counterintelligence (CI) investigations. 
     -At any time, the USG may inspect and seize data stored on this IS. 
     -Communications using, or data stored on, this IS are not private, are subject 
     to routine monitoring, interception, and search, and may be disclosed or used 
     for any USG-authorized purpose. 
     -This IS includes security measures (e.g., authentication and access controls) 
     to protect USG interests--not for your personal benefit or privacy. 
     -Notwithstanding the above, using this IS does not constitute consent to PM, LE 
     or CI investigative searching or monitoring of the content of privileged 
     communications, or work product, related to personal representation or services 
     by attorneys, psychotherapists, or clergy, and their assistants. Such 
     communications and work product are private and confidential. See User 
     Agreement for details. 
 
If the banner text does not match the Standard Mandatory DOD Notice and Consent Banner exactly, this is a finding.</check-content></check></Rule></Group><Group id="V-260526"><title>SRG-OS-000480-GPOS-00229</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260526r991591_rule" weight="10.0" severity="high"><version>UBTU-22-255025</version><title>Ubuntu 22.04 LTS must not allow unattended or automatic login via SSH.</title><description>&lt;VulnDiscussion&gt;Failure to restrict system access to authenticated users negatively impacts Ubuntu 22.04 LTS security.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64163r953390_fix">Configure the SSH server to not allow unattended or automatic login to the system.  
  
Add or modify the following lines in the "/etc/ssh/sshd_config" file:  
  
PermitEmptyPasswords no 
PermitUserEnvironment no 
  
Restart the SSH daemon for the changes to take effect: 
  
     $ sudo systemctl restart sshd.service</fixtext><fix id="F-64163r953390_fix" /><check system="C-64255r953389_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that unattended or automatic login via SSH is disabled by using the following command: 
 
     $ sudo /usr/sbin/sshd -dd 2&gt;&amp;1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iEH '(permit(.*?)(passwords|environment))' 
     /etc/ssh/sshd_config:PermitEmptyPasswords no 
     /etc/ssh/sshd_config:PermitUserEnvironment no 
 
If "PermitEmptyPasswords" and "PermitUserEnvironment" are not set to "no", are commented out, are missing, or conflicting results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260527"><title>SRG-OS-000126-GPOS-00066</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260527r986275_rule" weight="10.0" severity="medium"><version>UBTU-22-255030</version><title>Ubuntu 22.04 LTS must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive.</title><description>&lt;VulnDiscussion&gt;Terminating an unresponsive 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, deallocating associated TCP/IP address/port pairs at the operating system level and deallocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean the operating system terminates all sessions or network access; it only ends the unresponsive session and releases the resources associated with that session.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001133</ident><fixtext fixref="F-64164r953393_fix">Configure the SSH server to terminate a user session automatically after the SSH client has become unresponsive. 
 
Note: This setting must be applied in conjunction with UBTU-22-255040 to function correctly. 
 
Add or modify the following line in the "/etc/ssh/sshd_config" file: 
  
ClientAliveCountMax 1 
  
Restart the SSH daemon for the changes to take effect:  
  
     $ sudo systemctl restart sshd.service</fixtext><fix id="F-64164r953393_fix" /><check system="C-64256r953392_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the SSH server automatically terminates a user session after the SSH client has become unresponsive by using the following command:  
 
     $ sudo /usr/sbin/sshd -dd 2&gt;&amp;1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH 'clientalivecountmax' 
     /etc/ssh/sshd_config:ClientAliveCountMax 1 
 
If "ClientAliveCountMax" is not to "1", if conflicting results are returned, is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260528"><title>SRG-OS-000163-GPOS-00072</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260528r970703_rule" weight="10.0" severity="medium"><version>UBTU-22-255035</version><title>Ubuntu 22.04 LTS must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive.</title><description>&lt;VulnDiscussion&gt;Terminating an unresponsive 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, deallocating associated TCP/IP address/port pairs at the operating system level and deallocating 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 unresponsive session and releases the resources associated with that session.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001133</ident><fixtext fixref="F-64165r953396_fix">Configure the SSH server to terminate a user session automatically after the SSH client has been unresponsive for 10 minutes. 
 
Note: This setting must be applied in conjunction with UBTU-22-255040 to function correctly. 
 
Add or modify the following line in the "/etc/ssh/sshd_config" file: 
 
ClientAliveInterval 600 
 
Restart the SSH daemon for the changes to take effect: 
 
     $ sudo systemctl restart sshd.service</fixtext><fix id="F-64165r953396_fix" /><check system="C-64257r953395_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the SSH server automatically terminates a user session after the SSH client has been unresponsive for 10 minutes by using the following command: 
 
     $ sudo /usr/sbin/sshd -dd 2&gt;&amp;1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH 'clientaliveinterval' 
     /etc/ssh/sshd_config:ClientAliveInterval 600 
 
If "ClientAliveInterval" does not exist, is not set to a value of "600" or less, if conflicting results are returned, is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260529"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260529r991589_rule" weight="10.0" severity="high"><version>UBTU-22-255040</version><title>Ubuntu 22.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements.</title><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 system's 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64166r953399_fix">Configure the SSH server to disable X11 forwarding.  
 
Add or modify the following line in the "/etc/ssh/sshd_config" file: 
 
X11Forwarding no  
  
Restart the SSH daemon for the changes to take effect:  
  
     $ sudo systemctl restart sshd.service</fixtext><fix id="F-64166r953399_fix" /><check system="C-64258r953398_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that X11 forwarding is disabled by using the following command:  
 
     $ sudo /usr/sbin/sshd -dd 2&gt;&amp;1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH 'x11forwarding' 
     /etc/ssh/sshd_config:X11Forwarding no 
  
If "X11Forwarding" is set to "yes" and is not documented with the information system security officer (ISSO) as an operational requirement, is commented out, is missing, or conflicting results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260530"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260530r991589_rule" weight="10.0" severity="medium"><version>UBTU-22-255045</version><title>Ubuntu 22.04 LTS SSH daemon must prevent remote hosts from connecting to the proxy display.</title><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 DISPLAY 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64167r953402_fix">Configure the SSH server to prevent remote hosts from connecting to the proxy display.  
  
Add or modify the following line in the "/etc/ssh/sshd_config" file: 
 
X11UseLocalhost yes 
 
Restart the SSH daemon for the changes to take effect:  
 
     $ sudo systemctl restart sshd.service</fixtext><fix id="F-64167r953402_fix" /><check system="C-64259r953401_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the SSH server prevents remote hosts from connecting to the proxy display by using the following command: 
 
     $ sudo /usr/sbin/sshd -dd 2&gt;&amp;1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH 'x11uselocalhost' 
     /etc/ssh/sshd_config:X11UseLocalhost yes 
 
If "X11UseLocalhost" is set to "no", is commented out, is missing, or conflicting results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260531"><title>SRG-OS-000033-GPOS-00014</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260531r958408_rule" weight="10.0" severity="medium"><version>UBTU-22-255050</version><title>Ubuntu 22.04 LTS must configure the SSH daemon to use FIPS 140-3-approved ciphers to prevent the unauthorized disclosure of information and/or detect changes to information during transmission.</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, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.   
  
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network.   
  
Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.   
  
Encrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions which have common application in digital signatures, checksums, and message authentication codes.  
  
By specifying a cipher list with the order of ciphers being in a "strongest to weakest" orientation, the system will automatically attempt to use the strongest cipher for securing SSH connections.

Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000394-GPOS-00174, 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000068</ident><ident system="http://cyber.mil/cci">CCI-002421</ident><ident system="http://cyber.mil/cci">CCI-003123</ident><fixtext fixref="F-64168r953405_fix">Configure the SSH server to only implement FIPS-approved ciphers.  
  
Add or modify the following line in the "/etc/ssh/sshd_config" file: 
  
Ciphers aes256-ctr,aes256-gcm@openssh.com,aes192-ctr,aes128-ctr,aes128-gcm@openssh.com 
  
Restart the SSH server for the changes to take effect:  
  
     $ sudo systemctl restart sshd.service</fixtext><fix id="F-64168r953405_fix" /><check system="C-64260r953404_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the SSH server is configured to only implement FIPS-approved ciphers with the following command: 
 
     $ sudo /usr/sbin/sshd -dd 2&gt;&amp;1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH 'ciphers' 
     /etc/ssh/sshd_config:Ciphers aes256-ctr,aes256-gcm@openssh.com,aes192-ctr,aes128-ctr,aes128-gcm@openssh.com 
  
If "Ciphers" does not contain only the ciphers "aes256-ctr,aes256-gcm@openssh.com,aes192-ctr,aes128-ctr,aes128-gcm@openssh.com" in exact order, is commented out, is missing, or conflicting results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260532"><title>SRG-OS-000250-GPOS-00093</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260532r991554_rule" weight="10.0" severity="medium"><version>UBTU-22-255055</version><title>Ubuntu 22.04 LTS must configure the SSH daemon to use Message Authentication Codes (MACs) employing FIPS 140-3-approved cryptographic hashes to prevent the unauthorized disclosure of information and/or detect changes to information during transmission.</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. Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network.   
  
Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.   
  
Encrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions, which have common application in digital signatures, checksums, and message authentication codes.

Satisfies: SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001453</ident><ident system="http://cyber.mil/cci">CCI-002421</ident><ident system="http://cyber.mil/cci">CCI-002890</ident><fixtext fixref="F-64169r953408_fix">Configure the SSH server to only use MACs that employ FIPS 140-3 approved hashes.  
  
Add or modify the following line in the "/etc/ssh/sshd_config" file: 
 
MACs hmac-sha2-512,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha2-256-etm@openssh.com 
  
Restart the SSH server for the changes to take effect:  
  
     $ sudo systemctl reload sshd.service</fixtext><fix id="F-64169r953408_fix" /><check system="C-64261r953407_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the SSH server is configured to only use MACs that employ FIPS 140-3 approved ciphers by using the following command: 
 
     $ sudo /usr/sbin/sshd -dd 2&gt;&amp;1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH 'macs' 
     /etc/ssh/sshd_config:MACs hmac-sha2-512,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha2-256-etm@openssh.com 
 
If "MACs" does not contain only the hashes "hmac-sha2-512,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha2-256-etm@openssh.com" in exact order, is commented out, is missing, or conflicting results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260533"><title>SRG-OS-000033-GPOS-00014</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260533r958408_rule" weight="10.0" severity="medium"><version>UBTU-22-255060</version><title>Ubuntu 22.04 LTS SSH server must be configured to use only FIPS-validated key exchange algorithms.</title><description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections provided by FIPS-validated cryptographic algorithms, information can be viewed and altered by unauthorized users without detection. 
 
The system will attempt to use the first algorithm presented by the client that matches the server list. Listing the values "strongest to weakest" is a method to ensure the use of the strongest algorithm available to secure the SSH 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000068</ident><fixtext fixref="F-64170r953411_fix">Configure the SSH server to use only FIPS-validated key exchange algorithms. 
 
Add or modify the following line in the "/etc/ssh/sshd_config" file: 
 
KexAlgorithms ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256 
 
Restart the SSH server for changes to take effect: 
 
     $ sudo systemctl restart sshd.service</fixtext><fix id="F-64170r953411_fix" /><check system="C-64262r953410_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the SSH server is configured to use only FIPS-validated key exchange algorithms by using the following command: 
 
     $ sudo /usr/sbin/sshd -dd 2&gt;&amp;1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH 'kexalgorithms' 
     /etc/ssh/sshd_config:KexAlgorithms ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256 
  
If "KexAlgorithms" does not contain only the algorithms "ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256" in exact order, is commented out, is missing, or conflicting results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260534"><title>SRG-OS-000125-GPOS-00065</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260534r958510_rule" weight="10.0" severity="medium"><version>UBTU-22-255065</version><title>Ubuntu 22.04 LTS must use strong authenticators in establishing nonlocal maintenance and diagnostic sessions.</title><description>&lt;VulnDiscussion&gt;Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000877</ident><fixtext fixref="F-64171r953414_fix">Configure Ubuntu 22.04 LTS to use strong authentication when establishing nonlocal maintenance and diagnostic sessions.   
  
Add or modify the following line to /etc/ssh/sshd_config:  
  
UsePAM yes 
 
Restart the SSH server for changes to take effect: 
 
     $ sudo systemctl restart sshd.service</fixtext><fix id="F-64171r953414_fix" /><check system="C-64263r953413_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS is configured to use strong authenticators in the establishment of nonlocal maintenance and diagnostic maintenance by using the following command: 
 
     $ sudo /usr/sbin/sshd -dd 2&gt;&amp;1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH 'usepam' 
     /etc/ssh/sshd_config:UsePAM yes 
 
If "UsePAM" is not set to "yes", is commented out, is missing, or conflicting results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260535"><title>SRG-OS-000023-GPOS-00006</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260535r958390_rule" weight="10.0" severity="medium"><version>UBTU-22-271010</version><title>Ubuntu 22.04 LTS must enable the graphical user logon banner to display the Standard Mandatory DOD Notice and Consent Banner before granting local 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 Ubuntu 22.04 LTS 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.  
  
The banner must be formatted in accordance with applicable DOD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:  
  
"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.  
  
By using this IS (which includes any device attached to this IS), you consent to the following conditions:  
  
-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.  
  
-At any time, the USG may inspect and seize data stored on this IS.  
  
-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.  
  
-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.  
  
-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."  
  
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:  
  
"I've read (literal ampersand) consent to terms in IS user agreem't."&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000048</ident><fixtext fixref="F-64172r953417_fix">Configure Ubuntu 22.04 LTS to display the Standard Mandatory DOD Notice and Consent Banner before granting access to the operating system via a graphical user logon. 
 
Add or modify the following line in the "/etc/gdm3/greeter.dconf-defaults" file: 
 
[org/gnome/login-screen]  
banner-message-enable=true  
  
Update GDM with the new configuration by using the following commands:  
  
     $ sudo dconf update  
     $ sudo systemctl restart gdm3</fixtext><fix id="F-64172r953417_fix" /><check system="C-64264r953416_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS is configured to display the Standard Mandatory DOD Notice and Consent Banner before granting access to the operating system via a graphical user logon by using the following command:  
  
Note: If no graphical user interface is installed, this requirement is not applicable. 
  
     $ grep -i banner-message-enable /etc/gdm3/greeter.dconf-defaults 
     banner-message-enable=true  
  
If the value for "banner-message-enable" is set to "false", the line is commented out, or no value is returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260536"><title>SRG-OS-000023-GPOS-00006</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260536r958390_rule" weight="10.0" severity="medium"><version>UBTU-22-271015</version><title>Ubuntu 22.04 LTS must display the Standard Mandatory DOD Notice and Consent Banner before granting local 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 Ubuntu 22.04 LTS 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.  
  
The banner must be formatted in accordance with applicable DOD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters:  
  
"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.  
  
By using this IS (which includes any device attached to this IS), you consent to the following conditions:  
  
-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.  
  
-At any time, the USG may inspect and seize data stored on this IS.  
  
-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.  
  
-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.  
  
-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."  
  
Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner:  
  
"I've read (literal ampersand) consent to terms in IS user agreem't."&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000048</ident><fixtext fixref="F-64173r953420_fix">Edit the "/etc/gdm3/greeter.dconf-defaults" file.  
  
Set the "banner-message-text" line to contain the appropriate banner message text as shown below:  
  
banner-message-text="You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." 
  
Update GDM with the new configuration by using the following commands:  
  
     $ sudo dconf update 
 
     $ sudo systemctl restart gdm3</fixtext><fix id="F-64173r953420_fix" /><check system="C-64265r953419_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS displays the Standard Mandatory DOD Notice and Consent Banner before granting access to the operating system via a graphical user logon with the command:  
  
Note: If no graphical user interface is installed, this requirement is not applicable. 
  
     $ grep -i banner-message-text /etc/gdm3/greeter.dconf-defaults 
  
banner-message-text="You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.\n\n-At any time, the USG may inspect and seize data stored on this IS.\n\n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.\n\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." 
  
If the banner-message-text is missing, commented out, or does not match the Standard Mandatory DOD Notice and Consent Banner exactly, this is a finding.</check-content></check></Rule></Group><Group id="V-260537"><title>SRG-OS-000028-GPOS-00009</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260537r958400_rule" weight="10.0" severity="medium"><version>UBTU-22-271020</version><title>Ubuntu 22.04 LTS must retain a user's session lock until that user reestablishes access using established identification and authentication procedures.</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.  
  
Regardless of where the session lock is determined and implemented, once invoked, a session lock of Ubuntu 22.04 LTS must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000056</ident><fixtext fixref="F-64174r953423_fix">Configure Ubuntu 22.04 LTS to allow a user to lock the current graphical user interface session.   
  
Set the "lock-enabled" setting to allow graphical user interface session locks by using the following command:   
  
     $ gsettings set org.gnome.desktop.screensaver lock-enabled true</fixtext><fix id="F-64174r953423_fix" /><check system="C-64266r953422_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS has a graphical user interface session lock enabled by using the following command: 
  
Note: If no graphical user interface is installed, this requirement is not applicable. 
  
     $ sudo gsettings get org.gnome.desktop.screensaver lock-enabled 
     true 
  
If "lock-enabled" is not set to "true", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260538"><title>SRG-OS-000029-GPOS-00010</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260538r958402_rule" weight="10.0" severity="medium"><version>UBTU-22-271025</version><title>Ubuntu 22.04 LTS must initiate a graphical session lock after 15 minutes of inactivity.</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.  
  
Regardless of where the session lock is determined and implemented, once invoked, a session lock of Ubuntu 22.04 LTS must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000057</ident><fixtext fixref="F-64175r953426_fix">Configure Ubuntu 22.04 LTS to lock the current graphical user interface session after 15 minutes of inactivity.   
  
Set the following settings to allow graphical user interface session lock to initiate after 15 minutes of inactivity:   
  
     $ gsettings set org.gnome.desktop.screensaver lock-enabled true 
 
     $ gsettings set org.gnome.desktop.screensaver lock-delay 0 
 
     $ gsettings set org.gnome.desktop.session idle-delay 900</fixtext><fix id="F-64175r953426_fix" /><check system="C-64267r953425_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS has a graphical user interface session lock configured to activate after 15 minutes of inactivity by using the following commands:   
  
Note: If no graphical user interface is installed, this requirement is not applicable. 
 
Get the following settings to verify the graphical user interface session is configured to lock the graphical user session after 15 minutes of inactivity:  
   
     $ gsettings get org.gnome.desktop.screensaver lock-enabled 
     true 
 
     $ gsettings get org.gnome.desktop.screensaver lock-delay 
     uint32 0 
 
     $ gsettings get org.gnome.desktop.session idle-delay 
     uint32 900 
 
If "lock-enabled" is not set to "true", is commented out, or is missing, this is a finding. 
 
If "lock-delay" is set to a value greater than "0", or if "idle-delay" is set to a value greater than "900", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260539"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260539r991589_rule" weight="10.0" severity="high"><version>UBTU-22-271030</version><title>Ubuntu 22.04 LTS must disable the x86 Ctrl-Alt-Delete key sequence if a graphical user interface is installed.</title><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 the graphical 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64176r953429_fix">Configure Ubuntu 22.04 LTS to disable the Ctrl-Alt-Delete sequence when using a graphical user interface. 
 
     $ gsettings set org.gnome.settings-daemon.plugins.media-keys logout [] 
 
Update the dconf settings: 
 
     # dconf update</fixtext><fix id="F-64176r953429_fix" /><check system="C-64268r953428_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS is not configured to reboot the system when Ctrl-Alt-Delete is pressed when using a graphical user interface by using the following command: 
 
Note: If no graphical user interface is installed, this requirement is not applicable. 
 
     $ gsettings get org.gnome.settings-daemon.plugins.media-keys logout 
     @as [] 
 
If the "logout" key is bound to an action, is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260540"><title>SRG-OS-000378-GPOS-00163</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260540r986276_rule" weight="10.0" severity="medium"><version>UBTU-22-291010</version><title>Ubuntu 22.04 LTS must disable automatic mounting of Universal Serial Bus (USB) mass storage driver.</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.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001958</ident><ident system="http://cyber.mil/cci">CCI-003959</ident><fixtext fixref="F-64177r953432_fix">Configure Ubuntu 22.04 LTS to disable using the USB storage kernel module.  
 
Create and/or append a custom file under "/etc/modprobe.d/" to contain the following: 
 
     $ sudo su -c "echo install usb-storage /bin/false &gt;&gt; /etc/modprobe.d/stig.conf" 
 
Configure Ubuntu 22.04 LTS to disable the ability to use USB mass storage devices. 
 
     $ sudo su -c "echo blacklist usb-storage &gt;&gt; /etc/modprobe.d/stig.conf"</fixtext><fix id="F-64177r953432_fix" /><check system="C-64269r953431_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS disables ability to load the USB storage kernel module by using the following command: 
 
     $ grep usb-storage /etc/modprobe.d/* | grep "/bin/false" 
     /etc/modprobe.d/stig.conf:install usb-storage /bin/false 
 
If the command does not return any output, or the line is commented out, this is a finding. 
 
Verify Ubuntu 22.04 LTS disables the ability to use USB mass storage device. 
 
     $ grep usb-storage /etc/modprobe.d/* | grep -i "blacklist" 
     /etc/modprobe.d/stig.conf:blacklist usb-storage 
 
If the command does not return any output, or the line is commented out, this is a finding.</check-content></check></Rule></Group><Group id="V-260541"><title>SRG-OS-000481-GPOS-00481</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260541r958358_rule" weight="10.0" severity="medium"><version>UBTU-22-291015</version><title>Ubuntu 22.04 LTS must disable all wireless network adapters.</title><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 operating system.  
  
This requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with an operating system. 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 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 operating system. 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 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002418</ident><fixtext fixref="F-64178r953435_fix">Disable all wireless network interfaces by using the following command: 
  
     $ sudo ifdown &lt;wireless_interface_name&gt;  
  
For each interface listed, find their respective module by using the following command:  
  
     $ basename $(readlink -f /sys/class/net/&lt;wireless_interface_name&gt;/device/driver)  
  
where &lt;wireless_interface_name&gt; must be substituted by the actual interface name.  
 
Create and/or append a custom file under "/etc/modprobe.d/" by using the following command: 
 
     $ sudo su -c "echo install &lt;module_name&gt; /bin/false &gt;&gt; /etc/modprobe.d/stig.conf" 
 
where &lt;module_name&gt; must be substituted by the actual module name. 
 
For each module from the system, execute the following command to remove it:  
  
     $ sudo modprobe -r &lt;module_name&gt;</fixtext><fix id="F-64178r953435_fix" /><check system="C-64270r953434_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that there are no wireless interfaces configured on the system by using the following command:  
 
Note: If the system does not have any physical wireless network radios, this requirement is not applicable.  
  
     $ cat /proc/net/wireless 
  
If any wireless interface names are listed under "Interface" and have not been documented and approved by the information system security officer (ISSO), this is a finding.</check-content></check></Rule></Group><Group id="V-260542"><title>SRG-OS-000109-GPOS-00056</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260542r1015006_rule" weight="10.0" severity="medium"><version>UBTU-22-411010</version><title>Ubuntu 22.04 LTS must prevent direct login into the root account.</title><description>&lt;VulnDiscussion&gt;To ensure individual accountability and prevent unauthorized access, organizational users must be individually identified and authenticated.  
  
A group authenticator is a generic account used by multiple individuals. Use of a group authenticator alone does not uniquely identify individual users. Examples of the group authenticator is the Unix OS "root" user account, the Windows "Administrator" account, the "sa" account, or a "helpdesk" account.  
  
For example, the Unix and Windows operating systems offer a "switch user" capability allowing users to authenticate with their individual credentials and, when needed, "switch" to the administrator role. This method provides for unique individual authentication prior to using a group authenticator.  
  
Users (and any processes acting on behalf of users) must be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization, which outlines specific user actions that can be performed on the operating system without identification or authentication.  
  
Requiring individuals to be authenticated with an individual authenticator prior to using a group authenticator allows for traceability of actions, as well as adding an additional level of protection of the actions that can be taken with group account knowledge.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004045</ident><ident system="http://cyber.mil/cci">CCI-000770</ident><fixtext fixref="F-64179r953438_fix">Configure Ubuntu 22.04 LTS to prevent direct logins to the root account by using the following command:  
  
     $ sudo passwd -l root</fixtext><fix id="F-64179r953438_fix" /><check system="C-64271r953437_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS prevents direct logins to the root account by using the following command:  
  
     $ sudo passwd -S root  
     root L 08/09/2022 0 99999 7 -1 
  
If the output does not contain "L" in the second field to indicate the account is locked, this is a finding.</check-content></check></Rule></Group><Group id="V-260543"><title>SRG-OS-000104-GPOS-00051</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260543r958482_rule" weight="10.0" severity="medium"><version>UBTU-22-411015</version><title>Ubuntu 22.04 LTS must uniquely identify interactive users.</title><description>&lt;VulnDiscussion&gt;To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.  
  
Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following:   
  
1. Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and  
  
2. Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.

Satisfies: SRG-OS-000104-GPOS-00051, SRG-OS-000121-GPOS-00062&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000764</ident><ident system="http://cyber.mil/cci">CCI-000804</ident><fixtext fixref="F-64180r953441_fix">Edit the file "/etc/passwd" and provide each interactive user account that has a duplicate UID with a unique UID.</fixtext><fix id="F-64180r953441_fix" /><check system="C-64272r953440_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS contains no duplicate User IDs (UIDs) for interactive users by using the following command:  
  
     $ awk -F ":" 'list[$3]++{print $1, $3}' /etc/passwd 
  
If output is produced and the accounts listed are interactive user accounts, this is a finding.</check-content></check></Rule></Group><Group id="V-260545"><title>SRG-OS-000075-GPOS-00043</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260545r1015007_rule" weight="10.0" severity="medium"><version>UBTU-22-411025</version><title>Ubuntu 22.04 LTS must enforce 24 hours/one day as the minimum password lifetime. Passwords for new users must have a 24 hours/one day minimum password lifetime restriction.</title><description>&lt;VulnDiscussion&gt;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, then the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004066</ident><ident system="http://cyber.mil/cci">CCI-000198</ident><fixtext fixref="F-64182r986279_fix">Configure Ubuntu 22.04 LTS to enforce a 24 hours/one day minimum password lifetime.  
  
Add or modify the following line in the "/etc/login.defs" file:  
  
PASS_MIN_DAYS    1</fixtext><fix id="F-64182r986279_fix" /><check system="C-64274r986278_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS enforces a 24 hours/one day minimum password lifetime for new user accounts by using the following command:  
  
     $ grep -i pass_min_days /etc/login.defs 
     PASS_MIN_DAYS    1  
  
If "PASS_MIN_DAYS" is less than "1", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260546"><title>SRG-OS-000076-GPOS-00044</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260546r1038967_rule" weight="10.0" severity="medium"><version>UBTU-22-411030</version><title>Ubuntu 22.04 LTS must enforce a 60-day maximum password lifetime restriction. Passwords for new users must have a 60-day maximum password lifetime restriction.</title><description>&lt;VulnDiscussion&gt;Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the operating system does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the operating system passwords 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004066</ident><ident system="http://cyber.mil/cci">CCI-000199</ident><fixtext fixref="F-64183r953450_fix">Configure Ubuntu 22.04 LTS to enforce a 60-day maximum password lifetime.  
  
Add or modify the following line in the "/etc/login.defs" file:  
  
PASS_MAX_DAYS    60</fixtext><fix id="F-64183r953450_fix" /><check system="C-64275r953449_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS enforces a 60-day maximum password lifetime for new user accounts by using the following command: 
  
     $ grep -i pass_max_days /etc/login.defs 
     PASS_MAX_DAYS    60  
 
If "PASS_MAX_DAYS" is less than "60", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260547"><title>SRG-OS-000118-GPOS-00060</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260547r1015009_rule" weight="10.0" severity="medium"><version>UBTU-22-411035</version><title>Ubuntu 22.04 LTS must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.</title><description>&lt;VulnDiscussion&gt;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.  
  
Operating systems need to track periods of inactivity and disable application identifiers after 35 days of inactivity.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-003627</ident><ident system="http://cyber.mil/cci">CCI-003628</ident><ident system="http://cyber.mil/cci">CCI-000795</ident><fixtext fixref="F-64184r953453_fix">Configure Ubuntu 22.04 LTS to disable account identifiers after 35 days of inactivity after the password expiration.   
  
Run the following command to change the configuration for adduser:  
  
     $ sudo useradd -D -f 35 
  
Note: DOD recommendation is 35 days, but a lower value is acceptable. The value "0" will disable the account immediately after the password expires.</fixtext><fix id="F-64184r953453_fix" /><check system="C-64276r953452_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the account identifiers (individuals, groups, roles, and devices) are disabled after 35 days of inactivity by using the following command:  
  
Check the account inactivity value by performing the following command:  
  
     $ grep INACTIVE /etc/default/useradd  
     INACTIVE=35  
  
If "INACTIVE" is set to "-1" or is not set to "35", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260548"><title>SRG-OS-000002-GPOS-00002</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260548r958364_rule" weight="10.0" severity="medium"><version>UBTU-22-411040</version><title>Ubuntu 22.04 LTS must automatically expire temporary accounts within 72 hours.</title><description>&lt;VulnDiscussion&gt;Temporary accounts are privileged or nonprivileged accounts established during pressing circumstances, such as new software or hardware configuration or an incident response, where the need for prompt account activation requires bypassing normal account authorization procedures. If any inactive temporary accounts are left enabled on the system and are not either manually removed or automatically expired within 72 hours, the security posture of the system will be degraded and exposed to exploitation by unauthorized users or insider threat actors. 
 
Temporary accounts are different from emergency accounts. Emergency accounts, also known as "last resort" or "break glass" accounts, are local logon accounts enabled on the system for emergency use by authorized system administrators to manage a system when standard logon methods are failing or not available. Emergency accounts are not subject to manual removal or scheduled expiration requirements. 
 
The automatic expiration of temporary accounts may be extended as needed by the circumstances, but it must not be extended indefinitely. A documented permanent account should be established for privileged users who need long-term maintenance accounts.

Satisfies: SRG-OS-000002-GPOS-00002, SRG-OS-000123-GPOS-00064&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000016</ident><ident system="http://cyber.mil/cci">CCI-001682</ident><fixtext fixref="F-64185r953456_fix">Configure Ubuntu 22.04 LTS to expire temporary accounts after 72 hours by using the following command: 
 
     $ sudo chage -E $(date -d +3days +%Y-%m-%d) &lt;temporary_account_name&gt;</fixtext><fix id="F-64185r953456_fix" /><check system="C-64277r953455_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify temporary accounts have been provisioned with an expiration date of 72 hours by using the following command: 
 
     $ sudo chage -l &lt;temporary_account_name&gt; | grep -E '(Password|Account) expires' 
     Password expires     : Apr 1, 2024  
     Account expires        : Apr 1, 2024  
 
Verify each of these accounts has an expiration date set within 72 hours. 
 
If any temporary accounts have no expiration date set or do not expire within 72 hours, this is a finding.</check-content></check></Rule></Group><Group id="V-260549"><title>SRG-OS-000021-GPOS-00005</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260549r958388_rule" weight="10.0" severity="low"><version>UBTU-22-411045</version><title>Ubuntu 22.04 LTS must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts have been made.</title><description>&lt;VulnDiscussion&gt;By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account.

Satisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000044</ident><ident system="http://cyber.mil/cci">CCI-002238</ident><fixtext fixref="F-64186r953459_fix">Configure Ubuntu 22.04 LTS to utilize the "pam_faillock" module.  
 
Add or modify the following lines in the "/etc/pam.d/common-auth" file, below the "auth" definition for "pam_unix.so":  
 
auth     [default=die]  pam_faillock.so authfail 
auth     sufficient          pam_faillock.so authsucc 
 
Configure the "pam_faillock" module to use the following options. 
 
Add or modify the following lines in the "/etc/security/faillock.conf" file: 
 
audit 
silent 
deny = 3 
fail_interval = 900 
unlock_time = 0</fixtext><fix id="F-64186r953459_fix" /><check system="C-64278r953458_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that Ubuntu 22.04 LTS utilizes the "pam_faillock" module by using the following command: 
 
     $ grep faillock /etc/pam.d/common-auth 
 
auth     [default=die]  pam_faillock.so authfail 
auth     sufficient     pam_faillock.so authsucc 
 
If the "pam_faillock.so" module is not present in the "/etc/pam.d/common-auth" file, this is a finding. 
 
Verify the "pam_faillock" module is configured to use the following options: 
 
     $ sudo grep -Ew 'silent|audit|deny|fail_interval|unlock_time' /etc/security/faillock.conf 
     audit 
     silent 
     deny = 3 
     fail_interval = 900 
     unlock_time = 0 
 
If "audit" is commented out, or is missing, this is a finding.

If "silent" is commented out, or is missing, this is a finding.

If "deny" is set to a value greater than "3", is commented out, or is missing, this is a finding.
 
If "fail_interval" is set to a value greater than "900", is commented out, or is missing, this is a finding.
 
If "unlock_time" is not set to "0", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260550"><title>SRG-OS-000480-GPOS-00226</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260550r991588_rule" weight="10.0" severity="low"><version>UBTU-22-412010</version><title>Ubuntu 22.04 LTS must enforce a delay of at least four seconds between logon prompts following a failed logon attempt.</title><description>&lt;VulnDiscussion&gt;Limiting the number of logon attempts over a certain time interval reduces the chances that an unauthorized user may gain access to an 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64187r953462_fix">Configure Ubuntu 22.04 LTS to enforce a delay of at least four seconds between logon prompts following a failed logon attempt. 
 
Add or modify the following line in the "/etc/pam.d/common-auth" file: 
 
auth     required     pam_faildelay.so     delay=4000000</fixtext><fix id="F-64187r953462_fix" /><check system="C-64279r953461_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS enforces a delay of at least four seconds between logon prompts following a failed logon attempt by using the following command:  
  
     $ grep pam_faildelay /etc/pam.d/common-auth 
     auth     required     pam_faildelay.so     delay=4000000  
  
If "delay" is not set to "4000000" or greater, the line is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260552"><title>SRG-OS-000027-GPOS-00008</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260552r958398_rule" weight="10.0" severity="low"><version>UBTU-22-412020</version><title>Ubuntu 22.04 LTS must limit the number of concurrent sessions to ten for all accounts and/or account types.</title><description>&lt;VulnDiscussion&gt;Ubuntu 22.04 LTS 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 denial-of-service (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 upon mission needs and the operational environment for each 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000054</ident><fixtext fixref="F-64189r953468_fix">Configure Ubuntu 22.04 LTS to limit the number of concurrent sessions to 10 for all accounts and/or account types.  
  
Add or modify the following line at the top of the "/etc/security/limits.conf" file:  
  
* hard maxlogins 10</fixtext><fix id="F-64189r953468_fix" /><check system="C-64281r953467_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS limits the number of concurrent sessions to 10 for all accounts and/or account types by using the following command:  
  
     $ sudo grep -r -s '^[^#].*maxlogins' /etc/security/limits.conf /etc/security/limits.d/*.conf 
     /etc/security/limits.conf:* hard maxlogins 10 
 
If "maxlogins" does not have a value of "10" or less, is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260553"><title>SRG-OS-000030-GPOS-00011</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260553r1015010_rule" weight="10.0" severity="medium"><version>UBTU-22-412025</version><title>Ubuntu 22.04 LTS must allow users to directly initiate a session lock for all connection types.</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, Ubuntu 22.04 LTS need to provide users with the ability to manually invoke a session lock so users may secure their session if they need to temporarily vacate the immediate physical vicinity.

Satisfies: SRG-OS-000030-GPOS-00011, SRG-OS-000031-GPOS-00012&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000057</ident><ident system="http://cyber.mil/cci">CCI-000060</ident><ident system="http://cyber.mil/cci">CCI-000058</ident><fixtext fixref="F-64190r953471_fix">Install the "vlock" package by using the following command:  
  
     $ sudo apt-get install vlock</fixtext><fix id="F-64190r953471_fix" /><check system="C-64282r953470_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS has the "vlock" package installed by using the following command:  
  
     $ dpkg -l | grep vlock 
     ii     vlock     2.2.2-10     amd64     Virtual Console locking program 
  
If "vlock" is not installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260554"><title>SRG-OS-000279-GPOS-00109</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260554r958636_rule" weight="10.0" severity="medium"><version>UBTU-22-412030</version><title>Ubuntu 22.04 LTS must automatically exit interactive command shell user sessions after 15 minutes of inactivity.</title><description>&lt;VulnDiscussion&gt;Terminating an idle interactive command shell user session within a short time period reduces the window of opportunity for unauthorized personnel to take control of it when left unattended in a virtual terminal or physical console.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002361</ident><fixtext fixref="F-64191r953474_fix">Configure Ubuntu 22.04 LTS to exit interactive command shell user sessions after 15 minutes of inactivity. 
 
Create and/or append a custom file under "/etc/profile.d/" by using the following command: 
 
     $ sudo su -c "echo TMOUT=900 &gt;&gt; /etc/profile.d/99-terminal_tmout.sh" 
  
This will set a timeout value of 15 minutes for all future sessions.  
  
To set the timeout for the current sessions, execute the following command over the terminal session:  
  
     $ export TMOUT=900</fixtext><fix id="F-64191r953474_fix" /><check system="C-64283r953473_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS is configured to automatically exit interactive command shell user sessions after 15 minutes of inactivity or less by using the following command: 
  
     $ sudo grep -E "\bTMOUT=[0-9]+" /etc/bash.bashrc /etc/profile.d/* 
     /etc/profile.d/99-terminal_tmout.sh:TMOUT=900 
  
If "TMOUT" is not set to "900" or less, is set to "0", is commented out, or missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260555"><title>SRG-OS-000480-GPOS-00228</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260555r991590_rule" weight="10.0" severity="medium"><version>UBTU-22-412035</version><title>Ubuntu 22.04 LTS default filesystem permissions must be defined in such a way that all authenticated users can read and modify only their own files.</title><description>&lt;VulnDiscussion&gt;Setting the most restrictive default permissions ensures newly created accounts do not have unnecessary 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64192r953477_fix">Configure Ubuntu 22.04 LTS to define the default permissions for all authenticated users in such a way that the user can read and modify only their own files.  
 
Add or modify the following line in the "/etc/login.defs" file:  
 
UMASK 077</fixtext><fix id="F-64192r953477_fix" /><check system="C-64284r953476_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS defines default permissions for all authenticated users in such a way that the user can read and modify only their own files by using the following command: 
  
     $ grep -i '^\s*umask' /etc/login.defs  
     UMASK 077  
  
If the "UMASK" variable is set to "000", this is a finding with the severity raised to a CAT I.

If "UMASK" is not set to "077", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260556"><title>SRG-OS-000312-GPOS-00124</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260556r958702_rule" weight="10.0" severity="medium"><version>UBTU-22-431010</version><title>Ubuntu 22.04 LTS must have the "apparmor" package installed.</title><description>&lt;VulnDiscussion&gt;Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system level.  
  
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.  
  
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).

Satisfies: SRG-OS-000312-GPOS-00124, SRG-OS-000368-GPOS-00154, 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001764</ident><ident system="http://cyber.mil/cci">CCI-001774</ident><ident system="http://cyber.mil/cci">CCI-002165</ident><fixtext fixref="F-64193r953480_fix">Install the "appArmor" package by using the following command:  
  
     $ sudo apt-get install apparmor</fixtext><fix id="F-64193r953480_fix" /><check system="C-64285r953479_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS has the "apparmor" package installed by using the following command: 
  
     $ dpkg -l | grep apparmor  
     ii     apparmor     3.0.4-2ubuntu2.3     amd64     user-space parser utility for AppArmor 
 
If the "apparmor" package is not installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260557"><title>SRG-OS-000368-GPOS-00154</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260557r958804_rule" weight="10.0" severity="medium"><version>UBTU-22-431015</version><title>Ubuntu 22.04 LTS must be configured to use AppArmor.</title><description>&lt;VulnDiscussion&gt;Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system level.  
  
Some of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline.  
  
Methods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).

Satisfies: SRG-OS-000368-GPOS-00154, SRG-OS-000370-GPOS-00155, SRG-OS-000324-GPOS-00125&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001764</ident><ident system="http://cyber.mil/cci">CCI-001774</ident><ident system="http://cyber.mil/cci">CCI-002235</ident><fixtext fixref="F-64194r953483_fix">Enable and start "apparmor.service" by using the following command: 
  
     $ sudo systemctl enable apparmor.service --now 
  
Note: AppArmor must have properly configured profiles for applications and home directories. All configurations will be based on the actual system setup and organization and normally are on a per role basis. See the AppArmor documentation for more information on configuring profiles.</fixtext><fix id="F-64194r953483_fix" /><check system="C-64286r953482_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS AppArmor is active by using the following commands:  
 
     $ systemctl is-enabled apparmor.service 
     enabled  
 
     $ systemctl is-active apparmor.service 
     active   
 
If "apparmor.service" is not enabled and active, this is a finding. 
 
Check if AppArmor profiles are loaded and enforced by using the following command: 
 
     $ sudo apparmor_status | grep -i profile 
     32 profiles are loaded. 
     32 profiles are in enforce mode. 
     0 profiles are in complain mode. 
     0 profiles are in kill mode. 
     0 profiles are in unconfined mode. 
     2 processes have profiles defined. 
     0 processes are unconfined but have a profile defined. 
 
If no profiles are loaded and enforced, this is a finding.</check-content></check></Rule></Group><Group id="V-260558"><title>SRG-OS-000373-GPOS-00156</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260558r1050789_rule" weight="10.0" severity="medium"><version>UBTU-22-432010</version><title>Ubuntu 22.04 LTS must require users to reauthenticate for privilege escalation or when changing roles.</title><description>&lt;VulnDiscussion&gt;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.

Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004895</ident><ident system="http://cyber.mil/cci">CCI-002038</ident><fixtext fixref="F-64195r953486_fix">Remove any occurrence of "NOPASSWD" or "!authenticate" found in "/etc/sudoers" file or files in the "/etc/sudoers.d" directory.</fixtext><fix id="F-64195r953486_fix" /><check system="C-64287r953485_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the "/etc/sudoers" file has no occurrences of "NOPASSWD" or "!authenticate" by using the following command:  
  
     $ sudo grep -Ei '(nopasswd|!authenticate)' /etc/sudoers /etc/sudoers.d/* 
  
If any occurrences of "NOPASSWD" or "!authenticate" return from the command, this is a finding.</check-content></check></Rule></Group><Group id="V-260559"><title>SRG-OS-000134-GPOS-00068</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260559r958518_rule" weight="10.0" severity="high"><version>UBTU-22-432015</version><title>Ubuntu 22.04 LTS must ensure only users who need access to security functions are part of sudo group.</title><description>&lt;VulnDiscussion&gt;An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions.  
  
Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Operating systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For nonkernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code.  
  
Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of memory space and libraries.   
  
Ubuntu 22.04 LTS restricts access to security functions through the use of access control mechanisms and by implementing least privilege capabilities.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001084</ident><fixtext fixref="F-64196r953489_fix">Configure the sudo group with only members requiring access to security functions.  
  
To remove a user from the sudo group, run:  
  
     $ sudo gpasswd -d &lt;username&gt; sudo</fixtext><fix id="F-64196r953489_fix" /><check system="C-64288r953488_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the sudo group has only members who require access to security functions by using the following command:   
  
     $ grep sudo /etc/group  
     sudo:x:27:&lt;username&gt; 
  
If the sudo group contains users not needing access to security functions, this is a finding.</check-content></check></Rule></Group><Group id="V-260560"><title>SRG-OS-000069-GPOS-00037</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260560r1015012_rule" weight="10.0" severity="medium"><version>UBTU-22-611010</version><title>Ubuntu 22.04 LTS must enforce password complexity by requiring 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.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004066</ident><ident system="http://cyber.mil/cci">CCI-000192</ident><fixtext fixref="F-64197r953492_fix">Configure Ubuntu 22.04 LTS to enforce password complexity by requiring that at least one uppercase character be used.  
 
Add or modify the following line in the "/etc/security/pwquality.conf" file: 
  
ucredit = -1</fixtext><fix id="F-64197r953492_fix" /><check system="C-64289r953491_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS enforces password complexity by requiring at least one uppercase character be used by using the following command:  
  
     $ grep -i ucredit /etc/security/pwquality.conf 
     ucredit = -1  
  
If "ucredit" is greater than "-1", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260561"><title>SRG-OS-000070-GPOS-00038</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260561r1015013_rule" weight="10.0" severity="medium"><version>UBTU-22-611015</version><title>Ubuntu 22.04 LTS must enforce password complexity by requiring at least one lowercase 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.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004066</ident><ident system="http://cyber.mil/cci">CCI-000193</ident><fixtext fixref="F-64198r953495_fix">Configure Ubuntu 22.04 LTS to enforce password complexity by requiring that at least one lowercase character be used.  
 
Add or modify the following line in the "/etc/security/pwquality.conf" file: 
 
lcredit = -1</fixtext><fix id="F-64198r953495_fix" /><check system="C-64290r953494_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS enforces password complexity by requiring that at least one lowercase character be used by using the following command:  
  
     $ grep -i lcredit /etc/security/pwquality.conf 
     lcredit = -1  
  
If "lcredit" is greater than "-1", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260562"><title>SRG-OS-000071-GPOS-00039</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260562r1015014_rule" weight="10.0" severity="medium"><version>UBTU-22-611020</version><title>Ubuntu 22.04 LTS must enforce password complexity by requiring that at least one numeric 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.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004066</ident><ident system="http://cyber.mil/cci">CCI-000194</ident><fixtext fixref="F-64199r953498_fix">Configure Ubuntu 22.04 LTS to enforce password complexity by requiring that at least one numeric character be used.  
  
Add or modify the following line in the "/etc/security/pwquality.conf" file: 
 
dcredit = -1</fixtext><fix id="F-64199r953498_fix" /><check system="C-64291r953497_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS enforces password complexity by requiring that at least one numeric character be used by using the following command: 
 
     $ grep -i dcredit /etc/security/pwquality.conf 
     dcredit = -1  
  
If "dcredit" is greater than "-1", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260563"><title>SRG-OS-000266-GPOS-00101</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260563r1015015_rule" weight="10.0" severity="medium"><version>UBTU-22-611025</version><title>Ubuntu 22.04 LTS must enforce password complexity by requiring that at least one special 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 in determining 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.  
  
Special characters are those characters that are not alphanumeric. Examples include: ~ ! @ # $ % ^ *.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004066</ident><ident system="http://cyber.mil/cci">CCI-001619</ident><fixtext fixref="F-64200r953501_fix">Configure Ubuntu 22.04 LTS to enforce password complexity by requiring that at least one special character be used.   
  
Add or modify the following line in the "/etc/security/pwquality.conf" file: 
 
ocredit = -1</fixtext><fix id="F-64200r953501_fix" /><check system="C-64292r953500_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS enforces password complexity by requiring that at least one special character be used by using the following command: 
  
     $ grep -i ocredit /etc/security/pwquality.conf 
     ocredit = -1  
  
If "ocredit" is greater than "-1", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260564"><title>SRG-OS-000480-GPOS-00225</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260564r991587_rule" weight="10.0" severity="medium"><version>UBTU-22-611030</version><title>Ubuntu 22.04 LTS must prevent the use of dictionary words for passwords.</title><description>&lt;VulnDiscussion&gt;If Ubuntu 22.04 LTS allows the user to select passwords based on dictionary words, then this increases the chances of password compromise by increasing the opportunity for successful guesses and brute-force attacks.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64201r953504_fix">Configure Ubuntu 22.04 LTS to prevent the use of dictionary words for passwords. 
  
Add or modify the following line in the "/etc/security/pwquality.conf" file: 
  
dictcheck = 1</fixtext><fix id="F-64201r953504_fix" /><check system="C-64293r953503_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS prevents the use of dictionary words for passwords by using the following command: 
 
     $ grep -i dictcheck /etc/security/pwquality.conf 
     dictcheck = 1  
  
If "dictcheck" is not set to "1", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260565"><title>SRG-OS-000078-GPOS-00046</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260565r1015016_rule" weight="10.0" severity="medium"><version>UBTU-22-611035</version><title>Ubuntu 22.04 LTS must enforce a minimum 15-character password length.</title><description>&lt;VulnDiscussion&gt;The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.  
  
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004066</ident><ident system="http://cyber.mil/cci">CCI-000205</ident><fixtext fixref="F-64202r953507_fix">Configure Ubuntu 22.04 LTS to enforce a minimum 15-character password length.  
  
Add or modify the following line in the "/etc/security/pwquality.conf" file: 
 
minlen = 15</fixtext><fix id="F-64202r953507_fix" /><check system="C-64294r953506_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the pwquality configuration file enforces a minimum 15-character password length by using the following command: 
 
     $ grep -i minlen /etc/security/pwquality.conf 
     minlen = 15 
 
If "minlen" is not "15" or higher, is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260566"><title>SRG-OS-000072-GPOS-00040</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260566r1015017_rule" weight="10.0" severity="medium"><version>UBTU-22-611040</version><title>Ubuntu 22.04 LTS must require the change of at least eight characters when passwords are changed.</title><description>&lt;VulnDiscussion&gt;If the operating system allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks.  
  
The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different.  
  
If the password length is an odd number then number of changed characters must be rounded up. For example, a password length of 15 characters must require the change of at least eight characters.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004066</ident><ident system="http://cyber.mil/cci">CCI-000195</ident><fixtext fixref="F-64203r953510_fix">Configure Ubuntu 22.04 LTS to require the change of at least eight characters when passwords are changed.  
  
Add or modify the following line in the "/etc/security/pwquality.conf" file: 
 
difok = 8</fixtext><fix id="F-64203r953510_fix" /><check system="C-64295r953509_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS requires the change of at least eight characters when passwords are changed by using the following command: 
  
     $ grep -i difok /etc/security/pwquality.conf 
     difok = 8  
  
If "difok" is less than "8", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260567"><title>SRG-OS-000480-GPOS-00225</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260567r991587_rule" weight="10.0" severity="medium"><version>UBTU-22-611045</version><title>Ubuntu 22.04 LTS must be configured so that when passwords are changed or new passwords are established, pwquality must 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. "pwquality" enforces complex password construction configuration and has the ability to limit brute-force attacks 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64204r953513_fix">Configure Ubuntu 22.04 LTS to enforce password complexity rules. 
  
Add or modify the following line in the "/etc/security/pwquality.conf" file: 
  
enforcing = 1  
  
Add or modify the following line in the "/etc/pam.d/common-password" file: 
  
password requisite pam_pwquality.so retry=3  
  
Note: The value of "retry" should be between "1" and "3".</fixtext><fix id="F-64204r953513_fix" /><check system="C-64296r953512_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS enforces password complexity rules by using the following command:   
 
     $ grep -i enforcing /etc/security/pwquality.conf  
     enforcing = 1  
  
If "enforcing" is not "1", is commented out, or is missing, this is a finding.  
  
Check for the use of "pwquality" by using the following command:  
  
     $ cat /etc/pam.d/common-password | grep requisite | grep pam_pwquality 
      password     requisite     pam_pwquality.so retry=3  
  
If "retry" is set to "0" or is greater than "3", or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260569"><title>SRG-OS-000073-GPOS-00041</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260569r1044767_rule" weight="10.0" severity="medium"><version>UBTU-22-611055</version><title>Ubuntu 22.04 LTS must store only encrypted representations of passwords.</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 consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004062</ident><ident system="http://cyber.mil/cci">CCI-000196</ident><fixtext fixref="F-64206r1044766_fix">Configure Ubuntu 22.04 LTS to store encrypted representations of passwords. 
 
Add or modify the following line in the "/etc/pam.d/common-password" file: 
 
password [success=1 default=ignore] pam_unix.so obscure sha512 shadow remember=5 rounds=100000</fixtext><fix id="F-64206r1044766_fix" /><check system="C-64298r1044765_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the Ubuntu operating stores only encrypted representations of passwords with the following command: 
 
     $ grep pam_unix.so /etc/pam.d/common-password 
     password [success=1 default=ignore] pam_unix.so obscure sha512 shadow remember=5 rounds=100000
 
If "sha512" is missing from the "pam_unix.so" line, this is a finding.</check-content></check></Rule></Group><Group id="V-260570"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260570r991589_rule" weight="10.0" severity="high"><version>UBTU-22-611060</version><title>Ubuntu 22.04 LTS must not allow 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 must 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64207r953522_fix">Remove any instances of the "nullok" option in "/etc/pam.d/common-password" to prevent logons with empty passwords.</fixtext><fix id="F-64207r953522_fix" /><check system="C-64299r953521_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>To verify that null passwords cannot be used, run the following command:  
 
     $ grep nullok /etc/pam.d/common-password 
 
If this produces any output, this is a finding.</check-content></check></Rule></Group><Group id="V-260571"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260571r991589_rule" weight="10.0" severity="high"><version>UBTU-22-611065</version><title>Ubuntu 22.04 LTS 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 must 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64208r953525_fix">Configure all accounts on the system to have a password or lock the account by using the following commands: 
 
Set the account password: 
 
     $ sudo passwd &lt;username&gt; 
 
Or lock the account: 
 
     $ sudo passwd -l &lt;username&gt;</fixtext><fix id="F-64208r953525_fix" /><check system="C-64300r953524_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify all accounts on the system to have a password by using 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-260572"><title>SRG-OS-000120-GPOS-00061</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260572r971535_rule" weight="10.0" severity="medium"><version>UBTU-22-611070</version><title>Ubuntu 22.04 LTS must encrypt all stored passwords with a FIPS 140-3-approved cryptographic hashing algorithm.</title><description>&lt;VulnDiscussion&gt;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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000803</ident><fixtext fixref="F-64209r953528_fix">Configure Ubuntu 22.04 LTS to encrypt all stored passwords.   
  
Add or modify the following line in the "/etc/login.defs" file: 
  
ENCRYPT_METHOD SHA512</fixtext><fix id="F-64209r953528_fix" /><check system="C-64301r953527_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the shadow password suite configuration is set to encrypt passwords with a FIPS 140-3 approved cryptographic hashing algorithm by using the following command:  
  
     $ grep -i '^\s*encrypt_method' /etc/login.defs 
     ENCRYPT_METHOD SHA512  
  
If "ENCRYPT_METHOD" does not equal SHA512 or greater, is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260573"><title>SRG-OS-000375-GPOS-00160</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260573r1015019_rule" weight="10.0" severity="medium"><version>UBTU-22-612010</version><title>Ubuntu 22.04 LTS must implement multifactor authentication for remote access to privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access.</title><description>&lt;VulnDiscussion&gt;Using an authentication device, such as a CAC or token separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.  
  
Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government personal identity verification card and the DOD common access card.  
  
A privileged account is defined as an information system account with authorizations of a privileged user.  
  
Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-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).

Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000765</ident><ident system="http://cyber.mil/cci">CCI-000766</ident><ident system="http://cyber.mil/cci">CCI-004046</ident><ident system="http://cyber.mil/cci">CCI-004047</ident><ident system="http://cyber.mil/cci">CCI-000767</ident><ident system="http://cyber.mil/cci">CCI-000768</ident><ident system="http://cyber.mil/cci">CCI-001948</ident><fixtext fixref="F-64210r953531_fix">Install the "libpam-pkcs11" package by using the following command: 
 
     $ sudo apt-get install libpam-pkcs11</fixtext><fix id="F-64210r953531_fix" /><check system="C-64302r953530_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS has the packages required for multifactor authentication installed by using the following command:  
 
     $ dpkg -l | grep libpam-pkcs11 
     ii     libpam-pkcs11     0.6.11-4build2     amd64     Fully featured PAM module for using PKCS#11 smart cards 
 
If the "libpam-pkcs11" package is not installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260574"><title>SRG-OS-000376-GPOS-00161</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260574r958816_rule" weight="10.0" severity="medium"><version>UBTU-22-612015</version><title>Ubuntu 22.04 LTS must accept personal identity verification (PIV) credentials.</title><description>&lt;VulnDiscussion&gt;The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access.  
  
DOD has mandated the use of the common access card (CAC) to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001953</ident><fixtext fixref="F-64211r953534_fix">Install the "opensc-pkcs11" package by using the following command:  
  
     $ sudo apt-get install opensc-pkcs11</fixtext><fix id="F-64211r953534_fix" /><check system="C-64303r953533_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the "opensc-pcks11" package is installed on the system by using the following command:  
  
     $ dpkg -l | grep opensc-pkcs11 
     ii     opensc-pkcs11:amd64     0.22.0-1Ubuntu2     amd64     Smart card utilities with support for PKCS#15 compatible cards  
  
If the "opensc-pcks11" package is not installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260575"><title>SRG-OS-000105-GPOS-00052</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260575r1044770_rule" weight="10.0" severity="medium"><version>UBTU-22-612020</version><title>Ubuntu 22.04 LTS must implement smart card logins for multifactor authentication for local and network access to privileged and nonprivileged accounts.</title><description>&lt;VulnDiscussion&gt;Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased.  
  
Multifactor authentication requires using two or more factors to achieve authentication.  
  
Factors include:   
1) Something a user knows (e.g., password/PIN);  
2) Something a user has (e.g., cryptographic identification device, token); and  
3) Something a user is (e.g., biometric).  
  
A privileged account is defined as an information system account with authorizations of a privileged user.  
  
Network access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the internet).  
  
The DOD common access card (CAC) with DOD-approved PKI is an example of multifactor authentication.

Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000765</ident><ident system="http://cyber.mil/cci">CCI-000766</ident><ident system="http://cyber.mil/cci">CCI-004047</ident><ident system="http://cyber.mil/cci">CCI-000767</ident><ident system="http://cyber.mil/cci">CCI-000768</ident><fixtext fixref="F-64212r1044769_fix">Configure Ubuntu 22.04 LTS to use multifactor authentication for access to accounts.  
  
Add or modify the following line in the "/etc/pam.d/common-auth" file: 
  
auth     [success=3 default=ignore]     pam_pkcs11.so  
  
Add or modify the following line in the "/etc/ssh/sshd_config" file: 
 
PubkeyAuthentication yes</fixtext><fix id="F-64212r1044769_fix" /><check system="C-64304r1044768_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the "pam_pkcs11.so" module is configured by using the following command: 
 
     $ grep -i pam_pkcs11.so /etc/pam.d/common-auth 
     auth     [success=3 default=ignore]     pam_pkcs11.so  
 
If "pam_pkcs11.so" is commented out or is missing, this is a finding. 
 
Verify the sshd daemon allows public key authentication by using the following command: 
  
     $ sudo /usr/sbin/sshd -dd 2&gt;&amp;1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH 'pubkeyauthentication' 
     /etc/ssh/sshd_config:PubkeyAuthentication yes 
 
If "PubkeyAuthentication" is not set to "yes" or is commented out or missing, or if conflicting results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260576"><title>SRG-OS-000377-GPOS-00162</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260576r958818_rule" weight="10.0" severity="medium"><version>UBTU-22-612025</version><title>Ubuntu 22.04 LTS must electronically verify personal identity verification (PIV) credentials.</title><description>&lt;VulnDiscussion&gt;The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access.  
  
DOD has mandated the use of the common access card (CAC) to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001954</ident><fixtext fixref="F-64213r953540_fix">Configure Ubuntu 22.04 LTS to do certificate status checking for multifactor authentication.  
 
Add or modify all "cert_policy" lines in the "/etc/pam_pkcs11/pam_pkcs11.conf" file with the following: 
 
ocsp_on</fixtext><fix id="F-64213r953540_fix" /><check system="C-64305r953539_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS electronically verifies PIV credentials via certificate status checking by using the following command:  
  
     $ sudo grep use_pkcs11_module /etc/pam_pkcs11/pam_pkcs11.conf | awk '/pkcs11_module opensc {/,/}/' /etc/pam_pkcs11/pam_pkcs11.conf | grep cert_policy | grep ocsp_on 
     cert_policy = ca,signature,ocsp_on;  
  
If every returned "cert_policy" line is not set to "ocsp_on", the line is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260577"><title>SRG-OS-000066-GPOS-00034</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260577r986294_rule" weight="10.0" severity="medium"><version>UBTU-22-612030</version><title>Ubuntu 22.04 LTS, 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.  
  
When there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a certification authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA.  
  
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.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000185</ident><ident system="http://cyber.mil/cci">CCI-004909</ident><fixtext fixref="F-64214r953543_fix">Configure Ubuntu 22.04 LTS, for PKI-based authentication, to validate certificates by constructing a certification path to an accepted trust anchor.  
  
Add or modify all "cert_policy" lines in the "/etc/pam_pkcs11/pam_pkcs11.conf" file with the following: 
 
cert_policy = ca,signature,ocsp_on;  
  
Note: If the system is missing an "/etc/pam_pkcs11/" directory and an "/etc/pam_pkcs11/pam_pkcs11.conf", find an example to copy into place and modify accordingly at "/usr/share/doc/libpam-pkcs11/examples/pam_pkcs11.conf.example.gz".</fixtext><fix id="F-64214r953543_fix" /><check system="C-64306r953542_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS, for PKI-based authentication, has valid certificates by constructing a certification path to an accepted trust anchor.  
  
Determine which pkcs11 module is being used via the "use_pkcs11_module" in "/etc/pam_pkcs11/pam_pkcs11.conf" and then ensure "ca" is enabled in "cert_policy" by using the following command:  
   
     $ sudo grep use_pkcs11_module /etc/pam_pkcs11/pam_pkcs11.conf | awk '/pkcs11_module opensc {/,/}/' /etc/pam_pkcs11/pam_pkcs11.conf | grep cert_policy | grep ca   
     cert_policy = ca,signature,ocsp_on;  
  
If "cert_policy" is not set to "ca", the line is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260578"><title>SRG-OS-000384-GPOS-00167</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260578r1015021_rule" weight="10.0" severity="medium"><version>UBTU-22-612035</version><title>Ubuntu 22.04 LTS for PKI-based authentication, must implement a local cache of revocation data in case of the inability to access revocation information via the network.</title><description>&lt;VulnDiscussion&gt;Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-004068</ident><ident system="http://cyber.mil/cci">CCI-001991</ident><fixtext fixref="F-64215r953546_fix">Configure Ubuntu 22.04 LTS, for PKI-based authentication, to use local revocation data when unable to access the network to obtain it remotely.  
  
Add or update the "cert_policy" option in "/etc/pam_pkcs11/pam_pkcs11.conf" to include "crl_auto" or "crl_offline".  
  
cert_policy = ca,signature,ocsp_on, crl_auto;  
  
If the system is missing an "/etc/pam_pkcs11/" directory and an "/etc/pam_pkcs11/pam_pkcs11.conf", find an example to copy into place and modify accordingly at "/usr/share/doc/libpam-pkcs11/examples/pam_pkcs11.conf.example.gz".</fixtext><fix id="F-64215r953546_fix" /><check system="C-64307r953545_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS, for PKI-based authentication, uses local revocation data when unable to access it from the network by using the following command: 
 
Note: If smart card authentication is not being used on the system, this is not applicable.  
  
     $ grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf | grep  -E -- 'crl_auto|crl_offline' 
     cert_policy = ca,signature,ocsp_on,crl_auto; 
  
If "cert_policy" is not set to include "crl_auto" or "crl_offline", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260579"><title>SRG-OS-000068-GPOS-00036</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260579r958452_rule" weight="10.0" severity="high"><version>UBTU-22-612040</version><title>Ubuntu 22.04 LTS must map the authenticated identity to the user or group account for PKI-based authentication.</title><description>&lt;VulnDiscussion&gt;Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000187</ident><fixtext fixref="F-64216r953549_fix">Set "use_mappers=pwent" in "/etc/pam_pkcs11/pam_pkcs11.conf" or, if there is already a comma-separated list of mappers, add it to the list, separated by comma, and before the null mapper.  
  
If the system is missing an "/etc/pam_pkcs11/" directory and an "/etc/pam_pkcs11/pam_pkcs11.conf", find an example to copy into place and modify accordingly at "/usr/share/doc/libpam-pkcs11/examples/pam_pkcs11.conf.example.gz".</fixtext><fix id="F-64216r953549_fix" /><check system="C-64308r953548_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that "use_mappers" is set to "pwent" in "/etc/pam_pkcs11/pam_pkcs11.conf" file by using the following command:  
  
     $ grep -i use_mappers /etc/pam_pkcs11/pam_pkcs11.conf 
     use_mappers = pwent 
  
If "use_mappers" does not contain "pwent", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260580"><title>SRG-OS-000403-GPOS-00182</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260580r958868_rule" weight="10.0" severity="medium"><version>UBTU-22-631010</version><title>Ubuntu 22.04 LTS must use DOD PKI-established certificate authorities for verification of the establishment of protected sessions.</title><description>&lt;VulnDiscussion&gt;Untrusted certificate authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DOD systems or by organizations with insufficient security controls. If the CA used for verifying the certificate is not a DOD-approved CA, trust of this CA has not been established.  
  
The DOD will only accept PKI-certificates obtained from a DOD-approved internal or external certificate authority. Reliance on CAs for the establishment of secure sessions includes, for example, the use of SSL/TLS certificates.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002470</ident><fixtext fixref="F-64217r953552_fix">Configure Ubuntu 22.04 LTS to use of DOD PKI-established certificate authorities for verification of the establishment of protected sessions.  
 
Add at least one DOD certificate authority to the "/usr/share/ca-certificates" directory in the CRT format.  
  
Update the "/etc/ssl/certs" directory by using the following command:  
  
     $ sudo dpkg-reconfigure ca-certificates</fixtext><fix id="F-64217r953552_fix" /><check system="C-64309r953551_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the directory containing the root certificates for Ubuntu 22.04 LTS contains certificate files for DOD PKI-established certificate authorities by iterating over all files in the "/etc/ssl/certs" directory and checking if, at least one, has the subject matching "DOD ROOT CA". 
 
     $ ls /etc/ssl/certs | grep -i DOD 
     DOD_PKE_CA_chain.pem 
 
If no DOD root certificate is found, this is a finding. 
 
Verify that all root certificates present on the system have been approved by the AO. 
 
     $ ls /etc/ssl/certs 
 
If a certificate is present that is not approved by the AO, this is a finding.</check-content></check></Rule></Group><Group id="V-260581"><title>SRG-OS-000383-GPOS-00166</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260581r958828_rule" weight="10.0" severity="low"><version>UBTU-22-631015</version><title>Ubuntu 22.04 LTS must be configured such that Pluggable Authentication Module (PAM) prohibits the use of cached authentications after one day.</title><description>&lt;VulnDiscussion&gt;If cached authentication information is out-of-date, the validity of the authentication information may be questionable.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002007</ident><fixtext fixref="F-64218r953555_fix">Configure PAM to prohibit the use of cached authentications after one day.  
 
Add or modify the following line in the "/etc/sssd/sssd.conf" file, just below the line "[pam]": 
  
offline_credentials_expiration = 1 
  
Note: It is valid for this configuration to be in a file with a name that ends with ".conf" and does not begin with a "." in the "/etc/sssd/conf.d/" directory instead of the "/etc/sssd/sssd.conf" file.</fixtext><fix id="F-64218r953555_fix" /><check system="C-64310r953554_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that PAM prohibits the use of cached authentications after one day by using the following command: 
 
Note: If smart card authentication is not being used on the system, this requirement is not applicable.  
  
     $ sudo grep -i '^\s*offline_credentials_expiration' /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf 
     /etc/sssd/sssd.conf:offline_credentials_expiration = 1 
 
If "offline_credentials_expiration" is not set to "1", is commented out, is missing, or conflicting results are returned, this is a finding.</check-content></check></Rule></Group><Group id="V-260582"><title>SRG-OS-000445-GPOS-00199</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260582r958944_rule" weight="10.0" severity="medium"><version>UBTU-22-651010</version><title>Ubuntu 22.04 LTS 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 Ubuntu 22.04 LTS 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002696</ident><fixtext fixref="F-64219r953558_fix">Install the "aide" package: 
 
     $ sudo apt install aide</fixtext><fix id="F-64219r953558_fix" /><check system="C-64311r953557_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that Advanced Intrusion Detection Environment (AIDE) is installed by using the following command: 
 
     $ dpkg -l | grep aide 
     ii     aide     0.17.4-1     amd64     Advanced Intrusion Detection Environment - dynamic binary 
 
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-260583"><title>SRG-OS-000445-GPOS-00199</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260583r958944_rule" weight="10.0" severity="medium"><version>UBTU-22-651015</version><title>Ubuntu 22.04 LTS must configure AIDE to perform file integrity checking on the file system.</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 Ubuntu 22.04 LTS 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002696</ident><fixtext fixref="F-64220r953561_fix">Initialize AIDE (this will take a few minutes): 
 
     $ sudo aideinit 
     Running aide --init... 
 
Example output: 
 
Start timestamp: 2024-04-01 04:20:00 +1300 (AIDE 0.17.4) 
AIDE initialized database at /var/lib/aide/aide.db.new 
Ignored e2fs attributes: EIh 
 
Number of entries:      146185 
 
--------------------------------------------------- 
The attributes of the (uncompressed) database(s): 
--------------------------------------------------- 
 
/var/lib/aide/aide.db.new 
 SHA256    : UrYbC/KBOJcs8zKcSlKoifnnoPK66DEC 
             Aw6odu/BpgY= 
 SHA512    : ezENbbuh937SPWvtsdjRzy3i47XjLg7j 
             L3UGmr0EcgY6u8rczxgbn2RuwJfrIpef 
             0c1qMNobzrLXyDnnqEqAqw== 
 RMD160    : yBq2xio+g5ne4kvZzzMZ2v+EO9w= 
 TIGER     : GkJ/xkzJGu/aSQqk9A5LN271IOAQC3d0 
 CRC32     : g/beXA== 
 HAVAL     : zZm220YZiGna2edJ6Gi0rPv16AlpqeHB 
             y/XLB3hIPEY= 
 WHIRLPOOL : k6veoXavJ/BH9L125pCYAfTB8w5ZJkdC 
             DvVmYS0+cgmg7M0y/S2v42FNCEJ993mc 
             3kZMXJR/VVmwKg/7ntGixQ== 
 GOST      : psjiyix6mJlNsE984D0NwbfgBmB0ETGl 
             /R4PNvm/wKg= 
 
End timestamp: 2024-04-01 04:29:16 +1300 (run time: 9m 16s)</fixtext><fix id="F-64220r953561_fix" /><check system="C-64312r953560_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that Advanced Intrusion Detection Environment (AIDE) is configured and operating correctly by using the following command (this will take a few minutes): 
 
Note: If AIDE is not installed, this requirement is not applicable. 
 
     $ sudo aide -c /etc/aide/aide.conf --check 
 
Example output: 
 
Start timestamp: 2024-04-01 04:20:00 +1300 (AIDE 0.17.4) 
AIDE found differences between database and filesystem!! 
Ignored e2fs attributes: EIh 
... 
 
If AIDE is being used to perform file integrity checks but the command fails, this is a finding.</check-content></check></Rule></Group><Group id="V-260584"><title>SRG-OS-000363-GPOS-00150</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260584r958794_rule" weight="10.0" severity="medium"><version>UBTU-22-651020</version><title>Ubuntu 22.04 LTS must notify designated personnel if baseline configurations are changed in an unauthorized manner. The file integrity tool must notify the system administrator when changes to the baseline configuration or anomalies in the operation of any security functions are discovered.</title><description>&lt;VulnDiscussion&gt;Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating system. Changes to operating system configurations can have unintended side effects, some of which may be relevant to security.  
  
Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the operating system. The operating system's IMO/ISSO and SAs must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.

Satisfies: SRG-OS-000363-GPOS-00150, SRG-OS-000447-GPOS-00201&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001744</ident><ident system="http://cyber.mil/cci">CCI-002702</ident><fixtext fixref="F-64221r953564_fix">Configure AIDE to notify designated personnel if baseline configurations are changed in an unauthorized manner. 
 
Add or modify the following line in the "/etc/default/aide" file: 
 
SILENTREPORTS=no</fixtext><fix id="F-64221r953564_fix" /><check system="C-64313r953563_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that Advanced Intrusion Detection Environment (AIDE) notifies the system administrator when anomalies in the operation of any security functions are discovered by using the following command:  
  
     $ grep -i '^\s*silentreports' /etc/default/aide  
     SILENTREPORTS=no 
  
If "SILENTREPORTS" is set to "yes", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260585"><title>SRG-OS-000446-GPOS-00200</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260585r958946_rule" weight="10.0" severity="medium"><version>UBTU-22-651025</version><title>Ubuntu 22.04 LTS must be configured so that the script that runs each 30 days or less to check file integrity is the default.</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.  
  
Notifications provided by information systems include, for example, electronic alerts to system administrators, messages to local computer consoles, and/or hardware indications, such as lights.  
  
This requirement applies to Ubuntu 22.04 LTS 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002699</ident><fixtext fixref="F-64222r953567_fix">The cron file for AIDE is fairly complex as it creates the report. This file is installed with the "aide-common" package, and the default can be restored by copying it from the package:  
 
Extract the aide script from the "aide-common" package to its original place:  
  
     $ dpkg-deb --fsys-tarfile /tmp/aide-common_*.deb | sudo tar -x ./usr/share/aide/config/cron.daily/aide -C / 
 
Copy it to the cron.daily directory: 
 
     $  sudo cp -f /usr/share/aide/config/cron.daily/aide /etc/cron.daily/aide</fixtext><fix id="F-64222r953567_fix" /><check system="C-64314r953566_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the Advanced Intrusion Detection Environment (AIDE) default script used to check file integrity each 30 days or less is unchanged.  
  
Download the original aide-common package in the /tmp directory:  
  
     $ cd /tmp; apt download aide-common 
  
Fetch the SHA1 of the original script file: 
  
     $ dpkg-deb --fsys-tarfile /tmp/aide-common_*.deb | tar -xO ./usr/share/aide/config/cron.daily/aide | sha1sum 
     b71bb2cafaedf15ec3ac2f566f209d3260a37af0  -  
  
Compare with the SHA1 of the file in the daily or monthly cron directory:  
  
     $ sha1sum /etc/cron.{daily,monthly}/aide 2&gt;/dev/null 
     b71bb2cafaedf15ec3ac2f566f209d3260a37af0  /etc/cron.daily/aide 
  
If there is no AIDE script file in the cron directories, or the SHA1 value of at least one file in the daily or monthly cron directory does not match the SHA1 of the original, this is a finding.</check-content></check></Rule></Group><Group id="V-260586"><title>SRG-OS-000278-GPOS-00108</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260586r1044779_rule" weight="10.0" severity="medium"><version>UBTU-22-651030</version><title>Ubuntu 22.04 LTS must use cryptographic mechanisms to protect the integrity of audit tools.</title><description>&lt;VulnDiscussion&gt;Protecting the integrity of the tools used for auditing purposes is a critical step toward ensuring the integrity of audit information. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.  
  
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.  
  
It is not uncommon for attackers to replace the audit tools or inject code into the existing tools with the purpose of providing the capability to hide or erase system activity from the audit logs.  
  
To address this risk, audit tools must be cryptographically signed in order to provide the capability to identify when the audit tools have been modified, manipulated, or replaced. An example is a checksum hash of the file or 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001496</ident><fixtext fixref="F-64223r1044778_fix">Configure AIDE to protect the integrity of audit tools: 
 
Add or modify the following lines in the "/etc/aide/aide.conf" file: 
 
# Audit Tools  
/sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512  
/sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512  
/sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512  
/sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512  
/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512  
/sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512</fixtext><fix id="F-64223r1044778_fix" /><check system="C-64315r1044777_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that Advanced Intrusion Detection Environment (AIDE) is properly configured to use cryptographic mechanisms to protect the integrity of audit tools by using the following command:  
  
     $ grep -E '(\/sbin\/(audit|au))' /etc/aide/aide.conf 
     /sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512  
     /sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512  
     /sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512  
     /sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512  
     /sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512  
     /sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512  
  
If any of the seven lines do not appear as shown, are commented out, or are missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260587"><title>SRG-OS-000479-GPOS-00224</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260587r959008_rule" weight="10.0" severity="low"><version>UBTU-22-651035</version><title>Ubuntu 22.04 LTS must have a crontab script running weekly to offload audit events of standalone systems.</title><description>&lt;VulnDiscussion&gt;Information stored in one location is vulnerable to accidental or incidental deletion or alteration.  
  
Offloading is a common process in information systems with limited audit storage capacity.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001851</ident><fixtext fixref="F-64224r953573_fix">Create a script that offloads audit logs to external media and runs weekly.  
  
The script must be located in the "/etc/cron.weekly" directory.</fixtext><fix id="F-64224r953573_fix" /><check system="C-64316r953572_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify there is a script that offloads audit data and that script runs weekly by using the following command: 
 
Note: If the system is not connected to a network, this requirement is not applicable. 
  
     $ ls /etc/cron.weekly 
     &lt;audit_offload_script_name&gt; 
  
Check if the script inside the file does offloading of audit logs to external media.  
  
If the script file does not exist or does not offload audit logs, this is a finding.</check-content></check></Rule></Group><Group id="V-260588"><title>SRG-OS-000269-GPOS-00103</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260588r991562_rule" weight="10.0" severity="medium"><version>UBTU-22-652010</version><title>Ubuntu 22.04 LTS must be configured to preserve log records from failure events.</title><description>&lt;VulnDiscussion&gt;Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system.   
  
Preserving operating system state information helps to facilitate operating system restart and return to the operational mode of the organization with least disruption to mission/business processes.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001665</ident><fixtext fixref="F-64225r953576_fix">Install the log service by using the following command:  
 
     $ sudo apt-get install rsyslog 
  
Enable and activate the log service by using the following command:  
  
     $ sudo systemctl enable rsyslog.service --now</fixtext><fix id="F-64225r953576_fix" /><check system="C-64317r953575_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the log service is installed properly by using the following command:  
  
     $ dpkg -l | grep rsyslog 
     ii     rsyslog     8.2112.0-2ubuntu2.2     amd64     reliable system and kernel logging daemon 
  
If the "rsyslog" package is not installed, this is a finding.  
  
Check that the log service is enabled and active by using the following commands:  
 
     $ systemctl is-enabled rsyslog.service 
     enabled  
  
     $ systemctl is-active rsyslog.service 
     active  
  
If "rsyslog.service" is not enabled and active, this is a finding.</check-content></check></Rule></Group><Group id="V-260589"><title>SRG-OS-000032-GPOS-00013</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260589r958406_rule" weight="10.0" severity="medium"><version>UBTU-22-652015</version><title>Ubuntu 22.04 LTS must monitor remote access methods.</title><description>&lt;VulnDiscussion&gt;Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities, increase risk and make remote user access management difficult at best.  
  
Remote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.  
  
Automated monitoring of remote access sessions allows organizations to detect cyberattacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000067</ident><fixtext fixref="F-64226r953579_fix">Configure Ubuntu 22.04 LTS to monitor all remote access methods. 
 
Add or modify the following line in the "/etc/rsyslog.d/50-default.conf" file: 
 
auth.*,authpriv.* /var/log/secure  
daemon.* /var/log/messages  
 
Restart "rsyslog.service" for the changes to take effect by using the following command:  
  
     $ sudo systemctl restart rsyslog.service</fixtext><fix id="F-64226r953579_fix" /><check system="C-64318r953578_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that Ubuntu 22.04 LTS monitors all remote access methods by using the following command:  
  
     $  grep -Er '^(auth\.\*,authpriv\.\*|daemon\.\*)' /etc/rsyslog.* 
     /etc/rsyslog.d/50-default.conf:auth.*,authpriv.* /var/log/secure 
     /etc/rsyslog.d/50-default.conf:daemon.* /var/log/messages 
  
If "auth.*", "authpriv.*", or "daemon.*" are not configured to be logged in at least one of the config files, this is a finding.</check-content></check></Rule></Group><Group id="V-260590"><title>SRG-OS-000037-GPOS-00015</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260590r1015022_rule" weight="10.0" severity="medium"><version>UBTU-22-653010</version><title>Ubuntu 22.04 LTS must have the "auditd" package installed.</title><description>&lt;VulnDiscussion&gt;Without establishing the when, where, type, source, and outcome of events that occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.  
  
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 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.  
  
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.  
  
Successful incident response and auditing relies on timely, accurate system information and analysis in order to allow the organization to identify and respond to potential incidents in a proficient manner. If the operating system does not provide the ability to centrally review the operating system logs, forensic analysis is negatively impacted.  
  
Associating event types with detected events in Ubuntu 22.04 LTS audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.

Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000042-GPOS-00020, SRG-OS-000042-GPOS-00021, SRG-OS-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000062-GPOS-00031, SRG-OS-000122-GPOS-00063, SRG-OS-000337-GPOS-00129, SRG-OS-000348-GPOS-00136, SRG-OS-000349-GPOS-00137, SRG-OS-000350-GPOS-00138, SRG-OS-000351-GPOS-00139, SRG-OS-000352-GPOS-00140, SRG-OS-000353-GPOS-00141, SRG-OS-000354-GPOS-00142, SRG-OS-000365-GPOS-00152, SRG-OS-000475-GPOS-00220&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000130</ident><ident system="http://cyber.mil/cci">CCI-000131</ident><ident system="http://cyber.mil/cci">CCI-000132</ident><ident system="http://cyber.mil/cci">CCI-000133</ident><ident system="http://cyber.mil/cci">CCI-000134</ident><ident system="http://cyber.mil/cci">CCI-000135</ident><ident system="http://cyber.mil/cci">CCI-000154</ident><ident system="http://cyber.mil/cci">CCI-000158</ident><ident system="http://cyber.mil/cci">CCI-000169</ident><ident system="http://cyber.mil/cci">CCI-000172</ident><ident system="http://cyber.mil/cci">CCI-003938</ident><ident system="http://cyber.mil/cci">CCI-001875</ident><ident system="http://cyber.mil/cci">CCI-001876</ident><ident system="http://cyber.mil/cci">CCI-001877</ident><ident system="http://cyber.mil/cci">CCI-001878</ident><ident system="http://cyber.mil/cci">CCI-001879</ident><ident system="http://cyber.mil/cci">CCI-001880</ident><ident system="http://cyber.mil/cci">CCI-001881</ident><ident system="http://cyber.mil/cci">CCI-001882</ident><ident system="http://cyber.mil/cci">CCI-001914</ident><ident system="http://cyber.mil/cci">CCI-001814</ident><fixtext fixref="F-64227r953582_fix">Install the "auditd" package by using the following command:  
  
     $ sudo apt-get install auditd</fixtext><fix id="F-64227r953582_fix" /><check system="C-64319r953581_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the "auditd" package is installed by using the following command:  
  
     $ dpkg -l | grep auditd 
     ii     libauditd     1:3.0.7-1build1     amd64     User space tools for security auditing 
 
If the "auditd" package is not installed, this is a finding.</check-content></check></Rule></Group><Group id="V-260591"><title>SRG-OS-000037-GPOS-00015</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260591r1015023_rule" weight="10.0" severity="medium"><version>UBTU-22-653015</version><title>Ubuntu 22.04 LTS must produce audit records and reports containing information to establish when, where, what type, the source, and the outcome for all DOD-defined auditable events and actions in near real time.</title><description>&lt;VulnDiscussion&gt;Without establishing the when, where, type, source, and outcome of events that occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.  
  
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 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.  
  
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.  
  
Successful incident response and auditing relies on timely, accurate system information and analysis to allow the organization to identify and respond to potential incidents in a proficient manner. If the operating system does not provide the ability to centrally review the operating system logs, forensic analysis is negatively impacted.  
  
Associating event types with detected events in Ubuntu 22.04 LTS audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.

Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000042-GPOS-00020, SRG-OS-000042-GPOS-00021, SRG-OS-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000062-GPOS-00031, SRG-OS-000122-GPOS-00063, SRG-OS-000337-GPOS-00129, SRG-OS-000348-GPOS-00136, SRG-OS-000349-GPOS-00137, SRG-OS-000350-GPOS-00138, SRG-OS-000351-GPOS-00139, SRG-OS-000352-GPOS-00140, SRG-OS-000353-GPOS-00141, SRG-OS-000354-GPOS-00142, SRG-OS-000365-GPOS-00152, SRG-OS-000475-GPOS-00220&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000130</ident><ident system="http://cyber.mil/cci">CCI-000131</ident><ident system="http://cyber.mil/cci">CCI-000132</ident><ident system="http://cyber.mil/cci">CCI-000133</ident><ident system="http://cyber.mil/cci">CCI-000134</ident><ident system="http://cyber.mil/cci">CCI-000135</ident><ident system="http://cyber.mil/cci">CCI-000154</ident><ident system="http://cyber.mil/cci">CCI-000158</ident><ident system="http://cyber.mil/cci">CCI-000169</ident><ident system="http://cyber.mil/cci">CCI-000172</ident><ident system="http://cyber.mil/cci">CCI-003938</ident><ident system="http://cyber.mil/cci">CCI-001875</ident><ident system="http://cyber.mil/cci">CCI-001876</ident><ident system="http://cyber.mil/cci">CCI-001877</ident><ident system="http://cyber.mil/cci">CCI-001878</ident><ident system="http://cyber.mil/cci">CCI-001879</ident><ident system="http://cyber.mil/cci">CCI-001880</ident><ident system="http://cyber.mil/cci">CCI-001881</ident><ident system="http://cyber.mil/cci">CCI-001882</ident><ident system="http://cyber.mil/cci">CCI-001914</ident><ident system="http://cyber.mil/cci">CCI-001814</ident><fixtext fixref="F-64228r953585_fix">Enable and start the "auditd.service" by using the following command:  
  
     $ sudo systemctl enable auditd.service --now</fixtext><fix id="F-64228r953585_fix" /><check system="C-64320r953584_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the "auditd.service" is enabled and active by using the following commands:  
  
     $ systemctl is-enabled auditd.service 
     enabled 
  
     $ systemctl is-active auditd.service 
     active  
  
If the "auditd.service" is not enabled and active, this is a finding.</check-content></check></Rule></Group><Group id="V-260592"><title>SRG-OS-000342-GPOS-00133</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260592r958754_rule" weight="10.0" severity="low"><version>UBTU-22-653020</version><title>Ubuntu 22.04 LTS audit event multiplexor must be configured to offload audit logs onto a different system from the system being audited.</title><description>&lt;VulnDiscussion&gt;Information stored in one location is vulnerable to accidental or incidental deletion or alteration.  
  
Offloading is a common process in information systems with limited audit storage capacity. 
 
The auditd service does not include the ability to send audit records to a centralized server for management directly. However, it can use a plug-in for audit event multiplexor to pass audit records to a remote server.

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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001851</ident><fixtext fixref="F-64229r953588_fix">Configure the audit event multiplexor to offload audit records to a different system from the system being audited.  
  
Install the "audisp-plugins" package by using the following command:  
  
     $ sudo apt-get install audispd-plugins 
  
Set the audisp-remote plugin as active by editing the "/etc/audit/plugins.d/au-remote.conf" file:  
  
     $ sudo sed -i -E 's/active\s*=\s*no/active = yes/' /etc/audit/plugins.d/au-remote.conf 
  
Set the IP address of the remote system by editing the "/etc/audit/audisp-remote.conf" file:  
  
     $ sudo sed -i -E 's/(remote_server\s*=).*/\1 &lt;remote_server_ip_address&gt;/' /etc/audit/audisp-remote.conf 
  
Restart the "auditd.service" for the changes to take effect:  
  
     $ sudo systemctl restart auditd.service</fixtext><fix id="F-64229r953588_fix" /><check system="C-64321r953587_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the audit event multiplexor is configured to offload audit records to a different system from the system being audited.  
  
Check if the "audispd-plugins" package is installed:  
  
     $ dpkg -l | grep audispd-plugins 
     ii     audispd-plugins     1:3.0.7-1build1     amd64     Plugins for the audit event dispatcher 
  
If the "audispd-plugins" package is not installed, this is a finding.  
  
Check that the records are being offloaded to a remote server by using the following command:  
  
     $ sudo grep -i active /etc/audit/plugins.d/au-remote.conf 
     active = yes  
  
If "active" is not set to "yes", or the line is commented out, or is missing, this is a finding.  
  
Check that audisp-remote plugin is configured to send audit logs to a different system:  
  
     $ sudo grep -i remote_server /etc/audit/audisp-remote.conf 
     remote_server = 240.9.19.81 
  
If the "remote_server" parameter is not set, is set with a local IP address, or is set with an invalid IP address, this is a finding.</check-content></check></Rule></Group><Group id="V-260593"><title>SRG-OS-000046-GPOS-00022</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260593r958424_rule" weight="10.0" severity="low"><version>UBTU-22-653025</version><title>Ubuntu 22.04 LTS must alert the information system security officer (ISSO) and system administrator (SA) in the event of an audit processing failure.</title><description>&lt;VulnDiscussion&gt;It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected.  
  
Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded.  
  
This requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000139</ident><fixtext fixref="F-64230r953591_fix">Configure "auditd" service to notify the SA and ISSO in the event of an audit processing failure.   
  
Add or modify the following line in the "/etc/audit/auditd.conf " file: 
  
action_mail_acct = &lt;administrator_email_account&gt;  
  
Note: Change "administrator_email_account" to the email address of the SA and/or ISSO. 
  
Restart the "auditd" service for the changes take effect:  
  
     $ sudo systemctl restart auditd.service</fixtext><fix id="F-64230r953591_fix" /><check system="C-64322r953590_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the SA and ISSO are notified in the event of an audit processing failure by using the following command: 
 
Note: An email package must be installed on the system for email notifications to be sent. 
  
     $ sudo grep -i action_mail_acct /etc/audit/auditd.conf 
     action_mail_acct = &lt;administrator_email_account&gt; 
  
If "action_mail_acct" is not set to the email address of the SA and/or ISSO, is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260594"><title>SRG-OS-000047-GPOS-00023</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260594r1038966_rule" weight="10.0" severity="medium"><version>UBTU-22-653030</version><title>Ubuntu 22.04 LTS must shut down by default upon audit failure.</title><description>&lt;VulnDiscussion&gt;It is critical that when the operating system 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, the operating system must continue generating audit records if possible (automatically restarting the audit service if necessary), 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, the operating system 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000140</ident><fixtext fixref="F-64231r953594_fix">Configure Ubuntu 22.04 LTS to shut down by default upon audit failure.  
  
Add or modify the following line in the "/etc/audit/auditd.conf " file: 
 
disk_full_action = HALT 
  
Restart the "auditd" service for the changes to take effect:  
  
     $ sudo systemctl restart auditd.service 
 
Note: If system availability has been determined to be more important, and this decision is documented with the ISSO, configure Ubuntu 22.04 LTS to notify system administration staff and ISSO staff in the event of an audit processing failure by setting the "disk_full_action" to "SYSLOG" or "SINGLE".</fixtext><fix id="F-64231r953594_fix" /><check system="C-64323r953593_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS takes the appropriate action when the audit storage volume is full by using the following command:  
  
     $ sudo grep -i disk_full_action /etc/audit/auditd.conf 
     disk_full_action = HALT 
  
If "disk_full_action" is not set to "HALT", "SYSLOG", or "SINGLE", is commented out, or is missing, this is a finding.</check-content></check></Rule></Group><Group id="V-260595"><title>SRG-OS-000341-GPOS-00132</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260595r958752_rule" weight="10.0" severity="low"><version>UBTU-22-653035</version><title>Ubuntu 22.04 LTS must allocate audit record storage capacity to store at least one weeks' worth of audit records, when audit records are not immediately sent to a central audit record storage facility.</title><description>&lt;VulnDiscussion&gt;To ensure operating systems have a sufficient storage capacity in which to write the audit logs, operating systems must be able to allocate audit record storage capacity.  
  
The task of allocating audit record storage capacity is usually performed during initial installation of the operating system.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001849</ident><fixtext fixref="F-64232r953597_fix">Allocate enough storage capacity for at least one week's worth 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, use the "parted" program to resize the partition with sufficient space to contain one week's worth of audit records.  
  
If audit records are not stored on a partition made specifically for audit records, a new partition with sufficient amount of space will need be to be created.  
  
Set the auditd server to point to the mount point where the audit records must be located:  
  
     $ sudo sed -i -E 's@^(log_file\s*=\s*).*@\1 &lt;audit_partition_mountpoint&gt;/audit.log@' /etc/audit/auditd.conf  
  
where &lt;audit_partition_mountpoint&gt; is the aforementioned mount point.</fixtext><fix id="F-64232r953597_fix" /><check system="C-64324r953596_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS allocates audit record storage capacity to store at least one week's worth of audit records when audit records are not immediately sent to a central audit record storage facility.  
  
Determine which partition the audit records are being written to by using the following command:  
  
     $ sudo grep -i log_file /etc/audit/auditd.conf 
     log_file = /var/log/audit/audit.log 
  
Check the size of the partition that audit records are written to (with the example being "/var/log/audit/") by using the following command:  
  
     $ sudo df -h /var/log/audit/ 
     /dev/sda2 24G 10.4G 13.6G 43% /var/log/audit 
  
If the audit records are not written to a partition made specifically for audit records ("/var/log/audit" as a separate partition), determine the amount of space being used by other files in the partition by using the following command:  
  
     $ sudo du -sh &lt;audit_partition&gt; 
     1.8G /var/log/audit  
  
Note: The partition size needed to capture a week's worth of audit records is based on the activity level of the system and the total storage capacity available.  
  
If the audit record partition is not allocated for sufficient storage capacity, this is a finding.</check-content></check></Rule></Group><Group id="V-260596"><title>SRG-OS-000343-GPOS-00134</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260596r971542_rule" weight="10.0" severity="low"><version>UBTU-22-653040</version><title>Ubuntu 22.04 LTS must immediately notify the system administrator (SA) and information system security officer (ISSO) when the audit record storage volume reaches 25 percent remaining of the allocated capacity.</title><description>&lt;VulnDiscussion&gt;If security personnel are not notified immediately when storage volume reaches 25 percent remaining of the allocated capacity, 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-001855</ident><fixtext fixref="F-64233r953600_fix">Configure Ubuntu 22.04 LTS to notify the SA and ISSO when the audit record storage volume reaches 25 percent remaining of the allocated capacity. 
 
Add or modify the following lines in the "/etc/audit/auditd.conf " file: 
 
space_left = 25% 
space_left_action = email 
 
Restart the "auditd" service for the changes to take effect:  
  
     $ sudo systemctl restart auditd.service 
  
Note: If the "space_left_action" parameter is set to "exec", ensure the command being executed notifies the SA and ISSO.</fixtext><fix id="F-64233r953600_fix" /><check system="C-64325r953599_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS is configured to notify the SA and ISSO when the audit record storage volume reaches 25 percent remaining of the allocated capacity by using the following command:  
 
     $ sudo grep -i space_left /etc/audit/auditd.conf 
     space_left = 25% 
     space_left_action = email 
  
If "space_left" is set to a value less than "25%", is commented out, or is missing, this is a finding.

If "space_left_action" is not set to "email", is commented out, or is missing, this is a finding. 
  
Note: If the "space_left_action" is set to "exec", the system executes a designated script. If this script informs the SA of the event, this is not a finding.</check-content></check></Rule></Group><Group id="V-260597"><title>SRG-OS-000057-GPOS-00027</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260597r958434_rule" weight="10.0" severity="medium"><version>UBTU-22-653045</version><title>Ubuntu 22.04 LTS must be configured so that audit log files are not read- or write-accessible by unauthorized users.</title><description>&lt;VulnDiscussion&gt;Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.  
  
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.

Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000162</ident><ident system="http://cyber.mil/cci">CCI-000163</ident><fixtext fixref="F-64234r953603_fix">Configure the audit log files to have a mode of "600" or less permissive.  
  
Using the path of the directory containing the audit logs, configure the audit log files to have a mode of "600" or less permissive by using the following command:  
  
     $ sudo chmod 600 /var/log/audit/*</fixtext><fix id="F-64234r953603_fix" /><check system="C-64326r953602_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the audit log files have a mode of "600" or less permissive.  
  
Determine where the audit logs are stored by using the following command:  
  
     $ sudo grep -iw log_file /etc/audit/auditd.conf 
     log_file = /var/log/audit/audit.log 
  
Using the path of the directory containing the audit logs, determine if the audit log files have a mode of "600" or less by using the following command:  
  
     $ sudo stat -c "%n %a" /var/log/audit/* 
     /var/log/audit/audit.log 600 
  
If the audit log files have a mode more permissive than "600", this is a finding.</check-content></check></Rule></Group><Group id="V-260598"><title>SRG-OS-000057-GPOS-00027</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260598r958434_rule" weight="10.0" severity="medium"><version>UBTU-22-653050</version><title>Ubuntu 22.04 LTS must be configured to permit only authorized users ownership of the audit log files.</title><description>&lt;VulnDiscussion&gt;Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.  
  
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.

Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000162</ident><ident system="http://cyber.mil/cci">CCI-000163</ident><ident system="http://cyber.mil/cci">CCI-000164</ident><fixtext fixref="F-64235r953606_fix">Configure the audit log directory and its underlying files to be owned by "root" user.  
  
Using the path of the directory containing the audit logs, configure the audit log files to be owned by "root" user by using the following command:  
  
     $ sudo chown root /var/log/audit/*</fixtext><fix id="F-64235r953606_fix" /><check system="C-64327r953605_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the audit log files are owned by "root" account.  
  
Determine where the audit logs are stored by using the following command:  
  
     $ sudo grep -iw log_file /etc/audit/auditd.conf 
     log_file = /var/log/audit/audit.log  
  
Using the path of the directory containing the audit logs, determine if the audit log files are owned by the "root" user by using the following command:  
  
     $ sudo stat -c "%n %U" /var/log/audit/* 
     /var/log/audit/audit.log root  
  
If the audit log files are owned by a user other than "root", this is a finding.</check-content></check></Rule></Group><Group id="V-260599"><title>SRG-OS-000057-GPOS-00027</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260599r958434_rule" weight="10.0" severity="medium"><version>UBTU-22-653055</version><title>Ubuntu 22.04 LTS must permit only authorized groups ownership of the audit log files.</title><description>&lt;VulnDiscussion&gt;Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.  
  
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.

Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000162</ident><ident system="http://cyber.mil/cci">CCI-000163</ident><ident system="http://cyber.mil/cci">CCI-000164</ident><fixtext fixref="F-64236r953609_fix">Configure the group owner of newly created audit logs to be "root". 
 
Add or modify the following lines in the "/etc/audit/auditd.conf " file: 
 
log_group = root 
 
Reload the configuration file of the audit service to update the group ownership of existing files: 
 
     $ sudo systemctl kill auditd -s SIGHUP</fixtext><fix id="F-64236r953609_fix" /><check system="C-64328r953608_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the group owner of newly created audit logs is "root" by using the following command:  
 
     $ sudo grep -iw log_group /etc/audit/auditd.conf 
     log_group = root 
 
If "log_group" is not set to "root", this is a finding.</check-content></check></Rule></Group><Group id="V-260600"><title>SRG-OS-000059-GPOS-00029</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260600r958438_rule" weight="10.0" severity="medium"><version>UBTU-22-653060</version><title>Ubuntu 22.04 LTS must be configured so that the audit log directory is not write-accessible by unauthorized users.</title><description>&lt;VulnDiscussion&gt;If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.  
  
To ensure the veracity of audit information, the operating system must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design.  
  
Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000164</ident><fixtext fixref="F-64237r953612_fix">Configure the audit log directory to have a mode of "750" or less permissive.  
  
Using the path of the directory containing the audit logs, configure the audit log directory to have a mode of "750" or less permissive by using the following command:  
  
     $ sudo chmod -R  g-w,o-rwx /var/log/audit</fixtext><fix id="F-64237r953612_fix" /><check system="C-64329r953611_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that the audit log directory has a mode of "750" or less permissive.  
  
Determine where the audit logs are stored by using the following command:  
 
     $ sudo grep -iw log_file /etc/audit/auditd.conf 
     log_file = /var/log/audit/audit.log 
  
Using the path of the directory containing the audit logs, determine if the directory has a mode of "750" or less by using the following command:  
  
     $ sudo stat -c "%n %a" /var/log/audit 
     /var/log/audit 750 
  
If the audit log directory has a mode more permissive than "750", this is a finding.</check-content></check></Rule></Group><Group id="V-260601"><title>SRG-OS-000063-GPOS-00032</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260601r958444_rule" weight="10.0" severity="medium"><version>UBTU-22-653065</version><title>Ubuntu 22.04 LTS must be configured so that audit configuration files are not write-accessible by unauthorized users.</title><description>&lt;VulnDiscussion&gt;Without the capability to restrict which roles and individuals 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000171</ident><fixtext fixref="F-64238r953615_fix">Configure /etc/audit/audit.rules", "/etc/audit/auditd.conf", and "/etc/audit/rules.d/*" files to have a mode of "640" by using the following command:  
  
     $ sudo chmod -R 640 /etc/audit/audit.rules /etc/audit/auditd.conf /etc/audit/rules.d/*</fixtext><fix id="F-64238r953615_fix" /><check system="C-64330r953614_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that "/etc/audit/audit.rules", "/etc/audit/auditd.conf", and "/etc/audit/rules.d/*" files have a mode of "640" or less permissive by using the following command:  
  
     $ sudo ls -al /etc/audit/audit.rules /etc/audit/auditd.conf /etc/audit/rules.d/* | awk '{print $1, $9}' 
     -rw-r----- /etc/audit/audit.rules 
     -rw-r----- /etc/audit/auditd.conf 
     -rw-r----- /etc/audit/rules.d/audit.rules 
 
If "/etc/audit/audit.rules", "/etc/audit/auditd.conf", or "/etc/audit/rules.d/*" files have a mode more permissive than "640", this is a finding.</check-content></check></Rule></Group><Group id="V-260602"><title>SRG-OS-000063-GPOS-00032</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260602r958444_rule" weight="10.0" severity="medium"><version>UBTU-22-653070</version><title>Ubuntu 22.04 LTS must permit only authorized accounts to own the audit configuration files.</title><description>&lt;VulnDiscussion&gt;Without the capability to restrict which roles and individuals 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000171</ident><fixtext fixref="F-64239r953618_fix">Configure "/etc/audit/audit.rules", "/etc/audit/rules.d/*", and "/etc/audit/auditd.conf" files to be owned by root by using the following command:  
  
     $ sudo chown -R root /etc/audit/audit.rules /etc/audit/auditd.conf /etc/audit/rules.d/*</fixtext><fix id="F-64239r953618_fix" /><check system="C-64331r953617_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that "/etc/audit/audit.rules", "/etc/audit/auditd.conf", and "/etc/audit/rules.d/*" files are owned by root account by using the following command:  
  
     $ sudo ls -al /etc/audit/audit.rules /etc/audit/auditd.conf /etc/audit/rules.d/* | awk '{print $3, $9}' 
     root /etc/audit/audit.rules 
     root /etc/audit/auditd.conf 
     root /etc/audit/rules.d/audit.rules 
 
If "/etc/audit/audit.rules", "/etc/audit/auditd.conf", or "/etc/audit/rules.d/*" files are owned by a user other than "root", this is a finding.</check-content></check></Rule></Group><Group id="V-260603"><title>SRG-OS-000063-GPOS-00032</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260603r958444_rule" weight="10.0" severity="medium"><version>UBTU-22-653075</version><title>Ubuntu 22.04 LTS must permit only authorized groups to own the audit configuration files.</title><description>&lt;VulnDiscussion&gt;Without the capability to restrict which roles and individuals 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000171</ident><fixtext fixref="F-64240r953621_fix">Configure "/etc/audit/audit.rules", "/etc/audit/rules.d/*", and "/etc/audit/auditd.conf" files to be owned by root group by using the following command:  
  
     $ sudo chown -R :root /etc/audit/audit.rules /etc/audit/auditd.conf /etc/audit/rules.d/*</fixtext><fix id="F-64240r953621_fix" /><check system="C-64332r953620_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that "/etc/audit/audit.rules", "/etc/audit/auditd.conf", and "/etc/audit/rules.d/*" files are owned by root group by using the following command:  
  
     $ sudo ls -al /etc/audit/audit.rules /etc/audit/auditd.conf /etc/audit/rules.d/* | awk '{print $4, $9}'  
     root /etc/audit/audit.rules 
     root /etc/audit/auditd.conf 
     root /etc/audit/rules.d/audit.rules 
  
If "/etc/audit/audit.rules", "/etc/audit/auditd.conf", or "/etc/audit/rules.d/*" files are owned by a group other than "root", this is a finding.</check-content></check></Rule></Group><Group id="V-260604"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260604r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654010</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the apparmor_parser command.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.  
  
Audit records can be generated from various components within the information system (e.g., module or policy filter).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64241r953624_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "apparmor_parser" command. 
 
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file: 
 
-a always,exit -F path=/sbin/apparmor_parser -F perm=x -F auid&gt;=1000 -F auid!=unset -k perm_chng 
 
To reload the rules file, issue the following command: 
 
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64241r953624_fix" /><check system="C-64333r953623_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful attempts to use the "apparmor_parser" command by using the following command:  
  
     $ sudo auditctl -l | grep apparmor_parser 
     -a always,exit -S all -F path=/sbin/apparmor_parser -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=perm_chng  
 
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260605"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260605r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654015</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the chacl command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64242r953627_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chacl" command. 
 
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file: 
 
-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid&gt;=1000 -F auid!=unset -k perm_chng 
 
To reload the rules file, issue the following command: 
 
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64242r953627_fix" /><check system="C-64334r953626_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful attempts to use the "chacl" command by using the following command:   
 
     $ sudo auditctl -l | grep chacl 
     -a always,exit -S all -F path=/usr/bin/chacl -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=perm_chng 
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260606"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260606r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654020</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the chage command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64243r953630_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "chage" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file: 
  
-a always,exit -F path=/usr/bin/chage -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-chage 
 
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64243r953630_fix" /><check system="C-64335r953629_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that an audit event is generated for any successful/unsuccessful use of the "chage" command by using the following command:  
  
     $ sudo auditctl -l | grep -w chage 
     -a always,exit -S all -F path=/usr/bin/chage -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-chage 
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260607"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260607r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654025</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the chcon command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64244r953633_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chcon" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid&gt;=1000 -F auid!=unset -k perm_chng 
 
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64244r953633_fix" /><check system="C-64336r953632_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful attempts to use the "chcon" command by using the following command:  
  
     $ sudo auditctl -l | grep chcon 
     -a always,exit -S all -F path=/usr/bin/chcon -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=perm_chng 
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260608"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260608r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654030</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the chfn command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64245r953636_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "chfn" command.  
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/bin/chfn -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-chfn 
  
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64245r953636_fix" /><check system="C-64337r953635_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records upon successful/unsuccessful attempts to use the "chfn" command by using the following command:  
  
     $ sudo auditctl -l | grep /usr/bin/chfn 
     -a always,exit -S all -F path=/usr/bin/chfn -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-chfn  
  
If the command does not return lines that match the example or the lines are commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260609"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260609r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654035</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the chsh command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64246r953639_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chsh" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid&gt;=1000 -F auid!=unset -k priv_cmd 
    
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64246r953639_fix" /><check system="C-64338r953638_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful attempts to use the "chsh" command by using the following command:  
  
     $ sudo auditctl -l | grep chsh 
     -a always,exit -S all -F path=/usr/bin/chsh -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=priv_cmd  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Notes: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.</check-content></check></Rule></Group><Group id="V-260610"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260610r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654040</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the crontab command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64247r953642_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "crontab" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-crontab 
    
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64247r953642_fix" /><check system="C-64339r953641_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that an audit event is generated for any successful/unsuccessful use of the "crontab" command by using the following command:  
  
     $ sudo auditctl -l | grep -w crontab 
     -a always,exit -S all -F path=/usr/bin/crontab -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-crontab  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260611"><title>SRG-OS-000477-GPOS-00222</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260611r991586_rule" weight="10.0" severity="medium"><version>UBTU-22-654045</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful attempts to use the fdisk command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64248r953645_fix">Configure Ubuntu 22.04 LTS to audit the execution of the partition management program "fdisk".  
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-w /usr/sbin/fdisk -p x -k fdisk 
   
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64248r953645_fix" /><check system="C-64340r953644_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS is configured to audit the execution of the partition management program "fdisk" by using the following command:  
  
     $ sudo auditctl -l | grep fdisk 
     -w /usr/sbin/fdisk -p x -k fdisk 
  
If the command does not return a line, or the line is commented out, this is a finding.  
  
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260612"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260612r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654050</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the gpasswd command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64249r953648_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "gpasswd" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-gpasswd 
    
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64249r953648_fix" /><check system="C-64341r953647_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that an audit event is generated for any successful/unsuccessful use of the "gpasswd" command by using the following command: 
  
     $ sudo auditctl -l | grep -w gpasswd 
     -a always,exit -S all -F path=/usr/bin/gpasswd -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-gpasswd  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260613"><title>SRG-OS-000477-GPOS-00222</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260613r991586_rule" weight="10.0" severity="medium"><version>UBTU-22-654055</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful attempts to use the kmod command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64250r953651_fix">Configure Ubuntu 22.04 LTS to audit the execution of the module management program "kmod".  
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-w /bin/kmod -p x -k modules 
   
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64250r953651_fix" /><check system="C-64342r953650_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS is configured to audit the execution of the module management program "kmod" by using the following command:  
  
     $ sudo auditctl -l | grep kmod  
     -w /bin/kmod -p x -k module  
  
If the command does not return a line, or the line is commented out, this is a finding.  
  
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260614"><title>SRG-OS-000477-GPOS-00222</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260614r991586_rule" weight="10.0" severity="medium"><version>UBTU-22-654060</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful attempts to use modprobe command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64251r953654_fix">Configure Ubuntu 22.04 LTS to audit the execution of the module management program "modprobe".  
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-w /sbin/modprobe -p x -k modules  
   
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64251r953654_fix" /><check system="C-64343r953653_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify if Ubuntu 22.04 LTS is configured to audit the execution of the module management program "modprobe" with the following command:  
  
     $ sudo auditctl -l | grep /sbin/modprobe 
     -w /sbin/modprobe -p x -k modules  
  
If the command does not return a line, or the line is commented out, this is a finding.  
  
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260615"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260615r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654065</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the mount command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64252r953657_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "mount" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/bin/mount -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-mount  
  
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64252r953657_fix" /><check system="C-64344r953656_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records upon successful/unsuccessful attempts to use the "mount" command by using the following command:  
  
     $ sudo auditctl -l | grep /usr/bin/mount 
     -a always,exit -S all -F path=/usr/bin/mount -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-mount  
  
If the command does not return lines that match the example or the lines are commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260616"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260616r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654070</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the newgrp command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64253r953660_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "newgrp" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid&gt;=1000 -F auid!=unset -k priv_cmd  
    
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64253r953660_fix" /><check system="C-64345r953659_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful attempts to use the "newgrp" command by using the following command:   
  
     $ sudo auditctl -l | grep newgrp 
     -a always,exit -S all -F path=/usr/bin/newgrp -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=priv_cmd 
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260617"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260617r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654075</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the pam_timestamp_check command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64254r953663_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "pam_timestamp_check" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-pam_timestamp_check  
    
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64254r953663_fix" /><check system="C-64346r953662_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that an audit event is generated for any successful/unsuccessful use of the "pam_timestamp_check" command by using the following command:  
   
     $ sudo auditctl -l | grep -w pam_timestamp_check 
     -a always,exit -S all -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-pam_timestamp_check  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260618"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260618r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654080</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the passwd command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64255r953666_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "passwd" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-passwd  
    
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64255r953666_fix" /><check system="C-64347r953665_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that an audit event is generated for any successful/unsuccessful use of the "passwd" command by using the following command:   
  
     $ sudo auditctl -l | grep -w passwd 
     -a always,exit -S all -F path=/usr/bin/passwd -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-passwd  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.</check-content></check></Rule></Group><Group id="V-260619"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260619r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654085</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the setfacl command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64256r953669_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "setfacl" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid&gt;=1000 -F auid!=unset -k perm_chng  
    
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64256r953669_fix" /><check system="C-64348r953668_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful attempts to use the "setfacl" command by using the following command:  
  
     $ sudo auditctl -l | grep setfacl 
     -a always,exit -S all -F path=/usr/bin/setfacl -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=perm_chng  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260620"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260620r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654090</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the ssh-agent command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64257r953672_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "ssh-agent" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-ssh  
  
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64257r953672_fix" /><check system="C-64349r953671_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful attempts to use the "ssh-agent" command by using the following command:  
  
     $ sudo auditctl -l | grep /usr/bin/ssh-agent 
     -a always,exit -S all -F path=/usr/bin/ssh-agent -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-ssh  
  
If the command does not return lines that match the example or the lines are commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260621"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260621r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654095</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the ssh-keysign command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64258r953675_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "ssh-keysign" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-ssh  
  
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64258r953675_fix" /><check system="C-64350r953674_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful attempts to use the "ssh-keysign" command by using the following command: 
  
     $ sudo auditctl -l | grep ssh-keysign 
     -a always,exit -S all -F path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-ssh  
  
If the command does not return lines that match the example or the lines are commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260622"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260622r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654100</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the su command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64259r953678_fix">Configure Ubuntu 22.04 LTS to generate audit records when successful/unsuccessful attempts to use the "su" command occur.  
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/bin/su -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-priv_change   
  
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64259r953678_fix" /><check system="C-64351r953677_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records upon successful/unsuccessful attempts to use the "su" command by using the following command:  
  
     $ sudo auditctl -l | grep /bin/su 
     -a always,exit -S all -F path=/bin/su -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-priv_change  
  
If the command does not return lines that match the example or the lines are commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260623"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260623r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654105</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the sudo command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64260r953681_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "sudo" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid&gt;=1000 -F auid!=unset -k priv_cmd  
    
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64260r953681_fix" /><check system="C-64352r953680_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that an audit event is generated for any successful/unsuccessful use of the "sudo" command by using the following command: 
  
     $ sudo auditctl -l | grep /usr/bin/sudo  
     -a always,exit -S all -F path=/usr/bin/sudo -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=priv_cmd  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260624"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260624r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654110</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the sudoedit command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64261r953684_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "sudoedit" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules":  
  
-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid&gt;=1000 -F auid!=unset -k priv_cmd  
    
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64261r953684_fix" /><check system="C-64353r953683_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful attempts to use the "sudoedit" command by using the following command:  
  
     $ sudo auditctl -l | grep /usr/bin/sudoedit 
     -a always,exit -S all -F path=/usr/bin/sudoedit -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=priv_cmd  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260625"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260625r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654115</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the umount command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64262r953687_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "umount" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/bin/umount -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-umount  
  
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64262r953687_fix" /><check system="C-64354r953686_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify if Ubuntu 22.04 LTS generates audit records upon successful/unsuccessful attempts to use the "umount" command by using the following command:  
  
     $ sudo auditctl -l | grep /usr/bin/umount 
     -a always,exit -S all -F path=/usr/bin/umount -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-umount  
  
If the command does not return lines that match the example or the lines are commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260626"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260626r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654120</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the unix_update command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64263r953690_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "unix_update" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/sbin/unix_update -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-unix-update  
   
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64263r953690_fix" /><check system="C-64355r953689_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that an audit event is generated for any successful/unsuccessful use of the "unix_update" command by using the following command:   
  
     $ sudo auditctl -l | grep -w unix_update 
     -a always,exit -S all -F path=/sbin/unix_update -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-unix-update  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260627"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260627r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654125</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the usermod command.</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).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64264r953693_fix">Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "usermod" command.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid&gt;=1000 -F auid!=unset -k privileged-usermod 
    
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64264r953693_fix" /><check system="C-64356r953692_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify that an audit event is generated for any successful/unsuccessful use of the "usermod" command by using the following command:  
  
     $ sudo auditctl -l | grep -w usermod 
     -a always,exit -S all -F path=/usr/sbin/usermod -F perm=x -F auid&gt;=1000 -F auid!=-1 -F key=privileged-usermod  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260628"><title>SRG-OS-000004-GPOS-00004</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260628r958368_rule" weight="10.0" severity="medium"><version>UBTU-22-654130</version><title>Ubuntu 22.04 LTS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group.</title><description>&lt;VulnDiscussion&gt;Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.  
  
To address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.

Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000018</ident><ident system="http://cyber.mil/cci">CCI-000172</ident><ident system="http://cyber.mil/cci">CCI-001403</ident><ident system="http://cyber.mil/cci">CCI-001404</ident><ident system="http://cyber.mil/cci">CCI-001405</ident><ident system="http://cyber.mil/cci">CCI-002130</ident><fixtext fixref="F-64265r953696_fix">Configure Ubuntu 22.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group". 
 
Add or modify the following line to "/etc/audit/rules.d/stig.rules": 
 
-w /etc/group -p wa -k usergroup_modification 
 
To reload the rules file, issue the following command: 
 
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64265r953696_fix" /><check system="C-64357r953695_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group" by using the following command: 
 
     $ sudo auditctl -l | grep group 
     -w /etc/group -p wa -k usergroup_modification 
 
If the command does not return a line that matches the example or the line is commented out, this is a finding. 
 
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260629"><title>SRG-OS-000004-GPOS-00004</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260629r958368_rule" weight="10.0" severity="medium"><version>UBTU-22-654135</version><title>Ubuntu 22.04 LTS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow.</title><description>&lt;VulnDiscussion&gt;Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.  
  
To address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.

Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000018</ident><ident system="http://cyber.mil/cci">CCI-000172</ident><ident system="http://cyber.mil/cci">CCI-001403</ident><ident system="http://cyber.mil/cci">CCI-001404</ident><ident system="http://cyber.mil/cci">CCI-001405</ident><ident system="http://cyber.mil/cci">CCI-002130</ident><fixtext fixref="F-64266r953699_fix">Configure Ubuntu 22.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow".  
 
Add or modify the following line to "/etc/audit/rules.d/stig.rules": 
 
-w /etc/gshadow -p wa -k usergroup_modification 
 
To reload the rules file, issue the following command: 
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64266r953699_fix" /><check system="C-64358r953698_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow" by using the following command: 
 
     $ sudo auditctl -l | grep gshadow 
     -w /etc/gshadow -p wa -k usergroup_modification 
 
If the command does not return a line that matches the example or the line is commented out, this is a finding. 
 
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260630"><title>SRG-OS-000004-GPOS-00004</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260630r958368_rule" weight="10.0" severity="medium"><version>UBTU-22-654140</version><title>Ubuntu 22.04 LTS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd.</title><description>&lt;VulnDiscussion&gt;Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.  
  
To address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.

Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000018</ident><ident system="http://cyber.mil/cci">CCI-000172</ident><ident system="http://cyber.mil/cci">CCI-001403</ident><ident system="http://cyber.mil/cci">CCI-001404</ident><ident system="http://cyber.mil/cci">CCI-001405</ident><ident system="http://cyber.mil/cci">CCI-002130</ident><fixtext fixref="F-64267r953702_fix">Configure Ubuntu 22.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd". 
 
Add or modify the following line to "/etc/audit/rules.d/stig.rules": 
 
-w /etc/security/opasswd -p wa -k usergroup_modification 
 
To reload the rules file, issue the following command: 
 
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64267r953702_fix" /><check system="C-64359r953701_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd" by using the following command: 
 
     $ sudo auditctl -l | grep opasswd 
     -w /etc/security/opasswd -p wa -k usergroup_modification 
 
If the command does not return a line that matches the example or the line is commented out, this is a finding. 
 
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260631"><title>SRG-OS-000004-GPOS-00004</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260631r958368_rule" weight="10.0" severity="medium"><version>UBTU-22-654145</version><title>Ubuntu 22.04 LTS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd.</title><description>&lt;VulnDiscussion&gt;Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.  
  
To address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.

Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000018</ident><ident system="http://cyber.mil/cci">CCI-000172</ident><ident system="http://cyber.mil/cci">CCI-001403</ident><ident system="http://cyber.mil/cci">CCI-001404</ident><ident system="http://cyber.mil/cci">CCI-001405</ident><ident system="http://cyber.mil/cci">CCI-002130</ident><fixtext fixref="F-64268r953705_fix">Configure Ubuntu 22.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd". 
 
Add or modify the following line to "/etc/audit/rules.d/stig.rules": 
 
-w /etc/passwd -p wa -k usergroup_modification 
 
To reload the rules file, issue the following command: 
 
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64268r953705_fix" /><check system="C-64360r953704_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd" by using the following command: 
 
     $ sudo auditctl -l | grep passwd 
     -w /etc/passwd -p wa -k usergroup_modification 
 
If the command does not return a line that matches the example or the line is commented out, this is a finding. 
 
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260632"><title>SRG-OS-000004-GPOS-00004</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260632r958368_rule" weight="10.0" severity="medium"><version>UBTU-22-654150</version><title>Ubuntu 22.04 LTS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.</title><description>&lt;VulnDiscussion&gt;Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.  
  
To address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.

Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000018</ident><ident system="http://cyber.mil/cci">CCI-000172</ident><ident system="http://cyber.mil/cci">CCI-001403</ident><ident system="http://cyber.mil/cci">CCI-001404</ident><ident system="http://cyber.mil/cci">CCI-001405</ident><ident system="http://cyber.mil/cci">CCI-002130</ident><fixtext fixref="F-64269r953708_fix">Configure Ubuntu 22.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/shadow".  
 
Add or modify the following line to "/etc/audit/rules.d/stig.rules": 
 
-w /etc/shadow -p wa -k usergroup_modification 
 
To reload the rules file, issue the following command: 
 
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64269r953708_fix" /><check system="C-64361r953707_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/shadow" by using the following command: 
 
     $ sudo auditctl -l | grep shadow 
     -w /etc/shadow -p wa -k usergroup_modification 
 
If the command does not return a line that matches the example or the line is commented out, this is a finding. 
 
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260633"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260633r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654155</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the chmod, fchmod, and fchmodat system calls.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident 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 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 absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.

Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64270r953711_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chmod", "fchmod", and "fchmodat" system calls.  
  
Add or modify the following lines in the "/etc/audit/rules.d/stig.rules":  
  
-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_chng 
-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid&gt;=1000 -F auid!=unset -k perm_chng 
 
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64270r953711_fix" /><check system="C-64362r953710_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful attempts to use the "chmod", "fchmod", and "fchmodat" system calls by using the following command:  
  
     $ sudo auditctl -l | grep chmod 
     -a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid&gt;=1000 -F auid!=-1 -F key=perm_chng  
     -a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid&gt;=1000 -F auid!=-1 -F key=perm_chng  
  
If the command does not return audit rules for the "chmod", "fchmod" and "fchmodat" syscalls or the lines are commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260634"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260634r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654160</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the chown, fchown, fchownat, and lchown system calls.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident 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 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 absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.

Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64271r953714_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chown", "fchown", "fchownat", and "lchown" system calls.  
  
Add or modify the following lines in the "/etc/audit/rules.d/stig.rules":  
  
-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid&gt;=1000 -F auid!=unset -k perm_chng  
-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid&gt;=1000 -F auid!=unset -k perm_chng  
  
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64271r953714_fix" /><check system="C-64363r953713_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful attempts to use the "chown", "fchown", "fchownat", and "lchown" system calls by using the following command: 
  
     $ sudo auditctl -l | grep chown  
     -a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid&gt;=1000 -F auid!=-1 -F key=perm_chng  
     -a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid&gt;=1000 -F auid!=-1 -F key=perm_chng  
  
If the command does not return audit rules for the "chown", "fchown", "fchownat", and "lchown" syscalls or the lines are commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260635"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260635r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654165</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the creat, open, openat, open_by_handle_at, truncate, and ftruncate system calls.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident 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 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 absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.

Satisfies: SRG-OS-000064-GPOS-00033, 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64272r953717_fix">Configure the audit system to generate an audit event for any unsuccessful use of the "creat", "open", "openat", "open_by_handle_at", "truncate", and "ftruncate" system calls.   
  
Add or modify the following lines in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access  
-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access  
-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=unset -k perm_access  
-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=unset -k perm_access  
  
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64272r953717_fix" /><check system="C-64364r953716_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon unsuccessful attempts to use the "creat", "open", "openat", "open_by_handle_at", "truncate", and "ftruncate" system calls by using the following command:  
  
     $ sudo auditctl -l | grep 'open\|truncate\|creat'  
     -a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=-1 -F key=perm_access  
     -a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=-1 -F key=perm_access  
     -a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=-1 -F key=perm_access  
     -a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=-1 -F key=perm_access   
  
If the command does not return audit rules for the "creat", "open", "openat", "open_by_handle_at", "truncate", and "ftruncate" syscalls or the lines are commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260636"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260636r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654170</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the delete_module system call.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.  
 
Audit records can be generated from various components within the information system (e.g., module or policy filter).

Satisfies: SRG-OS-000064-GPOS-00033, 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64273r953720_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "delete_module" syscall.   
  
Add or modify the following lines in the "/etc/audit/rules.d/stig.rules" file:  
  
-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  
 
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64273r953720_fix" /><check system="C-64365r953719_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record for any successful/unsuccessful attempts to use the "delete_module" syscall by using the following command:  
  
     $ sudo auditctl -l | grep -w delete_module  
     -a always,exit -F arch=b32 -S delete_module -F auid&gt;=1000 -F auid!=-1 -F key=module_chng  
     -a always,exit -F arch=b64 -S delete_module -F auid&gt;=1000 -F auid!=-1 -F key=module_chng  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260637"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260637r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654175</version><title>Ubuntu 22.04 LTS must generate audit records for successful/unsuccessful uses of the init_module and finit_module 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). 
 
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 absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.

Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000471-GPOS-00216&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64274r953723_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "init_module" and "finit_module" syscalls.   
  
Add or modify the following lines in the "/etc/audit/rules.d/stig.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  
 
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64274r953723_fix" /><check system="C-64366r953722_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record for any successful/unsuccessful attempts to use the "init_module" and "finit_module" syscalls by using the following command:   
  
     $ sudo auditctl -l | grep init_module  
     -a always,exit -F arch=b32 -S init_module,finit_module -F auid&gt;=1000 -F auid!=-1 -F key=module_chng  
     -a always,exit -F arch=b64 -S init_module,finit_module -F auid&gt;=1000 -F auid!=-1 -F key=module_chng   
  
If the command does not return audit rules for the "init_module" and "finit_module" syscalls or the lines are commented out, this is a finding. 
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260638"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260638r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654180</version><title>Ubuntu 22.04 LTS must generate audit records for any use of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident 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 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 absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.

Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64275r953726_fix">Configure the audit system to generate an audit event for any successful/unsuccessful use of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls.  
  
Add or modify the following lines in the "/etc/audit/rules.d/stig.rules" file:  
  
-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=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&gt;=1000 -F auid!=unset -k perm_mod  
-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod   
  
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64275r953726_fix" /><check system="C-64367r953725_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful attempts to use the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls by using the following command:  
  
     $ sudo auditctl -l | grep xattr  
     -a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid&gt;=1000 -F auid!=-1 -F key=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&gt;=1000 -F auid!=-1 -F key=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 audit rules for the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr" and "lremovexattr" syscalls or the lines are commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260639"><title>SRG-OS-000468-GPOS-00212</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260639r991577_rule" weight="10.0" severity="medium"><version>UBTU-22-654185</version><title>Ubuntu 22.04 LTS must generate audit records for any successful/unsuccessful use of unlink, unlinkat, rename, renameat, and rmdir system calls.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident 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 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 absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64276r953729_fix">Configure the audit system to generate audit events for any successful/unsuccessful use of "unlink", "unlinkat", "rename", "renameat", and "rmdir" system calls.  
  
Add or modify the following lines in the "/etc/audit/rules.d/stig.rules" file: 
  
-a always,exit -F arch=b64 -S unlink,unlinkat,rename,renameat,rmdir -F auid&gt;=1000 -F auid!=unset -k delete  
-a always,exit -F arch=b32 -S unlink,unlinkat,rename,renameat,rmdir -F auid&gt;=1000 -F auid!=unset -k delete  
 
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64276r953729_fix" /><check system="C-64368r953728_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records for any successful/unsuccessful use of "unlink", "unlinkat", "rename", "renameat", and "rmdir" system calls by using the following command: 
  
     $ sudo auditctl -l | grep 'unlink\|rename\|rmdir'  
     -a always,exit -F arch=b64 -S unlink,unlinkat,rename,renameat,rmdir -F auid&gt;=1000 -F auid!=-1 -F key=delete  
     -a always,exit -F arch=b32 -S unlink,unlinkat,rename,renameat,rmdir -F auid&gt;=1000 -F auid!=-1 -F key=delete  
  
If the command does not return audit rules for the "unlink", "unlinkat", "rename", "renameat", and "rmdir" syscalls or the lines are commented out, this is a finding.  
  
Note: The "key" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.</check-content></check></Rule></Group><Group id="V-260640"><title>SRG-OS-000480-GPOS-00227</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260640r991589_rule" weight="10.0" severity="medium"><version>UBTU-22-654190</version><title>Ubuntu 22.04 LTS must generate audit records for all events that affect the systemd journal files.</title><description>&lt;VulnDiscussion&gt;Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to modify system level binaries and their operation. Auditing the systemd journal files provides logging that can be used for forensic purposes. 
  
To address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-64277r953732_fix">Configure Ubuntu 22.04 LTS to generate audit records for events that affect "/var/log/journal".  
  
Add or modify the following line to "/etc/audit/rules.d/stig.rules":  
  
-w /var/log/journal -p wa -k systemd_journal  
   
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64277r953732_fix" /><check system="C-64369r953731_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records for all events that affect "/var/log/journal" by using the following command:  
  
     $ sudo auditctl -l | grep journal  
     -w /var/log/journal -p wa -k systemd_journal  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260641"><title>SRG-OS-000472-GPOS-00217</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260641r991581_rule" weight="10.0" severity="medium"><version>UBTU-22-654195</version><title>Ubuntu 22.04 LTS must generate audit records for the /var/log/btmp file.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.  
  
Audit records can be generated from various components within the information system (e.g., module or policy filter).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64278r953735_fix">Configure the audit system to generate audit events showing start and stop times for user access via the "/var/log/btmp file".  
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-w /var/log/btmp -p wa -k logins  
   
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64278r953735_fix" /><check system="C-64370r953734_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records showing start and stop times for user access to the system via the "/var/log/btmp" file by using the following command:  
  
     $ sudo auditctl -l | grep '/var/log/btmp'  
     -w /var/log/btmp -p wa -k logins  
  
If the command does not return a line matching the example or the line is commented out, this is a finding.  
  
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260642"><title>SRG-OS-000472-GPOS-00217</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260642r991581_rule" weight="10.0" severity="medium"><version>UBTU-22-654200</version><title>Ubuntu 22.04 LTS must generate audit records for the /var/log/wtmp file.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.  
  
Audit records can be generated from various components within the information system (e.g., module or policy filter).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64279r953738_fix">Configure the audit system to generate audit events showing start and stop times for user access via the "/var/log/wtmp" file.  
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-w /var/log/wtmp -p wa -k logins  
   
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64279r953738_fix" /><check system="C-64371r953737_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records showing start and stop times for user access to the system via the "/var/log/wtmp" file by using the following command:   
  
     $ sudo auditctl -l | grep '/var/log/wtmp'  
     -w /var/log/wtmp -p wa -k logins  
  
If the command does not return a line matching the example or the line is commented out, this is a finding.  
  
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260643"><title>SRG-OS-000472-GPOS-00217</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260643r991581_rule" weight="10.0" severity="medium"><version>UBTU-22-654205</version><title>Ubuntu 22.04 LTS must generate audit records for the /var/run/utmp file.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.  
  
Audit records can be generated from various components within the information system (e.g., module or policy filter).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64280r953741_fix">Configure the audit system to generate audit events showing start and stop times for user access via the "/var/run/utmp" file.  
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-w /var/run/utmp -p wa -k logins  
   
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64280r953741_fix" /><check system="C-64372r953740_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records showing start and stop times for user access to the system via the "/var/run/utmp" file by using the following command: 
  
     $ sudo auditctl -l | grep '/var/run/utmp'  
     -w /var/run/utmp -p wa -k logins  
  
If the command does not return a line matching the example or the line is commented out, this is a finding.  
  
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260644"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260644r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654210</version><title>Ubuntu 22.04 LTS must generate audit records for the use and modification of faillog file.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.  
  
Audit records can be generated from various components within the information system (e.g., module or policy filter).

Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000470-GPOS-00214, 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64281r953744_fix">Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the "faillog" file.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-w /var/log/faillog -p wa -k logins  
    
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64281r953744_fix" /><check system="C-64373r953743_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record upon successful/unsuccessful modifications to the "faillog" file by using the following command: 
  
     $ sudo auditctl -l | grep faillog  
     -w /var/log/faillog -p wa -k logins  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260645"><title>SRG-OS-000064-GPOS-00033</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260645r958446_rule" weight="10.0" severity="medium"><version>UBTU-22-654215</version><title>Ubuntu 22.04 LTS must generate audit records for the use and modification of the lastlog file.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.  
  
Audit records can be generated from various components within the information system (e.g., module or policy filter).

Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000470-GPOS-00214, 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;</description><reference><dc:title>DPMS Target Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64282r953747_fix">Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the "lastlog" file.   
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-w /var/log/lastlog -p wa -k logins  
   
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64282r953747_fix" /><check system="C-64374r953746_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates an audit record when successful/unsuccessful modifications to the "lastlog" file occur by using the following command:   
  
     $ sudo auditctl -l | grep lastlog  
     -w /var/log/lastlog -p wa -k logins  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260646"><title>SRG-OS-000466-GPOS-00210</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260646r991575_rule" weight="10.0" severity="medium"><version>UBTU-22-654220</version><title>Ubuntu 22.04 LTS must generate audit records when successful/unsuccessful attempts to modify the /etc/sudoers file occur.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. 
 
Audit records can be generated from various components within the information system (e.g., module or policy filter).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64283r953750_fix">Configure Ubuntu 22.04 LTS to generate audit records for all modifications that affect "/etc/sudoers".   
 
Add or modify the following line to "/etc/audit/rules.d/stig.rules":  
 
-w /etc/sudoers -p wa -k privilege_modification  
 
To reload the rules file, issue the following command:  
 
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64283r953750_fix" /><check system="C-64375r953749_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records for all modifications that affect "/etc/sudoers" by using the following command:  
  
     $ sudo auditctl -l | grep sudoers  
     -w /etc/sudoers -p wa -k privilege_modification  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260647"><title>SRG-OS-000466-GPOS-00210</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260647r991575_rule" weight="10.0" severity="medium"><version>UBTU-22-654225</version><title>Ubuntu 22.04 LTS must generate audit records when successful/unsuccessful attempts to modify the /etc/sudoers.d directory occur.</title><description>&lt;VulnDiscussion&gt;Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. 
 
Audit records can be generated from various components within the information system (e.g., module or policy filter).&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><fixtext fixref="F-64284r953753_fix">Configure Ubuntu 22.04 LTS to generate audit records for all modifications that affect "/etc/sudoers.d" directory.   
 
Add or modify the following line to "/etc/audit/rules.d/stig.rules":  
 
-w /etc/sudoers.d -p wa -k privilege_modification  
 
To reload the rules file, issue the following command:  
 
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation.  he &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64284r953753_fix" /><check system="C-64376r953752_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS generates audit records for all modifications that affect "/etc/sudoers.d" directory by using the following command:   
  
     $ sudo auditctl -l | grep sudoers.d  
     -w /etc/sudoers.d -p wa -k privilege_modification  
  
If the command does not return a line that matches the example or the line is commented out, this is a finding.  
  
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260648"><title>SRG-OS-000326-GPOS-00126</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260648r958730_rule" weight="10.0" severity="medium"><version>UBTU-22-654230</version><title>Ubuntu 22.04 LTS must prevent all software from executing at higher privilege levels than users executing the software and the audit system must be configured to audit the execution of privileged functions.</title><description>&lt;VulnDiscussion&gt;In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by the organizations.  
  
Some programs and processes are required to operate at a higher privilege level and therefore should be excluded from the organization-defined software list after review.

Satisfies: SRG-OS-000326-GPOS-00126, SRG-OS-000327-GPOS-00127&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002233</ident><ident system="http://cyber.mil/cci">CCI-002234</ident><fixtext fixref="F-64285r953756_fix">Configure Ubuntu 22.04 LTS to audit the execution of all privileged functions.  
  
Add or modify the following lines in the "/etc/audit/rules.d/stig.rules" file:  
  
-a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k execpriv 
-a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k execpriv 
-a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k execpriv 
-a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k execpriv 
 
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64285r953756_fix" /><check system="C-64377r953755_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS audits the execution of privilege functions by auditing the "execve" system call by using the following command:  
  
     $ sudo auditctl -l | grep execve 
     -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -F key=execpriv 
     -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -F key=execpriv 
     -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -F key=execpriv 
     -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -F key=execpriv 
  
If the command does not return lines that match the example or the lines are commented out, this is a finding.  
  
Note: The "key=" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260649"><title>SRG-OS-000392-GPOS-00172</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260649r986298_rule" weight="10.0" severity="medium"><version>UBTU-22-654235</version><title>Ubuntu 22.04 LTS must generate audit records for privileged activities, nonlocal maintenance, diagnostic sessions and other system-level access.</title><description>&lt;VulnDiscussion&gt;If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available.  
  
This requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.  
  
Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection.  
  
This requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch.

Satisfies: SRG-OS-000392-GPOS-00172, 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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-000172</ident><ident system="http://cyber.mil/cci">CCI-002884</ident><ident system="http://cyber.mil/cci">CCI-004188</ident><fixtext fixref="F-64286r953759_fix">Configure Ubuntu 22.04 LTS to audit activities performed during nonlocal maintenance and diagnostic sessions.  
  
Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file:  
  
-w /var/log/sudo.log -p wa -k maintenance  
   
To reload the rules file, issue the following command:  
  
     $ sudo augenrules --load 
 
Note: The "-k &lt;keyname&gt;" at the end of the line gives the rule a unique meaning to help during an audit investigation. The &lt;keyname&gt; does not need to match the example above.</fixtext><fix id="F-64286r953759_fix" /><check system="C-64378r953758_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify Ubuntu 22.04 LTS audits activities performed during nonlocal maintenance and diagnostic sessions by using the following command:  
  
     $ sudo auditctl -l | grep sudo.log  
     -w /var/log/sudo.log -p wa -k maintenance  
  
If the command does not return lines that match the example or the lines are commented out, this is a finding.  
  
Note: The "-k" value is arbitrary and can be different from the example output above.</check-content></check></Rule></Group><Group id="V-260650"><title>SRG-OS-000396-GPOS-00176</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-260650r987791_rule" weight="10.0" severity="high"><version>UBTU-22-671010</version><title>Ubuntu 22.04 LTS must implement NIST FIPS-validated cryptography to protect classified information and for the following: To provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.</title><description>&lt;VulnDiscussion&gt;Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The operating system must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.

Satisfies: SRG-OS-000396-GPOS-00176, SRG-OS-000478-GPOS-00223&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 Canonical Ubuntu 22.04 LTS</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Canonical Ubuntu 22.04 LTS</dc:subject><dc:identifier>5594</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002450</ident><fixtext fixref="F-64287r953762_fix">Configure Ubuntu 22.04 LTS to run in FIPS mode. Add "fips=1" to the kernel parameter during Ubuntu 22.04 LTS install.  
  
Enabling a FIPS mode on a pre-existing system involves a number of modifications to Ubuntu 22.04 LTS. Refer to the Ubuntu Pro security certification documentation for instructions.   
  
A subscription to the "Ubuntu Pro" plan is required to obtain the FIPS Kernel cryptographic modules and enable FIPS. 
 
Note: Ubuntu Pro security certification instructions can be found at: https://ubuntu.com/security/certifications/docs/fips-enablement</fixtext><fix id="F-64287r953762_fix" /><check system="C-64379r953761_chk"><check-content-ref href="Canonical_Ubuntu_22.04_LTS_STIG.xml" name="M" /><check-content>Verify the system is configured to run in FIPS mode by using the following command:  
  
     $ grep -i 1 /proc/sys/crypto/fips_enabled 
     1  
  
If a value of "1" is not returned, this is a finding.</check-content></check></Rule></Group></Benchmark>