From dccce1d5cc06985a58f0ecba4fd0d977388592b2 Mon Sep 17 00:00:00 2001
From: Major Hayden <major@mhtx.net>
Date: Tue, 4 Apr 2017 07:22:01 -0500
Subject: [PATCH] Handle RHEL 7 STIG renumbering

This patch gets the docs adjusted to work with the new RHEL 7 STIG
version 1 release. The new STIG release has changed all of the
numbering, but it maintains a link to (most) of the old STIG IDs in
the XML.

Closes-bug: 1676865
Change-Id: I65023fe63163c9804a3aec9dcdbf23c69bedb604
---
 defaults/main.yml                             |   296 +-
 ...prise_Linux_7_STIG_V1R0-2_Manual-xccdf.xml | 10364 -------------
 ...erprise_Linux_7_STIG_V1R1_Manual-xccdf.xml | 12082 ++++++++++++++++
 doc/metadata/rhel7/RHEL-07-010031.rst         |     9 -
 doc/metadata/rhel7/RHEL-07-010070.rst         |    15 -
 doc/metadata/rhel7/RHEL-07-010071.rst         |    15 -
 doc/metadata/rhel7/RHEL-07-010373.rst         |     9 -
 doc/metadata/rhel7/RHEL-07-010400.rst         |    14 -
 doc/metadata/rhel7/RHEL-07-010401.rst         |    14 -
 doc/metadata/rhel7/RHEL-07-010440.rst         |     8 -
 doc/metadata/rhel7/RHEL-07-010470.rst         |    10 -
 doc/metadata/rhel7/RHEL-07-010490.rst         |    10 -
 doc/metadata/rhel7/RHEL-07-020170.rst         |     9 -
 doc/metadata/rhel7/RHEL-07-020870.rst         |     8 -
 doc/metadata/rhel7/RHEL-07-040020.rst         |    10 -
 doc/metadata/rhel7/RHEL-07-040030.rst         |    13 -
 doc/metadata/rhel7/RHEL-07-040040.rst         |    12 -
 doc/metadata/rhel7/RHEL-07-040050.rst         |    11 -
 doc/metadata/rhel7/RHEL-07-040060.rst         |     9 -
 doc/metadata/rhel7/RHEL-07-040070.rst         |     8 -
 doc/metadata/rhel7/RHEL-07-040080.rst         |     8 -
 doc/metadata/rhel7/RHEL-07-040230.rst         |    17 -
 doc/metadata/rhel7/RHEL-07-040333.rst         |     7 -
 doc/metadata/rhel7/RHEL-07-040490.rst         |    14 -
 doc/metadata/rhel7/RHEL-07-040810.rst         |    10 -
 .../rhel7/{RHEL-07-010010.rst => V-71849.rst} |     2 +-
 .../rhel7/{RHEL-07-010020.rst => V-71855.rst} |     2 +-
 .../rhel7/{RHEL-07-010030.rst => V-71859.rst} |     2 +-
 .../rhel7/{RHEL-07-010040.rst => V-71861.rst} |     4 +-
 doc/metadata/rhel7/V-71863.rst                |     9 +
 .../rhel7/{RHEL-07-010060.rst => V-71891.rst} |     2 +-
 .../rhel7/{RHEL-07-010073.rst => V-71893.rst} |     2 +-
 doc/metadata/rhel7/V-71895.rst                |    10 +
 .../rhel7/{RHEL-07-010072.rst => V-71897.rst} |     2 +-
 doc/metadata/rhel7/V-71899.rst                |    10 +
 .../rhel7/{RHEL-07-010074.rst => V-71901.rst} |     2 +-
 .../rhel7/{RHEL-07-010090.rst => V-71903.rst} |     2 +-
 .../rhel7/{RHEL-07-010100.rst => V-71905.rst} |     2 +-
 .../rhel7/{RHEL-07-010110.rst => V-71907.rst} |     2 +-
 .../rhel7/{RHEL-07-010120.rst => V-71909.rst} |     2 +-
 .../rhel7/{RHEL-07-010130.rst => V-71911.rst} |     2 +-
 .../rhel7/{RHEL-07-010140.rst => V-71913.rst} |     2 +-
 .../rhel7/{RHEL-07-010150.rst => V-71915.rst} |     2 +-
 .../rhel7/{RHEL-07-010160.rst => V-71917.rst} |     2 +-
 .../rhel7/{RHEL-07-010170.rst => V-71919.rst} |     2 +-
 .../rhel7/{RHEL-07-010180.rst => V-71921.rst} |     2 +-
 .../rhel7/{RHEL-07-010190.rst => V-71923.rst} |     2 +-
 .../rhel7/{RHEL-07-010200.rst => V-71925.rst} |     2 +-
 .../rhel7/{RHEL-07-010210.rst => V-71927.rst} |     2 +-
 .../rhel7/{RHEL-07-010220.rst => V-71929.rst} |     2 +-
 .../rhel7/{RHEL-07-010230.rst => V-71931.rst} |     2 +-
 .../rhel7/{RHEL-07-010240.rst => V-71933.rst} |     2 +-
 .../rhel7/{RHEL-07-010250.rst => V-71935.rst} |     2 +-
 .../rhel7/{RHEL-07-010260.rst => V-71937.rst} |     2 +-
 .../rhel7/{RHEL-07-010270.rst => V-71939.rst} |     2 +-
 .../rhel7/{RHEL-07-010280.rst => V-71941.rst} |     2 +-
 .../rhel7/{RHEL-07-010372.rst => V-71943.rst} |     4 +-
 .../rhel7/{RHEL-07-010371.rst => V-71945.rst} |     2 +-
 .../rhel7/{RHEL-07-010380.rst => V-71947.rst} |     2 +-
 .../rhel7/{RHEL-07-010381.rst => V-71949.rst} |     2 +-
 .../rhel7/{RHEL-07-010420.rst => V-71951.rst} |     2 +-
 .../rhel7/{RHEL-07-010430.rst => V-71953.rst} |     2 +-
 .../rhel7/{RHEL-07-010431.rst => V-71955.rst} |     2 +-
 .../rhel7/{RHEL-07-010441.rst => V-71957.rst} |     2 +-
 .../rhel7/{RHEL-07-010442.rst => V-71959.rst} |     2 +-
 .../rhel7/{RHEL-07-010460.rst => V-71961.rst} |     2 +-
 doc/metadata/rhel7/V-71963.rst                |    10 +
 .../rhel7/{RHEL-07-010500.rst => V-71965.rst} |     2 +-
 .../rhel7/{RHEL-07-020000.rst => V-71967.rst} |     2 +-
 .../rhel7/{RHEL-07-020010.rst => V-71969.rst} |     2 +-
 .../rhel7/{RHEL-07-020090.rst => V-71971.rst} |     2 +-
 .../rhel7/{RHEL-07-020130.rst => V-71973.rst} |     2 +-
 .../rhel7/{RHEL-07-020140.rst => V-71975.rst} |     2 +-
 .../rhel7/{RHEL-07-020150.rst => V-71977.rst} |     2 +-
 .../rhel7/{RHEL-07-020151.rst => V-71979.rst} |     2 +-
 .../rhel7/{RHEL-07-020152.rst => V-71981.rst} |     4 +-
 .../rhel7/{RHEL-07-020160.rst => V-71983.rst} |     2 +-
 .../rhel7/{RHEL-07-020161.rst => V-71985.rst} |     2 +-
 .../rhel7/{RHEL-07-020200.rst => V-71987.rst} |     2 +-
 .../rhel7/{RHEL-07-020210.rst => V-71989.rst} |     2 +-
 .../rhel7/{RHEL-07-020211.rst => V-71991.rst} |     4 +-
 .../rhel7/{RHEL-07-020220.rst => V-71993.rst} |     2 +-
 .../rhel7/{RHEL-07-020230.rst => V-71995.rst} |     2 +-
 .../rhel7/{RHEL-07-020240.rst => V-71997.rst} |     2 +-
 .../rhel7/{RHEL-07-020250.rst => V-71999.rst} |     2 +-
 .../rhel7/{RHEL-07-020290.rst => V-72001.rst} |     2 +-
 .../rhel7/{RHEL-07-020300.rst => V-72003.rst} |     2 +-
 .../rhel7/{RHEL-07-020310.rst => V-72005.rst} |     2 +-
 .../rhel7/{RHEL-07-020360.rst => V-72007.rst} |     2 +-
 .../rhel7/{RHEL-07-020370.rst => V-72009.rst} |     2 +-
 .../rhel7/{RHEL-07-020620.rst => V-72011.rst} |     2 +-
 .../rhel7/{RHEL-07-020630.rst => V-72013.rst} |     2 +-
 .../rhel7/{RHEL-07-020640.rst => V-72015.rst} |     2 +-
 .../rhel7/{RHEL-07-020650.rst => V-72017.rst} |     2 +-
 .../rhel7/{RHEL-07-020660.rst => V-72019.rst} |     4 +-
 .../rhel7/{RHEL-07-020670.rst => V-72021.rst} |     4 +-
 .../rhel7/{RHEL-07-020700.rst => V-72023.rst} |     2 +-
 .../rhel7/{RHEL-07-020680.rst => V-72025.rst} |     2 +-
 .../rhel7/{RHEL-07-020690.rst => V-72027.rst} |     2 +-
 .../rhel7/{RHEL-07-020850.rst => V-72029.rst} |     2 +-
 .../rhel7/{RHEL-07-020860.rst => V-72031.rst} |     2 +-
 .../rhel7/{RHEL-07-020840.rst => V-72033.rst} |     2 +-
 doc/metadata/rhel7/V-72035.rst                |    10 +
 .../rhel7/{RHEL-07-020880.rst => V-72037.rst} |     2 +-
 .../rhel7/{RHEL-07-020940.rst => V-72039.rst} |     2 +-
 .../rhel7/{RHEL-07-021010.rst => V-72041.rst} |     2 +-
 .../rhel7/{RHEL-07-021011.rst => V-72043.rst} |     2 +-
 .../rhel7/{RHEL-07-021012.rst => V-72045.rst} |     2 +-
 .../rhel7/{RHEL-07-021050.rst => V-72047.rst} |     2 +-
 .../rhel7/{RHEL-07-021060.rst => V-72049.rst} |     2 +-
 .../rhel7/{RHEL-07-021160.rst => V-72051.rst} |     2 +-
 .../rhel7/{RHEL-07-021190.rst => V-72053.rst} |     2 +-
 .../rhel7/{RHEL-07-021200.rst => V-72055.rst} |     2 +-
 .../rhel7/{RHEL-07-021230.rst => V-72057.rst} |     2 +-
 .../rhel7/{RHEL-07-021240.rst => V-72059.rst} |     2 +-
 .../rhel7/{RHEL-07-021250.rst => V-72061.rst} |     2 +-
 .../rhel7/{RHEL-07-021260.rst => V-72063.rst} |     2 +-
 .../rhel7/{RHEL-07-021270.rst => V-72065.rst} |     2 +-
 .../rhel7/{RHEL-07-021280.rst => V-72067.rst} |     2 +-
 .../rhel7/{RHEL-07-021600.rst => V-72069.rst} |     4 +-
 .../rhel7/{RHEL-07-021610.rst => V-72071.rst} |     4 +-
 .../rhel7/{RHEL-07-021620.rst => V-72073.rst} |     2 +-
 .../rhel7/{RHEL-07-021760.rst => V-72075.rst} |     2 +-
 .../rhel7/{RHEL-07-021910.rst => V-72077.rst} |     2 +-
 .../rhel7/{RHEL-07-030010.rst => V-72079.rst} |     2 +-
 .../rhel7/{RHEL-07-030090.rst => V-72081.rst} |     2 +-
 .../rhel7/{RHEL-07-030330.rst => V-72083.rst} |     2 +-
 .../rhel7/{RHEL-07-030331.rst => V-72085.rst} |     2 +-
 .../rhel7/{RHEL-07-030340.rst => V-72087.rst} |     2 +-
 .../rhel7/{RHEL-07-030350.rst => V-72089.rst} |     2 +-
 .../rhel7/{RHEL-07-030351.rst => V-72091.rst} |     2 +-
 .../rhel7/{RHEL-07-030352.rst => V-72093.rst} |     2 +-
 .../rhel7/{RHEL-07-030310.rst => V-72095.rst} |     2 +-
 .../rhel7/{RHEL-07-030380.rst => V-72097.rst} |     2 +-
 .../rhel7/{RHEL-07-030381.rst => V-72099.rst} |     2 +-
 .../rhel7/{RHEL-07-030382.rst => V-72101.rst} |     2 +-
 .../rhel7/{RHEL-07-030383.rst => V-72103.rst} |     2 +-
 .../rhel7/{RHEL-07-030390.rst => V-72105.rst} |     2 +-
 .../rhel7/{RHEL-07-030391.rst => V-72107.rst} |     2 +-
 .../rhel7/{RHEL-07-030392.rst => V-72109.rst} |     2 +-
 .../rhel7/{RHEL-07-030400.rst => V-72111.rst} |     2 +-
 .../rhel7/{RHEL-07-030401.rst => V-72113.rst} |     2 +-
 .../rhel7/{RHEL-07-030402.rst => V-72115.rst} |     2 +-
 .../rhel7/{RHEL-07-030403.rst => V-72117.rst} |     2 +-
 .../rhel7/{RHEL-07-030404.rst => V-72119.rst} |     2 +-
 .../rhel7/{RHEL-07-030405.rst => V-72121.rst} |     2 +-
 .../rhel7/{RHEL-07-030420.rst => V-72123.rst} |     2 +-
 .../rhel7/{RHEL-07-030421.rst => V-72125.rst} |     2 +-
 .../rhel7/{RHEL-07-030422.rst => V-72127.rst} |     2 +-
 .../rhel7/{RHEL-07-030423.rst => V-72129.rst} |     2 +-
 .../rhel7/{RHEL-07-030424.rst => V-72131.rst} |     2 +-
 .../rhel7/{RHEL-07-030425.rst => V-72133.rst} |     2 +-
 .../rhel7/{RHEL-07-030441.rst => V-72135.rst} |     2 +-
 .../rhel7/{RHEL-07-030442.rst => V-72137.rst} |     2 +-
 .../rhel7/{RHEL-07-030443.rst => V-72139.rst} |     2 +-
 .../rhel7/{RHEL-07-030444.rst => V-72141.rst} |     2 +-
 .../rhel7/{RHEL-07-030490.rst => V-72143.rst} |     2 +-
 .../rhel7/{RHEL-07-030491.rst => V-72145.rst} |     4 +-
 .../rhel7/{RHEL-07-030492.rst => V-72147.rst} |     2 +-
 .../rhel7/{RHEL-07-030510.rst => V-72149.rst} |     2 +-
 .../rhel7/{RHEL-07-030511.rst => V-72151.rst} |     2 +-
 .../rhel7/{RHEL-07-030512.rst => V-72153.rst} |     2 +-
 .../rhel7/{RHEL-07-030513.rst => V-72155.rst} |     2 +-
 .../rhel7/{RHEL-07-030514.rst => V-72157.rst} |     2 +-
 .../rhel7/{RHEL-07-030521.rst => V-72159.rst} |     2 +-
 .../rhel7/{RHEL-07-030522.rst => V-72161.rst} |     2 +-
 .../rhel7/{RHEL-07-030523.rst => V-72163.rst} |     2 +-
 .../rhel7/{RHEL-07-030524.rst => V-72165.rst} |     2 +-
 .../rhel7/{RHEL-07-030525.rst => V-72167.rst} |     2 +-
 .../rhel7/{RHEL-07-030526.rst => V-72169.rst} |     2 +-
 .../rhel7/{RHEL-07-030530.rst => V-72171.rst} |     2 +-
 .../rhel7/{RHEL-07-030531.rst => V-72173.rst} |     2 +-
 .../rhel7/{RHEL-07-030540.rst => V-72175.rst} |     2 +-
 .../rhel7/{RHEL-07-030541.rst => V-72177.rst} |     2 +-
 .../rhel7/{RHEL-07-030550.rst => V-72179.rst} |     2 +-
 .../rhel7/{RHEL-07-030560.rst => V-72181.rst} |     2 +-
 .../rhel7/{RHEL-07-030561.rst => V-72183.rst} |     2 +-
 .../rhel7/{RHEL-07-030630.rst => V-72185.rst} |     2 +-
 .../rhel7/{RHEL-07-030670.rst => V-72187.rst} |     2 +-
 .../rhel7/{RHEL-07-030671.rst => V-72189.rst} |     2 +-
 .../rhel7/{RHEL-07-030672.rst => V-72191.rst} |     2 +-
 .../rhel7/{RHEL-07-030673.rst => V-72193.rst} |     2 +-
 .../rhel7/{RHEL-07-030674.rst => V-72195.rst} |     2 +-
 .../rhel7/{RHEL-07-030710.rst => V-72197.rst} |     2 +-
 .../rhel7/{RHEL-07-030750.rst => V-72199.rst} |     2 +-
 .../rhel7/{RHEL-07-030751.rst => V-72201.rst} |     2 +-
 .../rhel7/{RHEL-07-030752.rst => V-72203.rst} |     2 +-
 .../rhel7/{RHEL-07-030753.rst => V-72205.rst} |     2 +-
 .../rhel7/{RHEL-07-030754.rst => V-72207.rst} |     2 +-
 .../rhel7/{RHEL-07-030770.rst => V-72209.rst} |     2 +-
 .../rhel7/{RHEL-07-030780.rst => V-72211.rst} |     2 +-
 .../rhel7/{RHEL-07-030810.rst => V-72213.rst} |     2 +-
 .../rhel7/{RHEL-07-030820.rst => V-72215.rst} |     2 +-
 .../rhel7/{RHEL-07-040010.rst => V-72217.rst} |     2 +-
 .../rhel7/{RHEL-07-040100.rst => V-72219.rst} |     2 +-
 .../rhel7/{RHEL-07-040110.rst => V-72221.rst} |     2 +-
 .../rhel7/{RHEL-07-040160.rst => V-72223.rst} |     2 +-
 .../rhel7/{RHEL-07-040170.rst => V-72225.rst} |     2 +-
 .../rhel7/{RHEL-07-040180.rst => V-72227.rst} |     2 +-
 .../rhel7/{RHEL-07-040182.rst => V-72229.rst} |     2 +-
 .../rhel7/{RHEL-07-040181.rst => V-72231.rst} |     2 +-
 .../rhel7/{RHEL-07-040260.rst => V-72233.rst} |     2 +-
 .../rhel7/{RHEL-07-040261.rst => V-72235.rst} |     2 +-
 .../rhel7/{RHEL-07-040190.rst => V-72237.rst} |     4 +-
 doc/metadata/rhel7/V-72239.rst                |     7 +
 .../rhel7/{RHEL-07-040191.rst => V-72241.rst} |     4 +-
 .../rhel7/{RHEL-07-040334.rst => V-72243.rst} |     2 +-
 .../rhel7/{RHEL-07-040301.rst => V-72245.rst} |     2 +-
 .../rhel7/{RHEL-07-040310.rst => V-72247.rst} |     2 +-
 .../rhel7/{RHEL-07-040332.rst => V-72249.rst} |     2 +-
 .../rhel7/{RHEL-07-040590.rst => V-72251.rst} |     2 +-
 .../rhel7/{RHEL-07-040620.rst => V-72253.rst} |     2 +-
 .../rhel7/{RHEL-07-040640.rst => V-72255.rst} |     2 +-
 .../rhel7/{RHEL-07-040650.rst => V-72257.rst} |     2 +-
 .../rhel7/{RHEL-07-040660.rst => V-72259.rst} |     2 +-
 .../rhel7/{RHEL-07-040670.rst => V-72261.rst} |     2 +-
 .../rhel7/{RHEL-07-040680.rst => V-72263.rst} |     2 +-
 .../rhel7/{RHEL-07-040690.rst => V-72265.rst} |     2 +-
 .../rhel7/{RHEL-07-040700.rst => V-72267.rst} |     2 +-
 .../rhel7/{RHEL-07-040210.rst => V-72269.rst} |     2 +-
 .../rhel7/{RHEL-07-040250.rst => V-72271.rst} |     2 +-
 .../rhel7/{RHEL-07-040290.rst => V-72273.rst} |     2 +-
 .../rhel7/{RHEL-07-040300.rst => V-72275.rst} |     2 +-
 .../rhel7/{RHEL-07-040330.rst => V-72277.rst} |     2 +-
 .../rhel7/{RHEL-07-040331.rst => V-72279.rst} |     4 +-
 .../rhel7/{RHEL-07-040320.rst => V-72281.rst} |     2 +-
 .../rhel7/{RHEL-07-040350.rst => V-72283.rst} |     2 +-
 .../rhel7/{RHEL-07-040410.rst => V-72285.rst} |     4 +-
 .../rhel7/{RHEL-07-040380.rst => V-72287.rst} |     2 +-
 .../rhel7/{RHEL-07-010402.rst => V-72289.rst} |     6 +-
 .../rhel7/{RHEL-07-040420.rst => V-72291.rst} |     2 +-
 .../rhel7/{RHEL-07-040421.rst => V-72293.rst} |     4 +-
 .../rhel7/{RHEL-07-040470.rst => V-72295.rst} |     2 +-
 .../rhel7/{RHEL-07-040480.rst => V-72297.rst} |     2 +-
 doc/metadata/rhel7/V-72299.rst                |     7 +
 .../rhel7/{RHEL-07-040500.rst => V-72301.rst} |     3 +-
 .../rhel7/{RHEL-07-040540.rst => V-72303.rst} |     2 +-
 .../rhel7/{RHEL-07-040520.rst => V-72305.rst} |     2 +-
 .../rhel7/{RHEL-07-040560.rst => V-72307.rst} |     2 +-
 .../rhel7/{RHEL-07-040730.rst => V-72309.rst} |     2 +-
 .../rhel7/{RHEL-07-040740.rst => V-72311.rst} |     2 +-
 .../rhel7/{RHEL-07-040580.rst => V-72313.rst} |     2 +-
 .../rhel7/{RHEL-07-040820.rst => V-72315.rst} |     4 +-
 .../rhel7/{RHEL-07-040830.rst => V-72317.rst} |     2 +-
 .../rhel7/{RHEL-07-040860.rst => V-72319.rst} |     2 +-
 doc/metadata/rhel7/V-72417.rst                |    19 +
 doc/metadata/rhel7/V-72427.rst                |    10 +
 doc/metadata/rhel7/V-72433.rst                |     9 +
 doc/metadata/rhel7/V-72435.rst                |     9 +
 doc/metadata/rhel7/V-73155.rst                |     9 +
 doc/metadata/rhel7/V-73157.rst                |     9 +
 doc/metadata/rhel7/V-73159.rst                |    14 +
 doc/metadata/rhel7/V-73161.rst                |     9 +
 doc/metadata/rhel7/V-73163.rst                |     9 +
 doc/metadata/rhel7/V-73165.rst                |     9 +
 doc/metadata/rhel7/V-73167.rst                |     9 +
 doc/metadata/rhel7/V-73171.rst                |     9 +
 doc/metadata/rhel7/V-73173.rst                |     9 +
 .../rhel7/{RHEL-07-040351.rst => V-73175.rst} |     4 +-
 doc/metadata/rhel7/V-73177.rst                |     9 +
 doc/metadata/stig_to_rst.py                   |    30 +
 doc/source/_exts/metadata-docs-rhel7.py       |     3 +-
 doc/source/developer-guide.rst                |     4 +-
 doc/source/special-notes.rst                  |     2 +-
 ...1-renumbering-fiesta-aa047fea3ea35e74.yaml |    20 +
 tasks/rhel7stig/aide.yml                      |    16 +-
 tasks/rhel7stig/apt.yml                       |    36 +-
 tasks/rhel7stig/auditd.yml                    |   128 +-
 tasks/rhel7stig/auth.yml                      |   222 +-
 tasks/rhel7stig/file_perms.yml                |    65 +-
 tasks/rhel7stig/graphical.yml                 |    55 +-
 tasks/rhel7stig/kernel.yml                    |    29 +-
 tasks/rhel7stig/lsm.yml                       |    16 +-
 tasks/rhel7stig/misc.yml                      |    75 +-
 tasks/rhel7stig/packages.yml                  |    34 +-
 tasks/rhel7stig/rpm.yml                       |    24 +-
 tasks/rhel7stig/sshd.yml                      |    49 +-
 templates/dconf-screensaver-lock.j2           |     8 +-
 .../dconf-session-user-config-lockout.j2      |     2 +-
 templates/osas-auditd-rhel7.j2                |    42 +-
 templates/pam_faillock.j2                     |     2 +-
 templates/sshd_config_block.j2                |    36 +-
 vars/main.yml                                 |   129 +-
 vars/redhat.yml                               |     6 +
 284 files changed, 13162 insertions(+), 11523 deletions(-)
 delete mode 100644 doc/metadata/U_Red_Hat_Enterprise_Linux_7_STIG_V1R0-2_Manual-xccdf.xml
 create mode 100644 doc/metadata/U_Red_Hat_Enterprise_Linux_7_STIG_V1R1_Manual-xccdf.xml
 delete mode 100644 doc/metadata/rhel7/RHEL-07-010031.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-010070.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-010071.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-010373.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-010400.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-010401.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-010440.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-010470.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-010490.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-020170.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-020870.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-040020.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-040030.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-040040.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-040050.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-040060.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-040070.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-040080.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-040230.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-040333.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-040490.rst
 delete mode 100644 doc/metadata/rhel7/RHEL-07-040810.rst
 rename doc/metadata/rhel7/{RHEL-07-010010.rst => V-71849.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-010020.rst => V-71855.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-010030.rst => V-71859.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-010040.rst => V-71861.rst} (68%)
 create mode 100644 doc/metadata/rhel7/V-71863.rst
 rename doc/metadata/rhel7/{RHEL-07-010060.rst => V-71891.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-010073.rst => V-71893.rst} (94%)
 create mode 100644 doc/metadata/rhel7/V-71895.rst
 rename doc/metadata/rhel7/{RHEL-07-010072.rst => V-71897.rst} (84%)
 create mode 100644 doc/metadata/rhel7/V-71899.rst
 rename doc/metadata/rhel7/{RHEL-07-010074.rst => V-71901.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-010090.rst => V-71903.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-010100.rst => V-71905.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-010110.rst => V-71907.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-010120.rst => V-71909.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-010130.rst => V-71911.rst} (98%)
 rename doc/metadata/rhel7/{RHEL-07-010140.rst => V-71913.rst} (98%)
 rename doc/metadata/rhel7/{RHEL-07-010150.rst => V-71915.rst} (98%)
 rename doc/metadata/rhel7/{RHEL-07-010160.rst => V-71917.rst} (98%)
 rename doc/metadata/rhel7/{RHEL-07-010170.rst => V-71919.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-010180.rst => V-71921.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-010190.rst => V-71923.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-010200.rst => V-71925.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-010210.rst => V-71927.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-010220.rst => V-71929.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-010230.rst => V-71931.rst} (91%)
 rename doc/metadata/rhel7/{RHEL-07-010240.rst => V-71933.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-010250.rst => V-71935.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-010260.rst => V-71937.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-010270.rst => V-71939.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-010280.rst => V-71941.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-010372.rst => V-71943.rst} (64%)
 rename doc/metadata/rhel7/{RHEL-07-010371.rst => V-71945.rst} (98%)
 rename doc/metadata/rhel7/{RHEL-07-010380.rst => V-71947.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-010381.rst => V-71949.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-010420.rst => V-71951.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-010430.rst => V-71953.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-010431.rst => V-71955.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-010441.rst => V-71957.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-010442.rst => V-71959.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-010460.rst => V-71961.rst} (98%)
 create mode 100644 doc/metadata/rhel7/V-71963.rst
 rename doc/metadata/rhel7/{RHEL-07-010500.rst => V-71965.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-020000.rst => V-71967.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-020010.rst => V-71969.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-020090.rst => V-71971.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-020130.rst => V-71973.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-020140.rst => V-71975.rst} (87%)
 rename doc/metadata/rhel7/{RHEL-07-020150.rst => V-71977.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-020151.rst => V-71979.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-020152.rst => V-71981.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-020160.rst => V-71983.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-020161.rst => V-71985.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-020200.rst => V-71987.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-020210.rst => V-71989.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-020211.rst => V-71991.rst} (85%)
 rename doc/metadata/rhel7/{RHEL-07-020220.rst => V-71993.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-020230.rst => V-71995.rst} (98%)
 rename doc/metadata/rhel7/{RHEL-07-020240.rst => V-71997.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-020250.rst => V-71999.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-020290.rst => V-72001.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-020300.rst => V-72003.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-020310.rst => V-72005.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-020360.rst => V-72007.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-020370.rst => V-72009.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-020620.rst => V-72011.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-020630.rst => V-72013.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-020640.rst => V-72015.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-020650.rst => V-72017.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-020660.rst => V-72019.rst} (79%)
 rename doc/metadata/rhel7/{RHEL-07-020670.rst => V-72021.rst} (79%)
 rename doc/metadata/rhel7/{RHEL-07-020700.rst => V-72023.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-020680.rst => V-72025.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-020690.rst => V-72027.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-020850.rst => V-72029.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-020860.rst => V-72031.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-020840.rst => V-72033.rst} (96%)
 create mode 100644 doc/metadata/rhel7/V-72035.rst
 rename doc/metadata/rhel7/{RHEL-07-020880.rst => V-72037.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-020940.rst => V-72039.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-021010.rst => V-72041.rst} (90%)
 rename doc/metadata/rhel7/{RHEL-07-021011.rst => V-72043.rst} (90%)
 rename doc/metadata/rhel7/{RHEL-07-021012.rst => V-72045.rst} (89%)
 rename doc/metadata/rhel7/{RHEL-07-021050.rst => V-72047.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-021060.rst => V-72049.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-021160.rst => V-72051.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-021190.rst => V-72053.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-021200.rst => V-72055.rst} (82%)
 rename doc/metadata/rhel7/{RHEL-07-021230.rst => V-72057.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-021240.rst => V-72059.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-021250.rst => V-72061.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-021260.rst => V-72063.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-021270.rst => V-72065.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-021280.rst => V-72067.rst} (98%)
 rename doc/metadata/rhel7/{RHEL-07-021600.rst => V-72069.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-021610.rst => V-72071.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-021620.rst => V-72073.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-021760.rst => V-72075.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-021910.rst => V-72077.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-030010.rst => V-72079.rst} (88%)
 rename doc/metadata/rhel7/{RHEL-07-030090.rst => V-72081.rst} (98%)
 rename doc/metadata/rhel7/{RHEL-07-030330.rst => V-72083.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030331.rst => V-72085.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-030340.rst => V-72087.rst} (98%)
 rename doc/metadata/rhel7/{RHEL-07-030350.rst => V-72089.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-030351.rst => V-72091.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-030352.rst => V-72093.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-030310.rst => V-72095.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-030380.rst => V-72097.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-030381.rst => V-72099.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-030382.rst => V-72101.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-030383.rst => V-72103.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-030390.rst => V-72105.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-030391.rst => V-72107.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-030392.rst => V-72109.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-030400.rst => V-72111.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030401.rst => V-72113.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-030402.rst => V-72115.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-030403.rst => V-72117.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030404.rst => V-72119.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-030405.rst => V-72121.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-030420.rst => V-72123.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030421.rst => V-72125.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030422.rst => V-72127.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030423.rst => V-72129.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030424.rst => V-72131.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030425.rst => V-72133.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030441.rst => V-72135.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-030442.rst => V-72137.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-030443.rst => V-72139.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-030444.rst => V-72141.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030490.rst => V-72143.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030491.rst => V-72145.rst} (68%)
 rename doc/metadata/rhel7/{RHEL-07-030492.rst => V-72147.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030510.rst => V-72149.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030511.rst => V-72151.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030512.rst => V-72153.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030513.rst => V-72155.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-030514.rst => V-72157.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030521.rst => V-72159.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-030522.rst => V-72161.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-030523.rst => V-72163.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030524.rst => V-72165.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030525.rst => V-72167.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-030526.rst => V-72169.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030530.rst => V-72171.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-030531.rst => V-72173.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030540.rst => V-72175.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030541.rst => V-72177.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030550.rst => V-72179.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030560.rst => V-72181.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030561.rst => V-72183.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030630.rst => V-72185.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030670.rst => V-72187.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030671.rst => V-72189.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030672.rst => V-72191.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030673.rst => V-72193.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-030674.rst => V-72195.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-030710.rst => V-72197.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-030750.rst => V-72199.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030751.rst => V-72201.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030752.rst => V-72203.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030753.rst => V-72205.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030754.rst => V-72207.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030770.rst => V-72209.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-030780.rst => V-72211.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-030810.rst => V-72213.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-030820.rst => V-72215.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-040010.rst => V-72217.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-040100.rst => V-72219.rst} (90%)
 rename doc/metadata/rhel7/{RHEL-07-040110.rst => V-72221.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-040160.rst => V-72223.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-040170.rst => V-72225.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-040180.rst => V-72227.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-040182.rst => V-72229.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-040181.rst => V-72231.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-040260.rst => V-72233.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-040261.rst => V-72235.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-040190.rst => V-72237.rst} (90%)
 create mode 100644 doc/metadata/rhel7/V-72239.rst
 rename doc/metadata/rhel7/{RHEL-07-040191.rst => V-72241.rst} (90%)
 rename doc/metadata/rhel7/{RHEL-07-040334.rst => V-72243.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-040301.rst => V-72245.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-040310.rst => V-72247.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-040332.rst => V-72249.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-040590.rst => V-72251.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-040620.rst => V-72253.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-040640.rst => V-72255.rst} (91%)
 rename doc/metadata/rhel7/{RHEL-07-040650.rst => V-72257.rst} (91%)
 rename doc/metadata/rhel7/{RHEL-07-040660.rst => V-72259.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-040670.rst => V-72261.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-040680.rst => V-72263.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-040690.rst => V-72265.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-040700.rst => V-72267.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-040210.rst => V-72269.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-040250.rst => V-72271.rst} (98%)
 rename doc/metadata/rhel7/{RHEL-07-040290.rst => V-72273.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-040300.rst => V-72275.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-040330.rst => V-72277.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-040331.rst => V-72279.rst} (68%)
 rename doc/metadata/rhel7/{RHEL-07-040320.rst => V-72281.rst} (89%)
 rename doc/metadata/rhel7/{RHEL-07-040350.rst => V-72283.rst} (97%)
 rename doc/metadata/rhel7/{RHEL-07-040410.rst => V-72285.rst} (68%)
 rename doc/metadata/rhel7/{RHEL-07-040380.rst => V-72287.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-010402.rst => V-72289.rst} (61%)
 rename doc/metadata/rhel7/{RHEL-07-040420.rst => V-72291.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-040421.rst => V-72293.rst} (68%)
 rename doc/metadata/rhel7/{RHEL-07-040470.rst => V-72295.rst} (91%)
 rename doc/metadata/rhel7/{RHEL-07-040480.rst => V-72297.rst} (94%)
 create mode 100644 doc/metadata/rhel7/V-72299.rst
 rename doc/metadata/rhel7/{RHEL-07-040500.rst => V-72301.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-040540.rst => V-72303.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-040520.rst => V-72305.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-040560.rst => V-72307.rst} (95%)
 rename doc/metadata/rhel7/{RHEL-07-040730.rst => V-72309.rst} (96%)
 rename doc/metadata/rhel7/{RHEL-07-040740.rst => V-72311.rst} (92%)
 rename doc/metadata/rhel7/{RHEL-07-040580.rst => V-72313.rst} (94%)
 rename doc/metadata/rhel7/{RHEL-07-040820.rst => V-72315.rst} (88%)
 rename doc/metadata/rhel7/{RHEL-07-040830.rst => V-72317.rst} (93%)
 rename doc/metadata/rhel7/{RHEL-07-040860.rst => V-72319.rst} (96%)
 create mode 100644 doc/metadata/rhel7/V-72417.rst
 create mode 100644 doc/metadata/rhel7/V-72427.rst
 create mode 100644 doc/metadata/rhel7/V-72433.rst
 create mode 100644 doc/metadata/rhel7/V-72435.rst
 create mode 100644 doc/metadata/rhel7/V-73155.rst
 create mode 100644 doc/metadata/rhel7/V-73157.rst
 create mode 100644 doc/metadata/rhel7/V-73159.rst
 create mode 100644 doc/metadata/rhel7/V-73161.rst
 create mode 100644 doc/metadata/rhel7/V-73163.rst
 create mode 100644 doc/metadata/rhel7/V-73165.rst
 create mode 100644 doc/metadata/rhel7/V-73167.rst
 create mode 100644 doc/metadata/rhel7/V-73171.rst
 create mode 100644 doc/metadata/rhel7/V-73173.rst
 rename doc/metadata/rhel7/{RHEL-07-040351.rst => V-73175.rst} (68%)
 create mode 100644 doc/metadata/rhel7/V-73177.rst
 create mode 100755 doc/metadata/stig_to_rst.py
 create mode 100644 releasenotes/notes/stig-rhel7-version-1-renumbering-fiesta-aa047fea3ea35e74.yaml

diff --git a/defaults/main.yml b/defaults/main.yml
index bca16ac0..a3ac75b7 100644
--- a/defaults/main.yml
+++ b/defaults/main.yml
@@ -384,156 +384,154 @@ security_unattended_upgrades_notifications: false
 
 ## AIDE (aide)
 # Initialize the AIDE database immediately (may take time).
-security_rhel7_initialize_aide: no                           # RHEL-07-020130
+security_rhel7_initialize_aide: no                           # V-71973
 
 ## Audit daemon (auditd)
 # Send audit records to a different system using audisp.
-#security_audisp_remote_server: '10.0.21.1'                  # RHEL-07-030330
+#security_audisp_remote_server: '10.0.21.1'                  # V-72083
 # Encrypt audit records when they are transmitted over the network.
-#security_audisp_enable_krb5: yes                            # RHEL-07-030331
+#security_audisp_enable_krb5: yes                            # V-72085
 # Set the auditd failure flag. WARNING: READ DOCUMENTATION BEFORE CHANGING!
-security_rhel7_audit_failure_flag: 1                         # RHEL-07-030090
+security_rhel7_audit_failure_flag: 1                         # V-72081
 # Set the action to take when the disk is full or network events cannot be sent.
-security_rhel7_auditd_disk_full_action: syslog               # RHEL-07-030340
-security_rhel7_auditd_network_failure_action: syslog         # RHEL-07-030340
+security_rhel7_auditd_disk_full_action: syslog               # V-72087
+security_rhel7_auditd_network_failure_action: syslog         # V-72087
 # Size of remaining disk space (in MB) that triggers alerts.
-security_rhel7_auditd_space_left: "{{ (ansible_mounts | selectattr('mount', 'equalto', '/') | map(attribute='size_total') | first * 0.25 / 1024 / 1024) | int }}" # RHEL-07-030350
+security_rhel7_auditd_space_left: "{{ (ansible_mounts | selectattr('mount', 'equalto', '/') | map(attribute='size_total') | first * 0.25 / 1024 / 1024) | int }}" # V-72089
 # Action to take when the space_left threshold is reached.
-security_rhel7_auditd_space_left_action: email               # RHEL-07-030351
+security_rhel7_auditd_space_left_action: email               # V-72091
 # Send auditd email alerts to this user.
-security_rhel7_auditd_action_mail_acct: root                 # RHEL-07-030352
+security_rhel7_auditd_action_mail_acct: root                 # V-72093
 # Add audit rules for commands/syscalls.
-security_rhel7_audit_chsh: yes                               # RHEL-07-030525
-security_rhel7_audit_chage: yes                              # RHEL-07-030513
-security_rhel7_audit_chcon: yes                              # RHEL-07-030443
-security_rhel7_audit_chmod: no                               # RHEL-07-030390
-security_rhel7_audit_chown: no                               # RHEL-07-030380
-security_rhel7_audit_creat: yes                              # RHEL-07-030420
-security_rhel7_audit_crontab: yes                            # RHEL-07-030561
-security_rhel7_audit_delete_module: yes                      # RHEL-07-030671
-security_rhel7_audit_fchmod: no                              # RHEL-07-030391
-security_rhel7_audit_fchmodat: no                            # RHEL-07-030392
-security_rhel7_audit_fchown: no                              # RHEL-07-030381
-security_rhel7_audit_fchownat: no                            # RHEL-07-030383
-security_rhel7_audit_fremovexattr: no                        # RHEL-07-030404
-security_rhel7_audit_fsetxattr: no                           # RHEL-07-030401
-security_rhel7_audit_ftruncate: yes                          # RHEL-07-030425
-security_rhel7_audit_init_module: yes                        # RHEL-07-030670
-security_rhel7_audit_gpasswd: yes                            # RHEL-07-030512
-security_rhel7_audit_lchown: no                              # RHEL-07-030382
-security_rhel7_audit_lremovexattr: no                        # RHEL-07-030405
-security_rhel7_audit_lsetxattr: no                           # RHEL-07-030402
-security_rhel7_audit_mount: yes                              # RHEL-07-030530
-security_rhel7_audit_newgrp: yes                             # RHEL-07-030524
-security_rhel7_audit_open: yes                               # RHEL-07-030421
-security_rhel7_audit_openat: yes                             # RHEL-07-030422
-security_rhel7_audit_open_by_handle_at: yes                  # RHEL-07-030423
-security_rhel7_audit_pam_timestamp_check: yes                # RHEL-07-030630
-security_rhel7_audit_passwd: yes                             # RHEL-07-030510
-security_rhel7_audit_postdrop: yes                           # RHEL-07-030540
-security_rhel7_audit_postqueue: yes                          # RHEL-07-030541
-security_rhel7_audit_pt_chown: yes                           # RHEL-07-030560
-security_rhel7_audit_removexattr: no                         # RHEL-07-030403
-security_rhel7_audit_rename: yes                             # RHEL-07-030750
-security_rhel7_audit_renameat: yes                           # RHEL-07-030751
-security_rhel7_audit_restorecon: yes                         # RHEL-07-030444
-security_rhel7_audit_rmdir: yes                              # RHEL-07-030752
-security_rhel7_audit_semanage: yes                           # RHEL-07-030441
-security_rhel7_audit_setsebool: yes                          # RHEL-07-030442
-security_rhel7_audit_setxattr: no                            # RHEL-07-030400
-security_rhel7_audit_ssh_keysign: yes                        # RHEL-07-030550
-security_rhel7_audit_su: yes                                 # RHEL-07-030521
-security_rhel7_audit_sudo: yes                               # RHEL-07-030522
-security_rhel7_audit_sudoedit: yes                           # RHEL-07-030526
-security_rhel7_audit_truncate: yes                           # RHEL-07-030424
-security_rhel7_audit_umount: yes                             # RHEL-07-030531
-security_rhel7_audit_unix_chkpwd: yes                        # RHEL-07-030511
-security_rhel7_audit_unlink: yes                             # RHEL-07-030753
-security_rhel7_audit_unlinkat: yes                           # RHEL-07-030754
-security_rhel7_audit_userhelper: yes                         # RHEL-07-030514
+security_rhel7_audit_chsh: yes                               # V-72167
+security_rhel7_audit_chage: yes                              # V-72155
+security_rhel7_audit_chcon: yes                              # V-72139
+security_rhel7_audit_chmod: no                               # V-72105
+security_rhel7_audit_chown: no                               # V-72097
+security_rhel7_audit_creat: yes                              # V-72123
+security_rhel7_audit_crontab: yes                            # V-72183
+security_rhel7_audit_delete_module: yes                      # V-72189
+security_rhel7_audit_fchmod: no                              # V-72107
+security_rhel7_audit_fchmodat: no                            # V-72109
+security_rhel7_audit_fchown: no                              # V-72099
+security_rhel7_audit_fchownat: no                            # V-72103
+security_rhel7_audit_fremovexattr: no                        # V-72119
+security_rhel7_audit_fsetxattr: no                           # V-72113
+security_rhel7_audit_ftruncate: yes                          # V-72133
+security_rhel7_audit_init_module: yes                        # V-72187
+security_rhel7_audit_gpasswd: yes                            # V-72153
+security_rhel7_audit_lchown: no                              # V-72101
+security_rhel7_audit_lremovexattr: no                        # V-72121
+security_rhel7_audit_lsetxattr: no                           # V-72115
+security_rhel7_audit_mount: yes                              # V-72171
+security_rhel7_audit_newgrp: yes                             # V-72165
+security_rhel7_audit_open: yes                               # V-72125
+security_rhel7_audit_openat: yes                             # V-72127
+security_rhel7_audit_open_by_handle_at: yes                  # V-72129
+security_rhel7_audit_pam_timestamp_check: yes                # V-72185
+security_rhel7_audit_passwd: yes                             # V-72149
+security_rhel7_audit_postdrop: yes                           # V-72175
+security_rhel7_audit_postqueue: yes                          # V-72177
+security_rhel7_audit_pt_chown: yes                           # V-72181
+security_rhel7_audit_removexattr: no                         # V-72117
+security_rhel7_audit_rename: yes                             # V-72199
+security_rhel7_audit_renameat: yes                           # V-72201
+security_rhel7_audit_restorecon: yes                         # V-72141
+security_rhel7_audit_rmdir: yes                              # V-72203
+security_rhel7_audit_semanage: yes                           # V-72135
+security_rhel7_audit_setsebool: yes                          # V-72137
+security_rhel7_audit_setxattr: no                            # V-72111
+security_rhel7_audit_ssh_keysign: yes                        # V-72179
+security_rhel7_audit_su: yes                                 # V-72159
+security_rhel7_audit_sudo: yes                               # V-72161
+security_rhel7_audit_sudoedit: yes                           # V-72169
+security_rhel7_audit_truncate: yes                           # V-72131
+security_rhel7_audit_umount: yes                             # V-72173
+security_rhel7_audit_unix_chkpwd: yes                        # V-72151
+security_rhel7_audit_unlink: yes                             # V-72205
+security_rhel7_audit_unlinkat: yes                           # V-72207
+security_rhel7_audit_userhelper: yes                         # V-72157
 # Add audit rules for other events.
-security_rhel7_audit_account_access: yes                     # RHEL-07-030490
-security_rhel7_audit_sudo_config_changes: yes                # RHEL-07-030523
-security_rhel7_audit_insmod: yes                             # RHEL-07-030672
-security_rhel7_audit_rmmod: yes                              # RHEL-07-030673
-security_rhel7_audit_modprobe: yes                           # RHEL-07-030674
-security_rhel7_audit_account_actions: yes                    # RHEL-07-030710
+security_rhel7_audit_account_access: yes                     # V-72143
+security_rhel7_audit_sudo_config_changes: yes                # V-72163
+security_rhel7_audit_insmod: yes                             # V-72191
+security_rhel7_audit_rmmod: yes                              # V-72193
+security_rhel7_audit_modprobe: yes                           # V-72195
+security_rhel7_audit_account_actions: yes                    # V-72197
 
 ## Authentication (auth)
 # Disallow logins from accounts with blank/null passwords via PAM.
-security_disallow_blank_password_login: yes                  # RHEL-07-010260
+security_disallow_blank_password_login: yes                  # V-71937
 # Apply password quality rules.
 # NOTE: The security_pwquality_apply_rules variable is a "master switch".
 # Set the 'security_pwquality_apply_rules' variable to 'yes' to apply all of
 # the password quality rules. Each rule can be disabled with a value of 'no'.
 security_pwquality_apply_rules: no
-security_pwquality_require_uppercase: yes                    # RHEL-07-010090
-security_pwquality_require_lowercase: yes                    # RHEL-07-010100
-security_pwquality_require_numeric: yes                      # RHEL-07-010110
-security_pwquality_require_special: yes                      # RHEL-07-010120
-security_pwquality_require_characters_changed: yes           # RHEL-07-010130
-security_pwquality_require_character_classes_changed: yes    # RHEL-07-010140
-security_pwquality_limit_repeated_characters: yes            # RHEL-07-010150
-security_pwquality_limit_repeated_character_classes: yes     # RHEL-07-010160
-security_pwquality_require_minimum_password_length: no       # RHEL-07-010250
+security_pwquality_require_uppercase: yes                    # V-71903
+security_pwquality_require_lowercase: yes                    # V-71905
+security_pwquality_require_numeric: yes                      # V-71907
+security_pwquality_require_special: yes                      # V-71909
+security_pwquality_require_characters_changed: yes           # V-71911
+security_pwquality_require_character_classes_changed: yes    # V-71913
+security_pwquality_limit_repeated_characters: yes            # V-71915
+security_pwquality_limit_repeated_character_classes: yes     # V-71917
+security_pwquality_require_minimum_password_length: no       # V-71935
+# Use pwquality when passwords are changed or established.
+security_enable_pwquality_password_set: no                   # V-73159
 # Ensure passwords are stored using SHA512.
-security_password_encrypt_method: SHA512                     # RHEL-07-010180
+security_password_encrypt_method: SHA512                     # V-71921
 # Ensure user/group admin utilities only store encrypted passwords.
-security_libuser_crypt_style_sha512: yes                     # RHEL-07-010190
+security_libuser_crypt_style_sha512: yes                     # V-71923
 # Set a minimum/maximum lifetime limit for user passwords.
-#security_password_min_lifetime_days: 1                      # RHEL-07-010200
-#security_password_max_lifetime_days: 60                     # RHEL-07-010220
-# Set a timeout (in seconds) to cache NSS authenticators with sssd.
-security_nss_cached_authenticator_timeout: 86400             # RHEL-07-010400
-# Set a timeout (in days) to cache PAM/ssh authenticators with sssd.
-security_pam_offline_credentials_expiration_days: 1          # RHEL-07-010401 / RHEL-07-010402
+#security_password_min_lifetime_days: 1                      # V-71925
+#security_password_max_lifetime_days: 60                     # V-71929
 # Set a delay (in seconds) between failed login attempts.
-security_shadow_utils_fail_delay: 4                          # RHEL-07-010420
+security_shadow_utils_fail_delay: 4                          # V-71951
 # Set a umask for all authenticated users.
-# security_shadow_utils_umask: '077'                         # RHEL-07-020230
+# security_shadow_utils_umask: '077'                         # V-71995
 # Create home directories for new users by default.
-security_shadow_utils_create_home: yes                       # RHEL-07-020630
+security_shadow_utils_create_home: yes                       # V-72013
 # How many old user password to remember to prevent password re-use.
-#security_password_remember_password: 5                      # RHEL-07-010240
+#security_password_remember_password: 5                      # V-71933
 # Disable user accounts if the password expires.
-security_disable_account_if_password_expires: no             # RHEL-07-010280
+security_disable_account_if_password_expires: no             # V-71941
 # Lock user accounts with excessive login failures. See documentation.
-security_pam_faillock_enable: no                             # RHEL-07-010371 / RHEL-07-010372 / RHEL-07-010373
+security_pam_faillock_enable: no                             # V-71945 / V-71943 / RHEL-07-010373
 security_pam_faillock_interval: 900
 security_pam_faillock_attempts: 3
 security_pam_faillock_deny_root: yes                         # RHEL-07-010373
-security_pam_faillock_unlock_time: 604800                    # RHEL-07-010372
+security_pam_faillock_unlock_time: 604800                    # V-71943
 # Limit the number of concurrent connections per account.
-#security_rhel7_concurrent_session_limit: 10                 # RHEL-07-040010
+#security_rhel7_concurrent_session_limit: 10                 # V-72217
 # Remove .shosts and shosts.equiv files.
-security_rhel7_remove_shosts_files: no                       # RHEL-07-040330
+security_rhel7_remove_shosts_files: no                       # V-72277
 
 ## File permissions (file_perms)
 # Reset file permissions and ownership for files installed via RPM packages.
-security_reset_perm_ownership: no                            # RHEL-07-010010
+security_reset_perm_ownership: no                            # V-71849
 # Search for files/directories owned by invalid users or groups.
-security_search_for_invalid_owner: no                        # RHEL-07-020360
-security_search_for_invalid_group_owner: no                  # RHEL-07-020370
+security_search_for_invalid_owner: no                        # V-72007
+security_search_for_invalid_group_owner: no                  # V-72009
 # Set user/group owners on each home directory and set mode to 0750.
-security_set_home_directory_permissions_and_owners: no       # RHEL-07-020650 / RHEL-07-020660 / RHEL-07-020670
+security_set_home_directory_permissions_and_owners: no       # V-72017 / V-72019 / V-72021
 
 ## Graphical interfaces (graphical)
 # Disable automatic gdm logins
-security_disable_gdm_automatic_login: yes                    # RHEL-07-010430
+security_disable_gdm_automatic_login: yes                    # V-71953
 # Disable timed gdm logins for guests
-security_disable_gdm_timed_login: yes                        # RHEL-07-010431
+security_disable_gdm_timed_login: yes                        # V-71955
 # Enable session locking for graphical logins.
-security_lock_session: no                                    # RHEL-07-010060
+security_lock_session: no                                    # V-71891
 # Set a timer (in seconds) when an inactive session is locked.
-security_lock_session_inactive_delay: 900                    # RHEL-07-010070
+security_lock_session_inactive_delay: 900                    # V-71893
 # Prevent users from modifying session lock settings.
 security_lock_session_override_user: yes                     # RHEL-07-010071
 # Lock a session (start screensaver) when a session is inactive.
-security_lock_session_when_inactive: yes                     # RHEL-07-010073
+security_lock_session_when_inactive: yes                     # V-71893
 # Time after screensaver starts when user login is required.
-security_lock_session_screensaver_lock_delay: 5              # RHEL-07-010074
+security_lock_session_screensaver_lock_delay: 5              # V-71901
 # Enable a login banner and set the text for the banner.
-security_enable_graphical_login_message: yes                 # RHEL-07-010030
+security_enable_graphical_login_message: yes                 # V-71859
 security_enable_graphical_login_message_text: >
     You are accessing a secured system and your actions will be logged along
     with identifying information. Disconnect immediately if you are not an
@@ -541,105 +539,107 @@ security_enable_graphical_login_message_text: >
 
 ## Linux Security Module (lsm)
 # Enable SELinux on Red Hat/CentOS and AppArmor on Ubuntu.
-security_rhel7_enable_linux_security_module: yes             # RHEL-07-020210 / RHEL-07-020211
+security_rhel7_enable_linux_security_module: yes             # V-71989 / V-71991
 
 ## Miscellaneous (misc)
 # Disable the autofs service.
-security_rhel7_disable_autofs: yes                           # RHEL-07-020161
+security_rhel7_disable_autofs: yes                           # V-71985
 # Enable virus scanning with clamav
-security_enable_virus_scanner: no                            # RHEL-07-030810
+security_enable_virus_scanner: no                            # V-72213
 # Disable ctrl-alt-delete key sequence on the console.
-security_rhel7_disable_ctrl_alt_delete: yes                  # RHEL-07-020220
+security_rhel7_disable_ctrl_alt_delete: yes                  # V-71993
 # Install and enable firewalld for iptables management.
-security_enable_firewalld: no                                # RHEL-07-040290
+security_enable_firewalld: no                                # V-72273
 # Rate limit TCP connections to 25/min and burstable to 100.
-security_enable_firewalld_rate_limit: no                     # RHEL-07-040250
+security_enable_firewalld_rate_limit: no                     # V-72271
 security_enable_firewalld_rate_limit_per_minute: 25
 security_enable_firewalld_rate_limit_burst: 100
 # Require authentication in GRUB to boot into single-user or maintenance modes.
-security_require_grub_authentication: no                     # RHEL-07-010460 / RHEL-07-010470
+security_require_grub_authentication: no                     # V-71961 / V-71963
 # The default password for grub authentication is 'secrete'.
 security_grub_password_hash: grub.pbkdf2.sha512.10000.7B21785BEAFEE3AC71459D8210E3FB42EC0F5011C24A2DF31A8127D43A0BB4F1563549DF443791BE8EDA3AE4E4D4E04DB78D4CA35320E4C646CF38320CBE16EC.4B46176AAB1405D97BADB696377C29DE3B3266188D9C3D2E57F3AE851815CCBC16A275B0DBF6F79D738DAD8F598BEE64C73AE35F19A28C5D1E7C7D96FF8A739B
 # Set session timeout.
-security_rhel7_session_timeout: 600                          # RHEL-07-040160
+security_rhel7_session_timeout: 600                          # V-72223
 # Enable chrony for NTP time synchronization.
-security_rhel7_enable_chrony: yes                            # RHEL-07-040210
+security_rhel7_enable_chrony: yes                            # V-72269
 # Restrict mail relaying.
-security_rhel7_restrict_mail_relaying: yes                   # RHEL-07-040480
+security_rhel7_restrict_mail_relaying: yes                   # V-72297
 
 ## Packages (packages)
 # Remove packages from the system as required by the STIG. Set any of these
 # to 'no' to skip their removal.
-security_rhel7_remove_rsh_server: yes                        # RHEL-07-020000
-security_rhel7_remove_telnet_server: yes                     # RHEL-07-021910
-security_rhel7_remove_tftp_server: yes                       # RHEL-07-040500
-security_rhel7_remove_xorg: yes                              # RHEL-07-040560
-security_rhel7_remove_ypserv: yes                            # RHEL-07-020010
+security_rhel7_remove_rsh_server: yes                        # V-71967
+security_rhel7_remove_telnet_server: yes                     # V-72077
+security_rhel7_remove_tftp_server: yes                       # V-72301
+security_rhel7_remove_xorg: yes                              # V-72307
+security_rhel7_remove_ypserv: yes                            # V-71969
 # Automatically remove dependencies when removing packages.
-security_package_clean_on_remove: no                         # RHEL-07-020200
+security_package_clean_on_remove: no                         # V-71987
 # Automatically update packages.
-security_rhel7_automatic_package_updates: no                 # RHEL-07-020250
+security_rhel7_automatic_package_updates: no                 # V-71999
+# Install packages for multi-factor authentication.
+security_install_multifactor_auth_packages: yes              # V-72417
 
 ## RPM (rpm)
 # Enable GPG checks for packages and repository data.
-security_enable_gpgcheck_packages: yes                       # RHEL-07-020150
-security_enable_gpgcheck_packages_local: yes                 # RHEL-07-020151
-security_enable_gpgcheck_repo: no                            # RHEL-07-020152
+security_enable_gpgcheck_packages: yes                       # V-71977
+security_enable_gpgcheck_packages_local: yes                 # V-71979
+security_enable_gpgcheck_repo: no                            # V-71981
 
 ## ssh server (sshd)
 # Ensure sshd is running and enabled at boot time.
-security_enable_sshd: yes                                    # RHEL-07-040261
+security_enable_sshd: yes                                    # V-72235
 # Disallow logins from users with empty/null passwords.
-security_sshd_disallow_empty_password: yes                   # RHEL-07-010270 / RHEL-07-010440
+security_sshd_disallow_empty_password: yes                   # V-71939 / RHEL-07-010440
 # Disallow users from overriding the ssh environment variables.
-security_sshd_disallow_environment_override: yes             # RHEL-07-010441
+security_sshd_disallow_environment_override: yes             # V-71957
 # Disallow host based authentication.
-security_sshd_disallow_host_based_auth: yes                  # RHEL-07-010442
+security_sshd_disallow_host_based_auth: yes                  # V-71959
 # Set a list of allowed ssh ciphers.
-security_sshd_cipher_list: 'aes128-ctr,aes192-ctr,aes256-ctr' # RHEL-07-040110
+security_sshd_cipher_list: 'aes128-ctr,aes192-ctr,aes256-ctr' # V-72221
 # Specify a text file to be displayed as the banner/MOTD for all sessions.
-security_sshd_banner_file: /etc/motd                         # RHEL-07-010040 / RHEL-07-040170
+security_sshd_banner_file: /etc/motd                         # V-71861 / V-72225
 # Set the interval for max session length and the number of intervals to allow.
-security_sshd_client_alive_interval: 600                     # RHEL-07-040190
-security_sshd_client_alive_count_max: 0                      # RHEL-07-040191
+security_sshd_client_alive_interval: 600                     # V-72237
+security_sshd_client_alive_count_max: 0                      # V-72241
 # Print the last login for a user when they log in over ssh.
-security_sshd_print_last_log: yes                            # RHEL-07-040301
+security_sshd_print_last_log: yes                            # V-72245
 # Permit direct root logins
-security_sshd_permit_root_login: no                          # RHEL-07-040310
+security_sshd_permit_root_login: no                          # V-72247
 # Disallow authentication using known hosts authentication.
-security_sshd_disallow_known_hosts_auth: yes                 # RHEL-07-040332 / RHEL-07-040333
+security_sshd_disallow_known_hosts_auth: yes                 # V-72249 / V-72239
 # Disallow rhosts authentication.
-security_sshd_disallow_rhosts_auth: yes                      # RHEL-07-040334
+security_sshd_disallow_rhosts_auth: yes                      # V-72243
 # Enable X11 forwarding.
-security_sshd_enable_x11_forwarding: yes                     # RHEL-07-040540
+security_sshd_enable_x11_forwarding: yes                     # V-72303
 # Set the allowed ssh protocols.
-security_sshd_protocol: 2                                    # RHEL-07-040590
+security_sshd_protocol: 2                                    # V-72251
 # Set the list of allowed Message Authentication Codes (MACs) for ssh.
-security_sshd_allowed_macs: 'hmac-sha2-256,hmac-sha2-512'    # RHEL-07-040620
+security_sshd_allowed_macs: 'hmac-sha2-256,hmac-sha2-512'    # V-72253
 # Disallow Generic Security Service Application Program Interface (GSSAPI) auth.
-security_sshd_disallow_gssapi: yes                           # RHEL-07-040660
+security_sshd_disallow_gssapi: yes                           # V-72259
 # Disallow compression or delay after login.
-security_sshd_compression: 'delayed'                         # RHEL-07-040700
+security_sshd_compression: 'delayed'                         # V-72267
 # Require privilege separation at every opportunity.
-security_sshd_enable_privilege_separation: yes               # RHEL-07-040690
+security_sshd_enable_privilege_separation: yes               # V-72265
 # Require strict mode checking of home directory configuration files.
-security_sshd_enable_strict_modes: yes                       # RHEL-07-040680
+security_sshd_enable_strict_modes: yes                       # V-72263
 # Disallow Kerberos authentication.
-security_sshd_disable_kerberos_auth: yes                     # RHEL-07-040670
+security_sshd_disable_kerberos_auth: yes                     # V-72261
 
 ## Kernel settings (kernel)
 # Disallow forwarding IPv4/IPv6 source routed packets on all interfaces
 # immediately and by default on new interfaces.
-security_disallow_source_routed_packet_forward_ipv4: yes     # RHEL-07-040350 / RHEL-07-040351
-security_disallow_source_routed_packet_forward_ipv6: yes     # RHEL-07-040860
+security_disallow_source_routed_packet_forward_ipv4: yes     # V-72283 / V-72285
+security_disallow_source_routed_packet_forward_ipv6: yes     # V-72319
 # Disallow responses to IPv4 ICMP echoes sent to broadcast address.
-security_disallow_echoes_broadcast_address: yes              # RHEL-07-040380
+security_disallow_echoes_broadcast_address: yes              # V-72287
 # Disallow IPV4 ICMP redirects on all interfaces immediately and by default on
 # new interfaces.
-security_disallow_icmp_redirects: yes                        # RHEL-07-040410 / RHEL-07-040420 / RHEL-07-040421
+security_disallow_icmp_redirects: yes                        # V-73175 / V-72289 / V-72291 / V-72293
 # Disallow IP forwarding.
-security_disallow_ip_forwarding: no                          # RHEL-07-040730
+security_disallow_ip_forwarding: no                          # V-72309
 # Disable USB storage support.
-security_rhel7_disable_usb_storage: yes                      # RHEL-07-020160
+security_rhel7_disable_usb_storage: yes                      # V-71983
 # Disable kdump.
-security_disable_kdump: yes                                  # RHEL-07-021230
+security_disable_kdump: yes                                  # V-72057
diff --git a/doc/metadata/U_Red_Hat_Enterprise_Linux_7_STIG_V1R0-2_Manual-xccdf.xml b/doc/metadata/U_Red_Hat_Enterprise_Linux_7_STIG_V1R0-2_Manual-xccdf.xml
deleted file mode 100644
index d3bb989d..00000000
--- a/doc/metadata/U_Red_Hat_Enterprise_Linux_7_STIG_V1R0-2_Manual-xccdf.xml
+++ /dev/null
@@ -1,10364 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type='text/xsl' href='STIG_unclass.xsl'?>
-<Benchmark xmlns="http://checklists.nist.gov/xccdf/1.1" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:cpe="http://cpe.mitre.org/language/2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" id="Red_Hat_Enterprise_Linux_7_STIG" xml:lang="en" 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">
-  <status date="2016-01-14">draft</status>
-  <title>Red Hat Enterprise Linux 7 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" />
-  <reference href="http://iase.disa.mil">
-    <dc:publisher>DISA, Field Security Operations</dc:publisher>
-    <dc:source>STIG.DOD.MIL</dc:source>
-  </reference>
-  <plain-text id="release-info">Release: 0.2 Benchmark Date: 30 Jun 2016</plain-text>
-  <version>1</version>
-  <Profile id="MAC-1_Public">
-    <title>I - Mission Critical Public</title>
-    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
-    <select idref="RHEL-07-010010" selected="true" />
-    <select idref="RHEL-07-010020" selected="true" />
-    <select idref="RHEL-07-010030" selected="true" />
-    <select idref="RHEL-07-010031" selected="true" />
-    <select idref="RHEL-07-010040" selected="true" />
-    <select idref="RHEL-07-010060" selected="true" />
-    <select idref="RHEL-07-010070" selected="true" />
-    <select idref="RHEL-07-010074" selected="true" />
-    <select idref="RHEL-07-010071" selected="true" />
-    <select idref="RHEL-07-010072" selected="true" />
-    <select idref="RHEL-07-010073" selected="true" />
-    <select idref="RHEL-07-010090" selected="true" />
-    <select idref="RHEL-07-010100" selected="true" />
-    <select idref="RHEL-07-010110" selected="true" />
-    <select idref="RHEL-07-010120" selected="true" />
-    <select idref="RHEL-07-010130" selected="true" />
-    <select idref="RHEL-07-010140" selected="true" />
-    <select idref="RHEL-07-010150" selected="true" />
-    <select idref="RHEL-07-010160" selected="true" />
-    <select idref="RHEL-07-010170" selected="true" />
-    <select idref="RHEL-07-010180" selected="true" />
-    <select idref="RHEL-07-010190" selected="true" />
-    <select idref="RHEL-07-010200" selected="true" />
-    <select idref="RHEL-07-010210" selected="true" />
-    <select idref="RHEL-07-010220" selected="true" />
-    <select idref="RHEL-07-010230" selected="true" />
-    <select idref="RHEL-07-010240" selected="true" />
-    <select idref="RHEL-07-010250" selected="true" />
-    <select idref="RHEL-07-010260" selected="true" />
-    <select idref="RHEL-07-010270" selected="true" />
-    <select idref="RHEL-07-010280" selected="true" />
-    <select idref="RHEL-07-010371" selected="true" />
-    <select idref="RHEL-07-010372" selected="true" />
-    <select idref="RHEL-07-010373" selected="true" />
-    <select idref="RHEL-07-010380" selected="true" />
-    <select idref="RHEL-07-010381" selected="true" />
-    <select idref="RHEL-07-010400" selected="true" />
-    <select idref="RHEL-07-010401" selected="true" />
-    <select idref="RHEL-07-010402" selected="true" />
-    <select idref="RHEL-07-010420" selected="true" />
-    <select idref="RHEL-07-010430" selected="true" />
-    <select idref="RHEL-07-010431" selected="true" />
-    <select idref="RHEL-07-010440" selected="true" />
-    <select idref="RHEL-07-010441" selected="true" />
-    <select idref="RHEL-07-010442" selected="true" />
-    <select idref="RHEL-07-010460" selected="true" />
-    <select idref="RHEL-07-010470" selected="true" />
-    <select idref="RHEL-07-010490" selected="true" />
-    <select idref="RHEL-07-010500" selected="true" />
-    <select idref="RHEL-07-020000" selected="true" />
-    <select idref="RHEL-07-020010" selected="true" />
-    <select idref="RHEL-07-020090" selected="true" />
-    <select idref="RHEL-07-020130" selected="true" />
-    <select idref="RHEL-07-020140" selected="true" />
-    <select idref="RHEL-07-020150" selected="true" />
-    <select idref="RHEL-07-020151" selected="true" />
-    <select idref="RHEL-07-020152" selected="true" />
-    <select idref="RHEL-07-020160" selected="true" />
-    <select idref="RHEL-07-020161" selected="true" />
-    <select idref="RHEL-07-020170" selected="true" />
-    <select idref="RHEL-07-020200" selected="true" />
-    <select idref="RHEL-07-020210" selected="true" />
-    <select idref="RHEL-07-020211" selected="true" />
-    <select idref="RHEL-07-020220" selected="true" />
-    <select idref="RHEL-07-020230" selected="true" />
-    <select idref="RHEL-07-020240" selected="true" />
-    <select idref="RHEL-07-020250" selected="true" />
-    <select idref="RHEL-07-020290" selected="true" />
-    <select idref="RHEL-07-020300" selected="true" />
-    <select idref="RHEL-07-020310" selected="true" />
-    <select idref="RHEL-07-020360" selected="true" />
-    <select idref="RHEL-07-020370" selected="true" />
-    <select idref="RHEL-07-020620" selected="true" />
-    <select idref="RHEL-07-020630" selected="true" />
-    <select idref="RHEL-07-020640" selected="true" />
-    <select idref="RHEL-07-020650" selected="true" />
-    <select idref="RHEL-07-020660" selected="true" />
-    <select idref="RHEL-07-020670" selected="true" />
-    <select idref="RHEL-07-020680" selected="true" />
-    <select idref="RHEL-07-020690" selected="true" />
-    <select idref="RHEL-07-020700" selected="true" />
-    <select idref="RHEL-07-020840" selected="true" />
-    <select idref="RHEL-07-020850" selected="true" />
-    <select idref="RHEL-07-020860" selected="true" />
-    <select idref="RHEL-07-020870" selected="true" />
-    <select idref="RHEL-07-020880" selected="true" />
-    <select idref="RHEL-07-020940" selected="true" />
-    <select idref="RHEL-07-021010" selected="true" />
-    <select idref="RHEL-07-021011" selected="true" />
-    <select idref="RHEL-07-021012" selected="true" />
-    <select idref="RHEL-07-021050" selected="true" />
-    <select idref="RHEL-07-021060" selected="true" />
-    <select idref="RHEL-07-021160" selected="true" />
-    <select idref="RHEL-07-021190" selected="true" />
-    <select idref="RHEL-07-021200" selected="true" />
-    <select idref="RHEL-07-021230" selected="true" />
-    <select idref="RHEL-07-021240" selected="true" />
-    <select idref="RHEL-07-021250" selected="true" />
-    <select idref="RHEL-07-021260" selected="true" />
-    <select idref="RHEL-07-021270" selected="true" />
-    <select idref="RHEL-07-021280" selected="true" />
-    <select idref="RHEL-07-021600" selected="true" />
-    <select idref="RHEL-07-021610" selected="true" />
-    <select idref="RHEL-07-021620" selected="true" />
-    <select idref="RHEL-07-021760" selected="true" />
-    <select idref="RHEL-07-021910" selected="true" />
-    <select idref="RHEL-07-030010" selected="true" />
-    <select idref="RHEL-07-030090" selected="true" />
-    <select idref="RHEL-07-030310" selected="true" />
-    <select idref="RHEL-07-030330" selected="true" />
-    <select idref="RHEL-07-030331" selected="true" />
-    <select idref="RHEL-07-030340" selected="true" />
-    <select idref="RHEL-07-030350" selected="true" />
-    <select idref="RHEL-07-030351" selected="true" />
-    <select idref="RHEL-07-030352" selected="true" />
-    <select idref="RHEL-07-030380" selected="true" />
-    <select idref="RHEL-07-030381" selected="true" />
-    <select idref="RHEL-07-030382" selected="true" />
-    <select idref="RHEL-07-030383" selected="true" />
-    <select idref="RHEL-07-030390" selected="true" />
-    <select idref="RHEL-07-030391" selected="true" />
-    <select idref="RHEL-07-030392" selected="true" />
-    <select idref="RHEL-07-030400" selected="true" />
-    <select idref="RHEL-07-030401" selected="true" />
-    <select idref="RHEL-07-030402" selected="true" />
-    <select idref="RHEL-07-030403" selected="true" />
-    <select idref="RHEL-07-030404" selected="true" />
-    <select idref="RHEL-07-030405" selected="true" />
-    <select idref="RHEL-07-030420" selected="true" />
-    <select idref="RHEL-07-030421" selected="true" />
-    <select idref="RHEL-07-030422" selected="true" />
-    <select idref="RHEL-07-030423" selected="true" />
-    <select idref="RHEL-07-030424" selected="true" />
-    <select idref="RHEL-07-030425" selected="true" />
-    <select idref="RHEL-07-030441" selected="true" />
-    <select idref="RHEL-07-030442" selected="true" />
-    <select idref="RHEL-07-030443" selected="true" />
-    <select idref="RHEL-07-030444" selected="true" />
-    <select idref="RHEL-07-030490" selected="true" />
-    <select idref="RHEL-07-030491" selected="true" />
-    <select idref="RHEL-07-030492" selected="true" />
-    <select idref="RHEL-07-030510" selected="true" />
-    <select idref="RHEL-07-030511" selected="true" />
-    <select idref="RHEL-07-030512" selected="true" />
-    <select idref="RHEL-07-030513" selected="true" />
-    <select idref="RHEL-07-030514" selected="true" />
-    <select idref="RHEL-07-030521" selected="true" />
-    <select idref="RHEL-07-030522" selected="true" />
-    <select idref="RHEL-07-030526" selected="true" />
-    <select idref="RHEL-07-030523" selected="true" />
-    <select idref="RHEL-07-030524" selected="true" />
-    <select idref="RHEL-07-030525" selected="true" />
-    <select idref="RHEL-07-030530" selected="true" />
-    <select idref="RHEL-07-030531" selected="true" />
-    <select idref="RHEL-07-030540" selected="true" />
-    <select idref="RHEL-07-030541" selected="true" />
-    <select idref="RHEL-07-030550" selected="true" />
-    <select idref="RHEL-07-030560" selected="true" />
-    <select idref="RHEL-07-030561" selected="true" />
-    <select idref="RHEL-07-030630" selected="true" />
-    <select idref="RHEL-07-030670" selected="true" />
-    <select idref="RHEL-07-030671" selected="true" />
-    <select idref="RHEL-07-030672" selected="true" />
-    <select idref="RHEL-07-030673" selected="true" />
-    <select idref="RHEL-07-030674" selected="true" />
-    <select idref="RHEL-07-030710" selected="true" />
-    <select idref="RHEL-07-030750" selected="true" />
-    <select idref="RHEL-07-030751" selected="true" />
-    <select idref="RHEL-07-030752" selected="true" />
-    <select idref="RHEL-07-030753" selected="true" />
-    <select idref="RHEL-07-030754" selected="true" />
-    <select idref="RHEL-07-030770" selected="true" />
-    <select idref="RHEL-07-030780" selected="true" />
-    <select idref="RHEL-07-030810" selected="true" />
-    <select idref="RHEL-07-030820" selected="true" />
-    <select idref="RHEL-07-040010" selected="true" />
-    <select idref="RHEL-07-040020" selected="true" />
-    <select idref="RHEL-07-040030" selected="true" />
-    <select idref="RHEL-07-040040" selected="true" />
-    <select idref="RHEL-07-040050" selected="true" />
-    <select idref="RHEL-07-040060" selected="true" />
-    <select idref="RHEL-07-040070" selected="true" />
-    <select idref="RHEL-07-040080" selected="true" />
-    <select idref="RHEL-07-040100" selected="true" />
-    <select idref="RHEL-07-040110" selected="true" />
-    <select idref="RHEL-07-040160" selected="true" />
-    <select idref="RHEL-07-040170" selected="true" />
-    <select idref="RHEL-07-040180" selected="true" />
-    <select idref="RHEL-07-040181" selected="true" />
-    <select idref="RHEL-07-040182" selected="true" />
-    <select idref="RHEL-07-040190" selected="true" />
-    <select idref="RHEL-07-040191" selected="true" />
-    <select idref="RHEL-07-040210" selected="true" />
-    <select idref="RHEL-07-040230" selected="true" />
-    <select idref="RHEL-07-040250" selected="true" />
-    <select idref="RHEL-07-040260" selected="true" />
-    <select idref="RHEL-07-040261" selected="true" />
-    <select idref="RHEL-07-040290" selected="true" />
-    <select idref="RHEL-07-040300" selected="true" />
-    <select idref="RHEL-07-040301" selected="true" />
-    <select idref="RHEL-07-040310" selected="true" />
-    <select idref="RHEL-07-040320" selected="true" />
-    <select idref="RHEL-07-040330" selected="true" />
-    <select idref="RHEL-07-040331" selected="true" />
-    <select idref="RHEL-07-040334" selected="true" />
-    <select idref="RHEL-07-040332" selected="true" />
-    <select idref="RHEL-07-040333" selected="true" />
-    <select idref="RHEL-07-040350" selected="true" />
-    <select idref="RHEL-07-040351" selected="true" />
-    <select idref="RHEL-07-040380" selected="true" />
-    <select idref="RHEL-07-040410" selected="true" />
-    <select idref="RHEL-07-040420" selected="true" />
-    <select idref="RHEL-07-040421" selected="true" />
-    <select idref="RHEL-07-040470" selected="true" />
-    <select idref="RHEL-07-040480" selected="true" />
-    <select idref="RHEL-07-040490" selected="true" />
-    <select idref="RHEL-07-040500" selected="true" />
-    <select idref="RHEL-07-040520" selected="true" />
-    <select idref="RHEL-07-040540" selected="true" />
-    <select idref="RHEL-07-040560" selected="true" />
-    <select idref="RHEL-07-040580" selected="true" />
-    <select idref="RHEL-07-040590" selected="true" />
-    <select idref="RHEL-07-040620" selected="true" />
-    <select idref="RHEL-07-040640" selected="true" />
-    <select idref="RHEL-07-040650" selected="true" />
-    <select idref="RHEL-07-040660" selected="true" />
-    <select idref="RHEL-07-040670" selected="true" />
-    <select idref="RHEL-07-040680" selected="true" />
-    <select idref="RHEL-07-040690" selected="true" />
-    <select idref="RHEL-07-040700" selected="true" />
-    <select idref="RHEL-07-040730" selected="true" />
-    <select idref="RHEL-07-040740" selected="true" />
-    <select idref="RHEL-07-040810" selected="true" />
-    <select idref="RHEL-07-040820" selected="true" />
-    <select idref="RHEL-07-040830" selected="true" />
-    <select idref="RHEL-07-040860" selected="true" />
-  </Profile>
-  <Profile id="MAC-1_Sensitive">
-    <title>I - Mission Critical Sensitive</title>
-    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
-    <select idref="RHEL-07-010010" selected="true" />
-    <select idref="RHEL-07-010020" selected="true" />
-    <select idref="RHEL-07-010030" selected="true" />
-    <select idref="RHEL-07-010031" selected="true" />
-    <select idref="RHEL-07-010040" selected="true" />
-    <select idref="RHEL-07-010060" selected="true" />
-    <select idref="RHEL-07-010070" selected="true" />
-    <select idref="RHEL-07-010074" selected="true" />
-    <select idref="RHEL-07-010071" selected="true" />
-    <select idref="RHEL-07-010072" selected="true" />
-    <select idref="RHEL-07-010073" selected="true" />
-    <select idref="RHEL-07-010090" selected="true" />
-    <select idref="RHEL-07-010100" selected="true" />
-    <select idref="RHEL-07-010110" selected="true" />
-    <select idref="RHEL-07-010120" selected="true" />
-    <select idref="RHEL-07-010130" selected="true" />
-    <select idref="RHEL-07-010140" selected="true" />
-    <select idref="RHEL-07-010150" selected="true" />
-    <select idref="RHEL-07-010160" selected="true" />
-    <select idref="RHEL-07-010170" selected="true" />
-    <select idref="RHEL-07-010180" selected="true" />
-    <select idref="RHEL-07-010190" selected="true" />
-    <select idref="RHEL-07-010200" selected="true" />
-    <select idref="RHEL-07-010210" selected="true" />
-    <select idref="RHEL-07-010220" selected="true" />
-    <select idref="RHEL-07-010230" selected="true" />
-    <select idref="RHEL-07-010240" selected="true" />
-    <select idref="RHEL-07-010250" selected="true" />
-    <select idref="RHEL-07-010260" selected="true" />
-    <select idref="RHEL-07-010270" selected="true" />
-    <select idref="RHEL-07-010280" selected="true" />
-    <select idref="RHEL-07-010371" selected="true" />
-    <select idref="RHEL-07-010372" selected="true" />
-    <select idref="RHEL-07-010373" selected="true" />
-    <select idref="RHEL-07-010380" selected="true" />
-    <select idref="RHEL-07-010381" selected="true" />
-    <select idref="RHEL-07-010400" selected="true" />
-    <select idref="RHEL-07-010401" selected="true" />
-    <select idref="RHEL-07-010402" selected="true" />
-    <select idref="RHEL-07-010420" selected="true" />
-    <select idref="RHEL-07-010430" selected="true" />
-    <select idref="RHEL-07-010431" selected="true" />
-    <select idref="RHEL-07-010440" selected="true" />
-    <select idref="RHEL-07-010441" selected="true" />
-    <select idref="RHEL-07-010442" selected="true" />
-    <select idref="RHEL-07-010460" selected="true" />
-    <select idref="RHEL-07-010470" selected="true" />
-    <select idref="RHEL-07-010490" selected="true" />
-    <select idref="RHEL-07-010500" selected="true" />
-    <select idref="RHEL-07-020000" selected="true" />
-    <select idref="RHEL-07-020010" selected="true" />
-    <select idref="RHEL-07-020090" selected="true" />
-    <select idref="RHEL-07-020130" selected="true" />
-    <select idref="RHEL-07-020140" selected="true" />
-    <select idref="RHEL-07-020150" selected="true" />
-    <select idref="RHEL-07-020151" selected="true" />
-    <select idref="RHEL-07-020152" selected="true" />
-    <select idref="RHEL-07-020160" selected="true" />
-    <select idref="RHEL-07-020161" selected="true" />
-    <select idref="RHEL-07-020170" selected="true" />
-    <select idref="RHEL-07-020200" selected="true" />
-    <select idref="RHEL-07-020210" selected="true" />
-    <select idref="RHEL-07-020211" selected="true" />
-    <select idref="RHEL-07-020220" selected="true" />
-    <select idref="RHEL-07-020230" selected="true" />
-    <select idref="RHEL-07-020240" selected="true" />
-    <select idref="RHEL-07-020250" selected="true" />
-    <select idref="RHEL-07-020290" selected="true" />
-    <select idref="RHEL-07-020300" selected="true" />
-    <select idref="RHEL-07-020310" selected="true" />
-    <select idref="RHEL-07-020360" selected="true" />
-    <select idref="RHEL-07-020370" selected="true" />
-    <select idref="RHEL-07-020620" selected="true" />
-    <select idref="RHEL-07-020630" selected="true" />
-    <select idref="RHEL-07-020640" selected="true" />
-    <select idref="RHEL-07-020650" selected="true" />
-    <select idref="RHEL-07-020660" selected="true" />
-    <select idref="RHEL-07-020670" selected="true" />
-    <select idref="RHEL-07-020680" selected="true" />
-    <select idref="RHEL-07-020690" selected="true" />
-    <select idref="RHEL-07-020700" selected="true" />
-    <select idref="RHEL-07-020840" selected="true" />
-    <select idref="RHEL-07-020850" selected="true" />
-    <select idref="RHEL-07-020860" selected="true" />
-    <select idref="RHEL-07-020870" selected="true" />
-    <select idref="RHEL-07-020880" selected="true" />
-    <select idref="RHEL-07-020940" selected="true" />
-    <select idref="RHEL-07-021010" selected="true" />
-    <select idref="RHEL-07-021011" selected="true" />
-    <select idref="RHEL-07-021012" selected="true" />
-    <select idref="RHEL-07-021050" selected="true" />
-    <select idref="RHEL-07-021060" selected="true" />
-    <select idref="RHEL-07-021160" selected="true" />
-    <select idref="RHEL-07-021190" selected="true" />
-    <select idref="RHEL-07-021200" selected="true" />
-    <select idref="RHEL-07-021230" selected="true" />
-    <select idref="RHEL-07-021240" selected="true" />
-    <select idref="RHEL-07-021250" selected="true" />
-    <select idref="RHEL-07-021260" selected="true" />
-    <select idref="RHEL-07-021270" selected="true" />
-    <select idref="RHEL-07-021280" selected="true" />
-    <select idref="RHEL-07-021600" selected="true" />
-    <select idref="RHEL-07-021610" selected="true" />
-    <select idref="RHEL-07-021620" selected="true" />
-    <select idref="RHEL-07-021760" selected="true" />
-    <select idref="RHEL-07-021910" selected="true" />
-    <select idref="RHEL-07-030010" selected="true" />
-    <select idref="RHEL-07-030090" selected="true" />
-    <select idref="RHEL-07-030310" selected="true" />
-    <select idref="RHEL-07-030330" selected="true" />
-    <select idref="RHEL-07-030331" selected="true" />
-    <select idref="RHEL-07-030340" selected="true" />
-    <select idref="RHEL-07-030350" selected="true" />
-    <select idref="RHEL-07-030351" selected="true" />
-    <select idref="RHEL-07-030352" selected="true" />
-    <select idref="RHEL-07-030380" selected="true" />
-    <select idref="RHEL-07-030381" selected="true" />
-    <select idref="RHEL-07-030382" selected="true" />
-    <select idref="RHEL-07-030383" selected="true" />
-    <select idref="RHEL-07-030390" selected="true" />
-    <select idref="RHEL-07-030391" selected="true" />
-    <select idref="RHEL-07-030392" selected="true" />
-    <select idref="RHEL-07-030400" selected="true" />
-    <select idref="RHEL-07-030401" selected="true" />
-    <select idref="RHEL-07-030402" selected="true" />
-    <select idref="RHEL-07-030403" selected="true" />
-    <select idref="RHEL-07-030404" selected="true" />
-    <select idref="RHEL-07-030405" selected="true" />
-    <select idref="RHEL-07-030420" selected="true" />
-    <select idref="RHEL-07-030421" selected="true" />
-    <select idref="RHEL-07-030422" selected="true" />
-    <select idref="RHEL-07-030423" selected="true" />
-    <select idref="RHEL-07-030424" selected="true" />
-    <select idref="RHEL-07-030425" selected="true" />
-    <select idref="RHEL-07-030441" selected="true" />
-    <select idref="RHEL-07-030442" selected="true" />
-    <select idref="RHEL-07-030443" selected="true" />
-    <select idref="RHEL-07-030444" selected="true" />
-    <select idref="RHEL-07-030490" selected="true" />
-    <select idref="RHEL-07-030491" selected="true" />
-    <select idref="RHEL-07-030492" selected="true" />
-    <select idref="RHEL-07-030510" selected="true" />
-    <select idref="RHEL-07-030511" selected="true" />
-    <select idref="RHEL-07-030512" selected="true" />
-    <select idref="RHEL-07-030513" selected="true" />
-    <select idref="RHEL-07-030514" selected="true" />
-    <select idref="RHEL-07-030521" selected="true" />
-    <select idref="RHEL-07-030522" selected="true" />
-    <select idref="RHEL-07-030526" selected="true" />
-    <select idref="RHEL-07-030523" selected="true" />
-    <select idref="RHEL-07-030524" selected="true" />
-    <select idref="RHEL-07-030525" selected="true" />
-    <select idref="RHEL-07-030530" selected="true" />
-    <select idref="RHEL-07-030531" selected="true" />
-    <select idref="RHEL-07-030540" selected="true" />
-    <select idref="RHEL-07-030541" selected="true" />
-    <select idref="RHEL-07-030550" selected="true" />
-    <select idref="RHEL-07-030560" selected="true" />
-    <select idref="RHEL-07-030561" selected="true" />
-    <select idref="RHEL-07-030630" selected="true" />
-    <select idref="RHEL-07-030670" selected="true" />
-    <select idref="RHEL-07-030671" selected="true" />
-    <select idref="RHEL-07-030672" selected="true" />
-    <select idref="RHEL-07-030673" selected="true" />
-    <select idref="RHEL-07-030674" selected="true" />
-    <select idref="RHEL-07-030710" selected="true" />
-    <select idref="RHEL-07-030750" selected="true" />
-    <select idref="RHEL-07-030751" selected="true" />
-    <select idref="RHEL-07-030752" selected="true" />
-    <select idref="RHEL-07-030753" selected="true" />
-    <select idref="RHEL-07-030754" selected="true" />
-    <select idref="RHEL-07-030770" selected="true" />
-    <select idref="RHEL-07-030780" selected="true" />
-    <select idref="RHEL-07-030810" selected="true" />
-    <select idref="RHEL-07-030820" selected="true" />
-    <select idref="RHEL-07-040010" selected="true" />
-    <select idref="RHEL-07-040020" selected="true" />
-    <select idref="RHEL-07-040030" selected="true" />
-    <select idref="RHEL-07-040040" selected="true" />
-    <select idref="RHEL-07-040050" selected="true" />
-    <select idref="RHEL-07-040060" selected="true" />
-    <select idref="RHEL-07-040070" selected="true" />
-    <select idref="RHEL-07-040080" selected="true" />
-    <select idref="RHEL-07-040100" selected="true" />
-    <select idref="RHEL-07-040110" selected="true" />
-    <select idref="RHEL-07-040160" selected="true" />
-    <select idref="RHEL-07-040170" selected="true" />
-    <select idref="RHEL-07-040180" selected="true" />
-    <select idref="RHEL-07-040181" selected="true" />
-    <select idref="RHEL-07-040182" selected="true" />
-    <select idref="RHEL-07-040190" selected="true" />
-    <select idref="RHEL-07-040191" selected="true" />
-    <select idref="RHEL-07-040210" selected="true" />
-    <select idref="RHEL-07-040230" selected="true" />
-    <select idref="RHEL-07-040250" selected="true" />
-    <select idref="RHEL-07-040260" selected="true" />
-    <select idref="RHEL-07-040261" selected="true" />
-    <select idref="RHEL-07-040290" selected="true" />
-    <select idref="RHEL-07-040300" selected="true" />
-    <select idref="RHEL-07-040301" selected="true" />
-    <select idref="RHEL-07-040310" selected="true" />
-    <select idref="RHEL-07-040320" selected="true" />
-    <select idref="RHEL-07-040330" selected="true" />
-    <select idref="RHEL-07-040331" selected="true" />
-    <select idref="RHEL-07-040334" selected="true" />
-    <select idref="RHEL-07-040332" selected="true" />
-    <select idref="RHEL-07-040333" selected="true" />
-    <select idref="RHEL-07-040350" selected="true" />
-    <select idref="RHEL-07-040351" selected="true" />
-    <select idref="RHEL-07-040380" selected="true" />
-    <select idref="RHEL-07-040410" selected="true" />
-    <select idref="RHEL-07-040420" selected="true" />
-    <select idref="RHEL-07-040421" selected="true" />
-    <select idref="RHEL-07-040470" selected="true" />
-    <select idref="RHEL-07-040480" selected="true" />
-    <select idref="RHEL-07-040490" selected="true" />
-    <select idref="RHEL-07-040500" selected="true" />
-    <select idref="RHEL-07-040520" selected="true" />
-    <select idref="RHEL-07-040540" selected="true" />
-    <select idref="RHEL-07-040560" selected="true" />
-    <select idref="RHEL-07-040580" selected="true" />
-    <select idref="RHEL-07-040590" selected="true" />
-    <select idref="RHEL-07-040620" selected="true" />
-    <select idref="RHEL-07-040640" selected="true" />
-    <select idref="RHEL-07-040650" selected="true" />
-    <select idref="RHEL-07-040660" selected="true" />
-    <select idref="RHEL-07-040670" selected="true" />
-    <select idref="RHEL-07-040680" selected="true" />
-    <select idref="RHEL-07-040690" selected="true" />
-    <select idref="RHEL-07-040700" selected="true" />
-    <select idref="RHEL-07-040730" selected="true" />
-    <select idref="RHEL-07-040740" selected="true" />
-    <select idref="RHEL-07-040810" selected="true" />
-    <select idref="RHEL-07-040820" selected="true" />
-    <select idref="RHEL-07-040830" selected="true" />
-    <select idref="RHEL-07-040860" selected="true" />
-  </Profile>
-  <Profile id="MAC-1_Classified">
-    <title>I - Mission Critical Classified</title>
-    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
-    <select idref="RHEL-07-010010" selected="true" />
-    <select idref="RHEL-07-010020" selected="true" />
-    <select idref="RHEL-07-010030" selected="true" />
-    <select idref="RHEL-07-010031" selected="true" />
-    <select idref="RHEL-07-010040" selected="true" />
-    <select idref="RHEL-07-010060" selected="true" />
-    <select idref="RHEL-07-010070" selected="true" />
-    <select idref="RHEL-07-010074" selected="true" />
-    <select idref="RHEL-07-010071" selected="true" />
-    <select idref="RHEL-07-010072" selected="true" />
-    <select idref="RHEL-07-010073" selected="true" />
-    <select idref="RHEL-07-010090" selected="true" />
-    <select idref="RHEL-07-010100" selected="true" />
-    <select idref="RHEL-07-010110" selected="true" />
-    <select idref="RHEL-07-010120" selected="true" />
-    <select idref="RHEL-07-010130" selected="true" />
-    <select idref="RHEL-07-010140" selected="true" />
-    <select idref="RHEL-07-010150" selected="true" />
-    <select idref="RHEL-07-010160" selected="true" />
-    <select idref="RHEL-07-010170" selected="true" />
-    <select idref="RHEL-07-010180" selected="true" />
-    <select idref="RHEL-07-010190" selected="true" />
-    <select idref="RHEL-07-010200" selected="true" />
-    <select idref="RHEL-07-010210" selected="true" />
-    <select idref="RHEL-07-010220" selected="true" />
-    <select idref="RHEL-07-010230" selected="true" />
-    <select idref="RHEL-07-010240" selected="true" />
-    <select idref="RHEL-07-010250" selected="true" />
-    <select idref="RHEL-07-010260" selected="true" />
-    <select idref="RHEL-07-010270" selected="true" />
-    <select idref="RHEL-07-010280" selected="true" />
-    <select idref="RHEL-07-010371" selected="true" />
-    <select idref="RHEL-07-010372" selected="true" />
-    <select idref="RHEL-07-010373" selected="true" />
-    <select idref="RHEL-07-010380" selected="true" />
-    <select idref="RHEL-07-010381" selected="true" />
-    <select idref="RHEL-07-010400" selected="true" />
-    <select idref="RHEL-07-010401" selected="true" />
-    <select idref="RHEL-07-010402" selected="true" />
-    <select idref="RHEL-07-010420" selected="true" />
-    <select idref="RHEL-07-010430" selected="true" />
-    <select idref="RHEL-07-010431" selected="true" />
-    <select idref="RHEL-07-010440" selected="true" />
-    <select idref="RHEL-07-010441" selected="true" />
-    <select idref="RHEL-07-010442" selected="true" />
-    <select idref="RHEL-07-010460" selected="true" />
-    <select idref="RHEL-07-010470" selected="true" />
-    <select idref="RHEL-07-010490" selected="true" />
-    <select idref="RHEL-07-010500" selected="true" />
-    <select idref="RHEL-07-020000" selected="true" />
-    <select idref="RHEL-07-020010" selected="true" />
-    <select idref="RHEL-07-020090" selected="true" />
-    <select idref="RHEL-07-020130" selected="true" />
-    <select idref="RHEL-07-020140" selected="true" />
-    <select idref="RHEL-07-020150" selected="true" />
-    <select idref="RHEL-07-020151" selected="true" />
-    <select idref="RHEL-07-020152" selected="true" />
-    <select idref="RHEL-07-020160" selected="true" />
-    <select idref="RHEL-07-020161" selected="true" />
-    <select idref="RHEL-07-020170" selected="true" />
-    <select idref="RHEL-07-020200" selected="true" />
-    <select idref="RHEL-07-020210" selected="true" />
-    <select idref="RHEL-07-020211" selected="true" />
-    <select idref="RHEL-07-020220" selected="true" />
-    <select idref="RHEL-07-020230" selected="true" />
-    <select idref="RHEL-07-020240" selected="true" />
-    <select idref="RHEL-07-020250" selected="true" />
-    <select idref="RHEL-07-020290" selected="true" />
-    <select idref="RHEL-07-020300" selected="true" />
-    <select idref="RHEL-07-020310" selected="true" />
-    <select idref="RHEL-07-020360" selected="true" />
-    <select idref="RHEL-07-020370" selected="true" />
-    <select idref="RHEL-07-020620" selected="true" />
-    <select idref="RHEL-07-020630" selected="true" />
-    <select idref="RHEL-07-020640" selected="true" />
-    <select idref="RHEL-07-020650" selected="true" />
-    <select idref="RHEL-07-020660" selected="true" />
-    <select idref="RHEL-07-020670" selected="true" />
-    <select idref="RHEL-07-020680" selected="true" />
-    <select idref="RHEL-07-020690" selected="true" />
-    <select idref="RHEL-07-020700" selected="true" />
-    <select idref="RHEL-07-020840" selected="true" />
-    <select idref="RHEL-07-020850" selected="true" />
-    <select idref="RHEL-07-020860" selected="true" />
-    <select idref="RHEL-07-020870" selected="true" />
-    <select idref="RHEL-07-020880" selected="true" />
-    <select idref="RHEL-07-020940" selected="true" />
-    <select idref="RHEL-07-021010" selected="true" />
-    <select idref="RHEL-07-021011" selected="true" />
-    <select idref="RHEL-07-021012" selected="true" />
-    <select idref="RHEL-07-021050" selected="true" />
-    <select idref="RHEL-07-021060" selected="true" />
-    <select idref="RHEL-07-021160" selected="true" />
-    <select idref="RHEL-07-021190" selected="true" />
-    <select idref="RHEL-07-021200" selected="true" />
-    <select idref="RHEL-07-021230" selected="true" />
-    <select idref="RHEL-07-021240" selected="true" />
-    <select idref="RHEL-07-021250" selected="true" />
-    <select idref="RHEL-07-021260" selected="true" />
-    <select idref="RHEL-07-021270" selected="true" />
-    <select idref="RHEL-07-021280" selected="true" />
-    <select idref="RHEL-07-021600" selected="true" />
-    <select idref="RHEL-07-021610" selected="true" />
-    <select idref="RHEL-07-021620" selected="true" />
-    <select idref="RHEL-07-021760" selected="true" />
-    <select idref="RHEL-07-021910" selected="true" />
-    <select idref="RHEL-07-030010" selected="true" />
-    <select idref="RHEL-07-030090" selected="true" />
-    <select idref="RHEL-07-030310" selected="true" />
-    <select idref="RHEL-07-030330" selected="true" />
-    <select idref="RHEL-07-030331" selected="true" />
-    <select idref="RHEL-07-030340" selected="true" />
-    <select idref="RHEL-07-030350" selected="true" />
-    <select idref="RHEL-07-030351" selected="true" />
-    <select idref="RHEL-07-030352" selected="true" />
-    <select idref="RHEL-07-030380" selected="true" />
-    <select idref="RHEL-07-030381" selected="true" />
-    <select idref="RHEL-07-030382" selected="true" />
-    <select idref="RHEL-07-030383" selected="true" />
-    <select idref="RHEL-07-030390" selected="true" />
-    <select idref="RHEL-07-030391" selected="true" />
-    <select idref="RHEL-07-030392" selected="true" />
-    <select idref="RHEL-07-030400" selected="true" />
-    <select idref="RHEL-07-030401" selected="true" />
-    <select idref="RHEL-07-030402" selected="true" />
-    <select idref="RHEL-07-030403" selected="true" />
-    <select idref="RHEL-07-030404" selected="true" />
-    <select idref="RHEL-07-030405" selected="true" />
-    <select idref="RHEL-07-030420" selected="true" />
-    <select idref="RHEL-07-030421" selected="true" />
-    <select idref="RHEL-07-030422" selected="true" />
-    <select idref="RHEL-07-030423" selected="true" />
-    <select idref="RHEL-07-030424" selected="true" />
-    <select idref="RHEL-07-030425" selected="true" />
-    <select idref="RHEL-07-030441" selected="true" />
-    <select idref="RHEL-07-030442" selected="true" />
-    <select idref="RHEL-07-030443" selected="true" />
-    <select idref="RHEL-07-030444" selected="true" />
-    <select idref="RHEL-07-030490" selected="true" />
-    <select idref="RHEL-07-030491" selected="true" />
-    <select idref="RHEL-07-030492" selected="true" />
-    <select idref="RHEL-07-030510" selected="true" />
-    <select idref="RHEL-07-030511" selected="true" />
-    <select idref="RHEL-07-030512" selected="true" />
-    <select idref="RHEL-07-030513" selected="true" />
-    <select idref="RHEL-07-030514" selected="true" />
-    <select idref="RHEL-07-030521" selected="true" />
-    <select idref="RHEL-07-030522" selected="true" />
-    <select idref="RHEL-07-030526" selected="true" />
-    <select idref="RHEL-07-030523" selected="true" />
-    <select idref="RHEL-07-030524" selected="true" />
-    <select idref="RHEL-07-030525" selected="true" />
-    <select idref="RHEL-07-030530" selected="true" />
-    <select idref="RHEL-07-030531" selected="true" />
-    <select idref="RHEL-07-030540" selected="true" />
-    <select idref="RHEL-07-030541" selected="true" />
-    <select idref="RHEL-07-030550" selected="true" />
-    <select idref="RHEL-07-030560" selected="true" />
-    <select idref="RHEL-07-030561" selected="true" />
-    <select idref="RHEL-07-030630" selected="true" />
-    <select idref="RHEL-07-030670" selected="true" />
-    <select idref="RHEL-07-030671" selected="true" />
-    <select idref="RHEL-07-030672" selected="true" />
-    <select idref="RHEL-07-030673" selected="true" />
-    <select idref="RHEL-07-030674" selected="true" />
-    <select idref="RHEL-07-030710" selected="true" />
-    <select idref="RHEL-07-030750" selected="true" />
-    <select idref="RHEL-07-030751" selected="true" />
-    <select idref="RHEL-07-030752" selected="true" />
-    <select idref="RHEL-07-030753" selected="true" />
-    <select idref="RHEL-07-030754" selected="true" />
-    <select idref="RHEL-07-030770" selected="true" />
-    <select idref="RHEL-07-030780" selected="true" />
-    <select idref="RHEL-07-030810" selected="true" />
-    <select idref="RHEL-07-030820" selected="true" />
-    <select idref="RHEL-07-040010" selected="true" />
-    <select idref="RHEL-07-040020" selected="true" />
-    <select idref="RHEL-07-040030" selected="true" />
-    <select idref="RHEL-07-040040" selected="true" />
-    <select idref="RHEL-07-040050" selected="true" />
-    <select idref="RHEL-07-040060" selected="true" />
-    <select idref="RHEL-07-040070" selected="true" />
-    <select idref="RHEL-07-040080" selected="true" />
-    <select idref="RHEL-07-040100" selected="true" />
-    <select idref="RHEL-07-040110" selected="true" />
-    <select idref="RHEL-07-040160" selected="true" />
-    <select idref="RHEL-07-040170" selected="true" />
-    <select idref="RHEL-07-040180" selected="true" />
-    <select idref="RHEL-07-040181" selected="true" />
-    <select idref="RHEL-07-040182" selected="true" />
-    <select idref="RHEL-07-040190" selected="true" />
-    <select idref="RHEL-07-040191" selected="true" />
-    <select idref="RHEL-07-040210" selected="true" />
-    <select idref="RHEL-07-040230" selected="true" />
-    <select idref="RHEL-07-040250" selected="true" />
-    <select idref="RHEL-07-040260" selected="true" />
-    <select idref="RHEL-07-040261" selected="true" />
-    <select idref="RHEL-07-040290" selected="true" />
-    <select idref="RHEL-07-040300" selected="true" />
-    <select idref="RHEL-07-040301" selected="true" />
-    <select idref="RHEL-07-040310" selected="true" />
-    <select idref="RHEL-07-040320" selected="true" />
-    <select idref="RHEL-07-040330" selected="true" />
-    <select idref="RHEL-07-040331" selected="true" />
-    <select idref="RHEL-07-040334" selected="true" />
-    <select idref="RHEL-07-040332" selected="true" />
-    <select idref="RHEL-07-040333" selected="true" />
-    <select idref="RHEL-07-040350" selected="true" />
-    <select idref="RHEL-07-040351" selected="true" />
-    <select idref="RHEL-07-040380" selected="true" />
-    <select idref="RHEL-07-040410" selected="true" />
-    <select idref="RHEL-07-040420" selected="true" />
-    <select idref="RHEL-07-040421" selected="true" />
-    <select idref="RHEL-07-040470" selected="true" />
-    <select idref="RHEL-07-040480" selected="true" />
-    <select idref="RHEL-07-040490" selected="true" />
-    <select idref="RHEL-07-040500" selected="true" />
-    <select idref="RHEL-07-040520" selected="true" />
-    <select idref="RHEL-07-040540" selected="true" />
-    <select idref="RHEL-07-040560" selected="true" />
-    <select idref="RHEL-07-040580" selected="true" />
-    <select idref="RHEL-07-040590" selected="true" />
-    <select idref="RHEL-07-040620" selected="true" />
-    <select idref="RHEL-07-040640" selected="true" />
-    <select idref="RHEL-07-040650" selected="true" />
-    <select idref="RHEL-07-040660" selected="true" />
-    <select idref="RHEL-07-040670" selected="true" />
-    <select idref="RHEL-07-040680" selected="true" />
-    <select idref="RHEL-07-040690" selected="true" />
-    <select idref="RHEL-07-040700" selected="true" />
-    <select idref="RHEL-07-040730" selected="true" />
-    <select idref="RHEL-07-040740" selected="true" />
-    <select idref="RHEL-07-040810" selected="true" />
-    <select idref="RHEL-07-040820" selected="true" />
-    <select idref="RHEL-07-040830" selected="true" />
-    <select idref="RHEL-07-040860" selected="true" />
-  </Profile>
-  <Profile id="MAC-2_Public">
-    <title>II - Mission Support Public</title>
-    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
-    <select idref="RHEL-07-010010" selected="true" />
-    <select idref="RHEL-07-010020" selected="true" />
-    <select idref="RHEL-07-010030" selected="true" />
-    <select idref="RHEL-07-010031" selected="true" />
-    <select idref="RHEL-07-010040" selected="true" />
-    <select idref="RHEL-07-010060" selected="true" />
-    <select idref="RHEL-07-010070" selected="true" />
-    <select idref="RHEL-07-010074" selected="true" />
-    <select idref="RHEL-07-010071" selected="true" />
-    <select idref="RHEL-07-010072" selected="true" />
-    <select idref="RHEL-07-010073" selected="true" />
-    <select idref="RHEL-07-010090" selected="true" />
-    <select idref="RHEL-07-010100" selected="true" />
-    <select idref="RHEL-07-010110" selected="true" />
-    <select idref="RHEL-07-010120" selected="true" />
-    <select idref="RHEL-07-010130" selected="true" />
-    <select idref="RHEL-07-010140" selected="true" />
-    <select idref="RHEL-07-010150" selected="true" />
-    <select idref="RHEL-07-010160" selected="true" />
-    <select idref="RHEL-07-010170" selected="true" />
-    <select idref="RHEL-07-010180" selected="true" />
-    <select idref="RHEL-07-010190" selected="true" />
-    <select idref="RHEL-07-010200" selected="true" />
-    <select idref="RHEL-07-010210" selected="true" />
-    <select idref="RHEL-07-010220" selected="true" />
-    <select idref="RHEL-07-010230" selected="true" />
-    <select idref="RHEL-07-010240" selected="true" />
-    <select idref="RHEL-07-010250" selected="true" />
-    <select idref="RHEL-07-010260" selected="true" />
-    <select idref="RHEL-07-010270" selected="true" />
-    <select idref="RHEL-07-010280" selected="true" />
-    <select idref="RHEL-07-010371" selected="true" />
-    <select idref="RHEL-07-010372" selected="true" />
-    <select idref="RHEL-07-010373" selected="true" />
-    <select idref="RHEL-07-010380" selected="true" />
-    <select idref="RHEL-07-010381" selected="true" />
-    <select idref="RHEL-07-010400" selected="true" />
-    <select idref="RHEL-07-010401" selected="true" />
-    <select idref="RHEL-07-010402" selected="true" />
-    <select idref="RHEL-07-010420" selected="true" />
-    <select idref="RHEL-07-010430" selected="true" />
-    <select idref="RHEL-07-010431" selected="true" />
-    <select idref="RHEL-07-010440" selected="true" />
-    <select idref="RHEL-07-010441" selected="true" />
-    <select idref="RHEL-07-010442" selected="true" />
-    <select idref="RHEL-07-010460" selected="true" />
-    <select idref="RHEL-07-010470" selected="true" />
-    <select idref="RHEL-07-010490" selected="true" />
-    <select idref="RHEL-07-010500" selected="true" />
-    <select idref="RHEL-07-020000" selected="true" />
-    <select idref="RHEL-07-020010" selected="true" />
-    <select idref="RHEL-07-020090" selected="true" />
-    <select idref="RHEL-07-020130" selected="true" />
-    <select idref="RHEL-07-020140" selected="true" />
-    <select idref="RHEL-07-020150" selected="true" />
-    <select idref="RHEL-07-020151" selected="true" />
-    <select idref="RHEL-07-020152" selected="true" />
-    <select idref="RHEL-07-020160" selected="true" />
-    <select idref="RHEL-07-020161" selected="true" />
-    <select idref="RHEL-07-020170" selected="true" />
-    <select idref="RHEL-07-020200" selected="true" />
-    <select idref="RHEL-07-020210" selected="true" />
-    <select idref="RHEL-07-020211" selected="true" />
-    <select idref="RHEL-07-020220" selected="true" />
-    <select idref="RHEL-07-020230" selected="true" />
-    <select idref="RHEL-07-020240" selected="true" />
-    <select idref="RHEL-07-020250" selected="true" />
-    <select idref="RHEL-07-020290" selected="true" />
-    <select idref="RHEL-07-020300" selected="true" />
-    <select idref="RHEL-07-020310" selected="true" />
-    <select idref="RHEL-07-020360" selected="true" />
-    <select idref="RHEL-07-020370" selected="true" />
-    <select idref="RHEL-07-020620" selected="true" />
-    <select idref="RHEL-07-020630" selected="true" />
-    <select idref="RHEL-07-020640" selected="true" />
-    <select idref="RHEL-07-020650" selected="true" />
-    <select idref="RHEL-07-020660" selected="true" />
-    <select idref="RHEL-07-020670" selected="true" />
-    <select idref="RHEL-07-020680" selected="true" />
-    <select idref="RHEL-07-020690" selected="true" />
-    <select idref="RHEL-07-020700" selected="true" />
-    <select idref="RHEL-07-020840" selected="true" />
-    <select idref="RHEL-07-020850" selected="true" />
-    <select idref="RHEL-07-020860" selected="true" />
-    <select idref="RHEL-07-020870" selected="true" />
-    <select idref="RHEL-07-020880" selected="true" />
-    <select idref="RHEL-07-020940" selected="true" />
-    <select idref="RHEL-07-021010" selected="true" />
-    <select idref="RHEL-07-021011" selected="true" />
-    <select idref="RHEL-07-021012" selected="true" />
-    <select idref="RHEL-07-021050" selected="true" />
-    <select idref="RHEL-07-021060" selected="true" />
-    <select idref="RHEL-07-021160" selected="true" />
-    <select idref="RHEL-07-021190" selected="true" />
-    <select idref="RHEL-07-021200" selected="true" />
-    <select idref="RHEL-07-021230" selected="true" />
-    <select idref="RHEL-07-021240" selected="true" />
-    <select idref="RHEL-07-021250" selected="true" />
-    <select idref="RHEL-07-021260" selected="true" />
-    <select idref="RHEL-07-021270" selected="true" />
-    <select idref="RHEL-07-021280" selected="true" />
-    <select idref="RHEL-07-021600" selected="true" />
-    <select idref="RHEL-07-021610" selected="true" />
-    <select idref="RHEL-07-021620" selected="true" />
-    <select idref="RHEL-07-021760" selected="true" />
-    <select idref="RHEL-07-021910" selected="true" />
-    <select idref="RHEL-07-030010" selected="true" />
-    <select idref="RHEL-07-030090" selected="true" />
-    <select idref="RHEL-07-030310" selected="true" />
-    <select idref="RHEL-07-030330" selected="true" />
-    <select idref="RHEL-07-030331" selected="true" />
-    <select idref="RHEL-07-030340" selected="true" />
-    <select idref="RHEL-07-030350" selected="true" />
-    <select idref="RHEL-07-030351" selected="true" />
-    <select idref="RHEL-07-030352" selected="true" />
-    <select idref="RHEL-07-030380" selected="true" />
-    <select idref="RHEL-07-030381" selected="true" />
-    <select idref="RHEL-07-030382" selected="true" />
-    <select idref="RHEL-07-030383" selected="true" />
-    <select idref="RHEL-07-030390" selected="true" />
-    <select idref="RHEL-07-030391" selected="true" />
-    <select idref="RHEL-07-030392" selected="true" />
-    <select idref="RHEL-07-030400" selected="true" />
-    <select idref="RHEL-07-030401" selected="true" />
-    <select idref="RHEL-07-030402" selected="true" />
-    <select idref="RHEL-07-030403" selected="true" />
-    <select idref="RHEL-07-030404" selected="true" />
-    <select idref="RHEL-07-030405" selected="true" />
-    <select idref="RHEL-07-030420" selected="true" />
-    <select idref="RHEL-07-030421" selected="true" />
-    <select idref="RHEL-07-030422" selected="true" />
-    <select idref="RHEL-07-030423" selected="true" />
-    <select idref="RHEL-07-030424" selected="true" />
-    <select idref="RHEL-07-030425" selected="true" />
-    <select idref="RHEL-07-030441" selected="true" />
-    <select idref="RHEL-07-030442" selected="true" />
-    <select idref="RHEL-07-030443" selected="true" />
-    <select idref="RHEL-07-030444" selected="true" />
-    <select idref="RHEL-07-030490" selected="true" />
-    <select idref="RHEL-07-030491" selected="true" />
-    <select idref="RHEL-07-030492" selected="true" />
-    <select idref="RHEL-07-030510" selected="true" />
-    <select idref="RHEL-07-030511" selected="true" />
-    <select idref="RHEL-07-030512" selected="true" />
-    <select idref="RHEL-07-030513" selected="true" />
-    <select idref="RHEL-07-030514" selected="true" />
-    <select idref="RHEL-07-030521" selected="true" />
-    <select idref="RHEL-07-030522" selected="true" />
-    <select idref="RHEL-07-030526" selected="true" />
-    <select idref="RHEL-07-030523" selected="true" />
-    <select idref="RHEL-07-030524" selected="true" />
-    <select idref="RHEL-07-030525" selected="true" />
-    <select idref="RHEL-07-030530" selected="true" />
-    <select idref="RHEL-07-030531" selected="true" />
-    <select idref="RHEL-07-030540" selected="true" />
-    <select idref="RHEL-07-030541" selected="true" />
-    <select idref="RHEL-07-030550" selected="true" />
-    <select idref="RHEL-07-030560" selected="true" />
-    <select idref="RHEL-07-030561" selected="true" />
-    <select idref="RHEL-07-030630" selected="true" />
-    <select idref="RHEL-07-030670" selected="true" />
-    <select idref="RHEL-07-030671" selected="true" />
-    <select idref="RHEL-07-030672" selected="true" />
-    <select idref="RHEL-07-030673" selected="true" />
-    <select idref="RHEL-07-030674" selected="true" />
-    <select idref="RHEL-07-030710" selected="true" />
-    <select idref="RHEL-07-030750" selected="true" />
-    <select idref="RHEL-07-030751" selected="true" />
-    <select idref="RHEL-07-030752" selected="true" />
-    <select idref="RHEL-07-030753" selected="true" />
-    <select idref="RHEL-07-030754" selected="true" />
-    <select idref="RHEL-07-030770" selected="true" />
-    <select idref="RHEL-07-030780" selected="true" />
-    <select idref="RHEL-07-030810" selected="true" />
-    <select idref="RHEL-07-030820" selected="true" />
-    <select idref="RHEL-07-040010" selected="true" />
-    <select idref="RHEL-07-040020" selected="true" />
-    <select idref="RHEL-07-040030" selected="true" />
-    <select idref="RHEL-07-040040" selected="true" />
-    <select idref="RHEL-07-040050" selected="true" />
-    <select idref="RHEL-07-040060" selected="true" />
-    <select idref="RHEL-07-040070" selected="true" />
-    <select idref="RHEL-07-040080" selected="true" />
-    <select idref="RHEL-07-040100" selected="true" />
-    <select idref="RHEL-07-040110" selected="true" />
-    <select idref="RHEL-07-040160" selected="true" />
-    <select idref="RHEL-07-040170" selected="true" />
-    <select idref="RHEL-07-040180" selected="true" />
-    <select idref="RHEL-07-040181" selected="true" />
-    <select idref="RHEL-07-040182" selected="true" />
-    <select idref="RHEL-07-040190" selected="true" />
-    <select idref="RHEL-07-040191" selected="true" />
-    <select idref="RHEL-07-040210" selected="true" />
-    <select idref="RHEL-07-040230" selected="true" />
-    <select idref="RHEL-07-040250" selected="true" />
-    <select idref="RHEL-07-040260" selected="true" />
-    <select idref="RHEL-07-040261" selected="true" />
-    <select idref="RHEL-07-040290" selected="true" />
-    <select idref="RHEL-07-040300" selected="true" />
-    <select idref="RHEL-07-040301" selected="true" />
-    <select idref="RHEL-07-040310" selected="true" />
-    <select idref="RHEL-07-040320" selected="true" />
-    <select idref="RHEL-07-040330" selected="true" />
-    <select idref="RHEL-07-040331" selected="true" />
-    <select idref="RHEL-07-040334" selected="true" />
-    <select idref="RHEL-07-040332" selected="true" />
-    <select idref="RHEL-07-040333" selected="true" />
-    <select idref="RHEL-07-040350" selected="true" />
-    <select idref="RHEL-07-040351" selected="true" />
-    <select idref="RHEL-07-040380" selected="true" />
-    <select idref="RHEL-07-040410" selected="true" />
-    <select idref="RHEL-07-040420" selected="true" />
-    <select idref="RHEL-07-040421" selected="true" />
-    <select idref="RHEL-07-040470" selected="true" />
-    <select idref="RHEL-07-040480" selected="true" />
-    <select idref="RHEL-07-040490" selected="true" />
-    <select idref="RHEL-07-040500" selected="true" />
-    <select idref="RHEL-07-040520" selected="true" />
-    <select idref="RHEL-07-040540" selected="true" />
-    <select idref="RHEL-07-040560" selected="true" />
-    <select idref="RHEL-07-040580" selected="true" />
-    <select idref="RHEL-07-040590" selected="true" />
-    <select idref="RHEL-07-040620" selected="true" />
-    <select idref="RHEL-07-040640" selected="true" />
-    <select idref="RHEL-07-040650" selected="true" />
-    <select idref="RHEL-07-040660" selected="true" />
-    <select idref="RHEL-07-040670" selected="true" />
-    <select idref="RHEL-07-040680" selected="true" />
-    <select idref="RHEL-07-040690" selected="true" />
-    <select idref="RHEL-07-040700" selected="true" />
-    <select idref="RHEL-07-040730" selected="true" />
-    <select idref="RHEL-07-040740" selected="true" />
-    <select idref="RHEL-07-040810" selected="true" />
-    <select idref="RHEL-07-040820" selected="true" />
-    <select idref="RHEL-07-040830" selected="true" />
-    <select idref="RHEL-07-040860" selected="true" />
-  </Profile>
-  <Profile id="MAC-2_Sensitive">
-    <title>II - Mission Support Sensitive</title>
-    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
-    <select idref="RHEL-07-010010" selected="true" />
-    <select idref="RHEL-07-010020" selected="true" />
-    <select idref="RHEL-07-010030" selected="true" />
-    <select idref="RHEL-07-010031" selected="true" />
-    <select idref="RHEL-07-010040" selected="true" />
-    <select idref="RHEL-07-010060" selected="true" />
-    <select idref="RHEL-07-010070" selected="true" />
-    <select idref="RHEL-07-010074" selected="true" />
-    <select idref="RHEL-07-010071" selected="true" />
-    <select idref="RHEL-07-010072" selected="true" />
-    <select idref="RHEL-07-010073" selected="true" />
-    <select idref="RHEL-07-010090" selected="true" />
-    <select idref="RHEL-07-010100" selected="true" />
-    <select idref="RHEL-07-010110" selected="true" />
-    <select idref="RHEL-07-010120" selected="true" />
-    <select idref="RHEL-07-010130" selected="true" />
-    <select idref="RHEL-07-010140" selected="true" />
-    <select idref="RHEL-07-010150" selected="true" />
-    <select idref="RHEL-07-010160" selected="true" />
-    <select idref="RHEL-07-010170" selected="true" />
-    <select idref="RHEL-07-010180" selected="true" />
-    <select idref="RHEL-07-010190" selected="true" />
-    <select idref="RHEL-07-010200" selected="true" />
-    <select idref="RHEL-07-010210" selected="true" />
-    <select idref="RHEL-07-010220" selected="true" />
-    <select idref="RHEL-07-010230" selected="true" />
-    <select idref="RHEL-07-010240" selected="true" />
-    <select idref="RHEL-07-010250" selected="true" />
-    <select idref="RHEL-07-010260" selected="true" />
-    <select idref="RHEL-07-010270" selected="true" />
-    <select idref="RHEL-07-010280" selected="true" />
-    <select idref="RHEL-07-010371" selected="true" />
-    <select idref="RHEL-07-010372" selected="true" />
-    <select idref="RHEL-07-010373" selected="true" />
-    <select idref="RHEL-07-010380" selected="true" />
-    <select idref="RHEL-07-010381" selected="true" />
-    <select idref="RHEL-07-010400" selected="true" />
-    <select idref="RHEL-07-010401" selected="true" />
-    <select idref="RHEL-07-010402" selected="true" />
-    <select idref="RHEL-07-010420" selected="true" />
-    <select idref="RHEL-07-010430" selected="true" />
-    <select idref="RHEL-07-010431" selected="true" />
-    <select idref="RHEL-07-010440" selected="true" />
-    <select idref="RHEL-07-010441" selected="true" />
-    <select idref="RHEL-07-010442" selected="true" />
-    <select idref="RHEL-07-010460" selected="true" />
-    <select idref="RHEL-07-010470" selected="true" />
-    <select idref="RHEL-07-010490" selected="true" />
-    <select idref="RHEL-07-010500" selected="true" />
-    <select idref="RHEL-07-020000" selected="true" />
-    <select idref="RHEL-07-020010" selected="true" />
-    <select idref="RHEL-07-020090" selected="true" />
-    <select idref="RHEL-07-020130" selected="true" />
-    <select idref="RHEL-07-020140" selected="true" />
-    <select idref="RHEL-07-020150" selected="true" />
-    <select idref="RHEL-07-020151" selected="true" />
-    <select idref="RHEL-07-020152" selected="true" />
-    <select idref="RHEL-07-020160" selected="true" />
-    <select idref="RHEL-07-020161" selected="true" />
-    <select idref="RHEL-07-020170" selected="true" />
-    <select idref="RHEL-07-020200" selected="true" />
-    <select idref="RHEL-07-020210" selected="true" />
-    <select idref="RHEL-07-020211" selected="true" />
-    <select idref="RHEL-07-020220" selected="true" />
-    <select idref="RHEL-07-020230" selected="true" />
-    <select idref="RHEL-07-020240" selected="true" />
-    <select idref="RHEL-07-020250" selected="true" />
-    <select idref="RHEL-07-020290" selected="true" />
-    <select idref="RHEL-07-020300" selected="true" />
-    <select idref="RHEL-07-020310" selected="true" />
-    <select idref="RHEL-07-020360" selected="true" />
-    <select idref="RHEL-07-020370" selected="true" />
-    <select idref="RHEL-07-020620" selected="true" />
-    <select idref="RHEL-07-020630" selected="true" />
-    <select idref="RHEL-07-020640" selected="true" />
-    <select idref="RHEL-07-020650" selected="true" />
-    <select idref="RHEL-07-020660" selected="true" />
-    <select idref="RHEL-07-020670" selected="true" />
-    <select idref="RHEL-07-020680" selected="true" />
-    <select idref="RHEL-07-020690" selected="true" />
-    <select idref="RHEL-07-020700" selected="true" />
-    <select idref="RHEL-07-020840" selected="true" />
-    <select idref="RHEL-07-020850" selected="true" />
-    <select idref="RHEL-07-020860" selected="true" />
-    <select idref="RHEL-07-020870" selected="true" />
-    <select idref="RHEL-07-020880" selected="true" />
-    <select idref="RHEL-07-020940" selected="true" />
-    <select idref="RHEL-07-021010" selected="true" />
-    <select idref="RHEL-07-021011" selected="true" />
-    <select idref="RHEL-07-021012" selected="true" />
-    <select idref="RHEL-07-021050" selected="true" />
-    <select idref="RHEL-07-021060" selected="true" />
-    <select idref="RHEL-07-021160" selected="true" />
-    <select idref="RHEL-07-021190" selected="true" />
-    <select idref="RHEL-07-021200" selected="true" />
-    <select idref="RHEL-07-021230" selected="true" />
-    <select idref="RHEL-07-021240" selected="true" />
-    <select idref="RHEL-07-021250" selected="true" />
-    <select idref="RHEL-07-021260" selected="true" />
-    <select idref="RHEL-07-021270" selected="true" />
-    <select idref="RHEL-07-021280" selected="true" />
-    <select idref="RHEL-07-021600" selected="true" />
-    <select idref="RHEL-07-021610" selected="true" />
-    <select idref="RHEL-07-021620" selected="true" />
-    <select idref="RHEL-07-021760" selected="true" />
-    <select idref="RHEL-07-021910" selected="true" />
-    <select idref="RHEL-07-030010" selected="true" />
-    <select idref="RHEL-07-030090" selected="true" />
-    <select idref="RHEL-07-030310" selected="true" />
-    <select idref="RHEL-07-030330" selected="true" />
-    <select idref="RHEL-07-030331" selected="true" />
-    <select idref="RHEL-07-030340" selected="true" />
-    <select idref="RHEL-07-030350" selected="true" />
-    <select idref="RHEL-07-030351" selected="true" />
-    <select idref="RHEL-07-030352" selected="true" />
-    <select idref="RHEL-07-030380" selected="true" />
-    <select idref="RHEL-07-030381" selected="true" />
-    <select idref="RHEL-07-030382" selected="true" />
-    <select idref="RHEL-07-030383" selected="true" />
-    <select idref="RHEL-07-030390" selected="true" />
-    <select idref="RHEL-07-030391" selected="true" />
-    <select idref="RHEL-07-030392" selected="true" />
-    <select idref="RHEL-07-030400" selected="true" />
-    <select idref="RHEL-07-030401" selected="true" />
-    <select idref="RHEL-07-030402" selected="true" />
-    <select idref="RHEL-07-030403" selected="true" />
-    <select idref="RHEL-07-030404" selected="true" />
-    <select idref="RHEL-07-030405" selected="true" />
-    <select idref="RHEL-07-030420" selected="true" />
-    <select idref="RHEL-07-030421" selected="true" />
-    <select idref="RHEL-07-030422" selected="true" />
-    <select idref="RHEL-07-030423" selected="true" />
-    <select idref="RHEL-07-030424" selected="true" />
-    <select idref="RHEL-07-030425" selected="true" />
-    <select idref="RHEL-07-030441" selected="true" />
-    <select idref="RHEL-07-030442" selected="true" />
-    <select idref="RHEL-07-030443" selected="true" />
-    <select idref="RHEL-07-030444" selected="true" />
-    <select idref="RHEL-07-030490" selected="true" />
-    <select idref="RHEL-07-030491" selected="true" />
-    <select idref="RHEL-07-030492" selected="true" />
-    <select idref="RHEL-07-030510" selected="true" />
-    <select idref="RHEL-07-030511" selected="true" />
-    <select idref="RHEL-07-030512" selected="true" />
-    <select idref="RHEL-07-030513" selected="true" />
-    <select idref="RHEL-07-030514" selected="true" />
-    <select idref="RHEL-07-030521" selected="true" />
-    <select idref="RHEL-07-030522" selected="true" />
-    <select idref="RHEL-07-030526" selected="true" />
-    <select idref="RHEL-07-030523" selected="true" />
-    <select idref="RHEL-07-030524" selected="true" />
-    <select idref="RHEL-07-030525" selected="true" />
-    <select idref="RHEL-07-030530" selected="true" />
-    <select idref="RHEL-07-030531" selected="true" />
-    <select idref="RHEL-07-030540" selected="true" />
-    <select idref="RHEL-07-030541" selected="true" />
-    <select idref="RHEL-07-030550" selected="true" />
-    <select idref="RHEL-07-030560" selected="true" />
-    <select idref="RHEL-07-030561" selected="true" />
-    <select idref="RHEL-07-030630" selected="true" />
-    <select idref="RHEL-07-030670" selected="true" />
-    <select idref="RHEL-07-030671" selected="true" />
-    <select idref="RHEL-07-030672" selected="true" />
-    <select idref="RHEL-07-030673" selected="true" />
-    <select idref="RHEL-07-030674" selected="true" />
-    <select idref="RHEL-07-030710" selected="true" />
-    <select idref="RHEL-07-030750" selected="true" />
-    <select idref="RHEL-07-030751" selected="true" />
-    <select idref="RHEL-07-030752" selected="true" />
-    <select idref="RHEL-07-030753" selected="true" />
-    <select idref="RHEL-07-030754" selected="true" />
-    <select idref="RHEL-07-030770" selected="true" />
-    <select idref="RHEL-07-030780" selected="true" />
-    <select idref="RHEL-07-030810" selected="true" />
-    <select idref="RHEL-07-030820" selected="true" />
-    <select idref="RHEL-07-040010" selected="true" />
-    <select idref="RHEL-07-040020" selected="true" />
-    <select idref="RHEL-07-040030" selected="true" />
-    <select idref="RHEL-07-040040" selected="true" />
-    <select idref="RHEL-07-040050" selected="true" />
-    <select idref="RHEL-07-040060" selected="true" />
-    <select idref="RHEL-07-040070" selected="true" />
-    <select idref="RHEL-07-040080" selected="true" />
-    <select idref="RHEL-07-040100" selected="true" />
-    <select idref="RHEL-07-040110" selected="true" />
-    <select idref="RHEL-07-040160" selected="true" />
-    <select idref="RHEL-07-040170" selected="true" />
-    <select idref="RHEL-07-040180" selected="true" />
-    <select idref="RHEL-07-040181" selected="true" />
-    <select idref="RHEL-07-040182" selected="true" />
-    <select idref="RHEL-07-040190" selected="true" />
-    <select idref="RHEL-07-040191" selected="true" />
-    <select idref="RHEL-07-040210" selected="true" />
-    <select idref="RHEL-07-040230" selected="true" />
-    <select idref="RHEL-07-040250" selected="true" />
-    <select idref="RHEL-07-040260" selected="true" />
-    <select idref="RHEL-07-040261" selected="true" />
-    <select idref="RHEL-07-040290" selected="true" />
-    <select idref="RHEL-07-040300" selected="true" />
-    <select idref="RHEL-07-040301" selected="true" />
-    <select idref="RHEL-07-040310" selected="true" />
-    <select idref="RHEL-07-040320" selected="true" />
-    <select idref="RHEL-07-040330" selected="true" />
-    <select idref="RHEL-07-040331" selected="true" />
-    <select idref="RHEL-07-040334" selected="true" />
-    <select idref="RHEL-07-040332" selected="true" />
-    <select idref="RHEL-07-040333" selected="true" />
-    <select idref="RHEL-07-040350" selected="true" />
-    <select idref="RHEL-07-040351" selected="true" />
-    <select idref="RHEL-07-040380" selected="true" />
-    <select idref="RHEL-07-040410" selected="true" />
-    <select idref="RHEL-07-040420" selected="true" />
-    <select idref="RHEL-07-040421" selected="true" />
-    <select idref="RHEL-07-040470" selected="true" />
-    <select idref="RHEL-07-040480" selected="true" />
-    <select idref="RHEL-07-040490" selected="true" />
-    <select idref="RHEL-07-040500" selected="true" />
-    <select idref="RHEL-07-040520" selected="true" />
-    <select idref="RHEL-07-040540" selected="true" />
-    <select idref="RHEL-07-040560" selected="true" />
-    <select idref="RHEL-07-040580" selected="true" />
-    <select idref="RHEL-07-040590" selected="true" />
-    <select idref="RHEL-07-040620" selected="true" />
-    <select idref="RHEL-07-040640" selected="true" />
-    <select idref="RHEL-07-040650" selected="true" />
-    <select idref="RHEL-07-040660" selected="true" />
-    <select idref="RHEL-07-040670" selected="true" />
-    <select idref="RHEL-07-040680" selected="true" />
-    <select idref="RHEL-07-040690" selected="true" />
-    <select idref="RHEL-07-040700" selected="true" />
-    <select idref="RHEL-07-040730" selected="true" />
-    <select idref="RHEL-07-040740" selected="true" />
-    <select idref="RHEL-07-040810" selected="true" />
-    <select idref="RHEL-07-040820" selected="true" />
-    <select idref="RHEL-07-040830" selected="true" />
-    <select idref="RHEL-07-040860" selected="true" />
-  </Profile>
-  <Profile id="MAC-2_Classified">
-    <title>II - Mission Support Classified</title>
-    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
-    <select idref="RHEL-07-010010" selected="true" />
-    <select idref="RHEL-07-010020" selected="true" />
-    <select idref="RHEL-07-010030" selected="true" />
-    <select idref="RHEL-07-010031" selected="true" />
-    <select idref="RHEL-07-010040" selected="true" />
-    <select idref="RHEL-07-010060" selected="true" />
-    <select idref="RHEL-07-010070" selected="true" />
-    <select idref="RHEL-07-010074" selected="true" />
-    <select idref="RHEL-07-010071" selected="true" />
-    <select idref="RHEL-07-010072" selected="true" />
-    <select idref="RHEL-07-010073" selected="true" />
-    <select idref="RHEL-07-010090" selected="true" />
-    <select idref="RHEL-07-010100" selected="true" />
-    <select idref="RHEL-07-010110" selected="true" />
-    <select idref="RHEL-07-010120" selected="true" />
-    <select idref="RHEL-07-010130" selected="true" />
-    <select idref="RHEL-07-010140" selected="true" />
-    <select idref="RHEL-07-010150" selected="true" />
-    <select idref="RHEL-07-010160" selected="true" />
-    <select idref="RHEL-07-010170" selected="true" />
-    <select idref="RHEL-07-010180" selected="true" />
-    <select idref="RHEL-07-010190" selected="true" />
-    <select idref="RHEL-07-010200" selected="true" />
-    <select idref="RHEL-07-010210" selected="true" />
-    <select idref="RHEL-07-010220" selected="true" />
-    <select idref="RHEL-07-010230" selected="true" />
-    <select idref="RHEL-07-010240" selected="true" />
-    <select idref="RHEL-07-010250" selected="true" />
-    <select idref="RHEL-07-010260" selected="true" />
-    <select idref="RHEL-07-010270" selected="true" />
-    <select idref="RHEL-07-010280" selected="true" />
-    <select idref="RHEL-07-010371" selected="true" />
-    <select idref="RHEL-07-010372" selected="true" />
-    <select idref="RHEL-07-010373" selected="true" />
-    <select idref="RHEL-07-010380" selected="true" />
-    <select idref="RHEL-07-010381" selected="true" />
-    <select idref="RHEL-07-010400" selected="true" />
-    <select idref="RHEL-07-010401" selected="true" />
-    <select idref="RHEL-07-010402" selected="true" />
-    <select idref="RHEL-07-010420" selected="true" />
-    <select idref="RHEL-07-010430" selected="true" />
-    <select idref="RHEL-07-010431" selected="true" />
-    <select idref="RHEL-07-010440" selected="true" />
-    <select idref="RHEL-07-010441" selected="true" />
-    <select idref="RHEL-07-010442" selected="true" />
-    <select idref="RHEL-07-010460" selected="true" />
-    <select idref="RHEL-07-010470" selected="true" />
-    <select idref="RHEL-07-010490" selected="true" />
-    <select idref="RHEL-07-010500" selected="true" />
-    <select idref="RHEL-07-020000" selected="true" />
-    <select idref="RHEL-07-020010" selected="true" />
-    <select idref="RHEL-07-020090" selected="true" />
-    <select idref="RHEL-07-020130" selected="true" />
-    <select idref="RHEL-07-020140" selected="true" />
-    <select idref="RHEL-07-020150" selected="true" />
-    <select idref="RHEL-07-020151" selected="true" />
-    <select idref="RHEL-07-020152" selected="true" />
-    <select idref="RHEL-07-020160" selected="true" />
-    <select idref="RHEL-07-020161" selected="true" />
-    <select idref="RHEL-07-020170" selected="true" />
-    <select idref="RHEL-07-020200" selected="true" />
-    <select idref="RHEL-07-020210" selected="true" />
-    <select idref="RHEL-07-020211" selected="true" />
-    <select idref="RHEL-07-020220" selected="true" />
-    <select idref="RHEL-07-020230" selected="true" />
-    <select idref="RHEL-07-020240" selected="true" />
-    <select idref="RHEL-07-020250" selected="true" />
-    <select idref="RHEL-07-020290" selected="true" />
-    <select idref="RHEL-07-020300" selected="true" />
-    <select idref="RHEL-07-020310" selected="true" />
-    <select idref="RHEL-07-020360" selected="true" />
-    <select idref="RHEL-07-020370" selected="true" />
-    <select idref="RHEL-07-020620" selected="true" />
-    <select idref="RHEL-07-020630" selected="true" />
-    <select idref="RHEL-07-020640" selected="true" />
-    <select idref="RHEL-07-020650" selected="true" />
-    <select idref="RHEL-07-020660" selected="true" />
-    <select idref="RHEL-07-020670" selected="true" />
-    <select idref="RHEL-07-020680" selected="true" />
-    <select idref="RHEL-07-020690" selected="true" />
-    <select idref="RHEL-07-020700" selected="true" />
-    <select idref="RHEL-07-020840" selected="true" />
-    <select idref="RHEL-07-020850" selected="true" />
-    <select idref="RHEL-07-020860" selected="true" />
-    <select idref="RHEL-07-020870" selected="true" />
-    <select idref="RHEL-07-020880" selected="true" />
-    <select idref="RHEL-07-020940" selected="true" />
-    <select idref="RHEL-07-021010" selected="true" />
-    <select idref="RHEL-07-021011" selected="true" />
-    <select idref="RHEL-07-021012" selected="true" />
-    <select idref="RHEL-07-021050" selected="true" />
-    <select idref="RHEL-07-021060" selected="true" />
-    <select idref="RHEL-07-021160" selected="true" />
-    <select idref="RHEL-07-021190" selected="true" />
-    <select idref="RHEL-07-021200" selected="true" />
-    <select idref="RHEL-07-021230" selected="true" />
-    <select idref="RHEL-07-021240" selected="true" />
-    <select idref="RHEL-07-021250" selected="true" />
-    <select idref="RHEL-07-021260" selected="true" />
-    <select idref="RHEL-07-021270" selected="true" />
-    <select idref="RHEL-07-021280" selected="true" />
-    <select idref="RHEL-07-021600" selected="true" />
-    <select idref="RHEL-07-021610" selected="true" />
-    <select idref="RHEL-07-021620" selected="true" />
-    <select idref="RHEL-07-021760" selected="true" />
-    <select idref="RHEL-07-021910" selected="true" />
-    <select idref="RHEL-07-030010" selected="true" />
-    <select idref="RHEL-07-030090" selected="true" />
-    <select idref="RHEL-07-030310" selected="true" />
-    <select idref="RHEL-07-030330" selected="true" />
-    <select idref="RHEL-07-030331" selected="true" />
-    <select idref="RHEL-07-030340" selected="true" />
-    <select idref="RHEL-07-030350" selected="true" />
-    <select idref="RHEL-07-030351" selected="true" />
-    <select idref="RHEL-07-030352" selected="true" />
-    <select idref="RHEL-07-030380" selected="true" />
-    <select idref="RHEL-07-030381" selected="true" />
-    <select idref="RHEL-07-030382" selected="true" />
-    <select idref="RHEL-07-030383" selected="true" />
-    <select idref="RHEL-07-030390" selected="true" />
-    <select idref="RHEL-07-030391" selected="true" />
-    <select idref="RHEL-07-030392" selected="true" />
-    <select idref="RHEL-07-030400" selected="true" />
-    <select idref="RHEL-07-030401" selected="true" />
-    <select idref="RHEL-07-030402" selected="true" />
-    <select idref="RHEL-07-030403" selected="true" />
-    <select idref="RHEL-07-030404" selected="true" />
-    <select idref="RHEL-07-030405" selected="true" />
-    <select idref="RHEL-07-030420" selected="true" />
-    <select idref="RHEL-07-030421" selected="true" />
-    <select idref="RHEL-07-030422" selected="true" />
-    <select idref="RHEL-07-030423" selected="true" />
-    <select idref="RHEL-07-030424" selected="true" />
-    <select idref="RHEL-07-030425" selected="true" />
-    <select idref="RHEL-07-030441" selected="true" />
-    <select idref="RHEL-07-030442" selected="true" />
-    <select idref="RHEL-07-030443" selected="true" />
-    <select idref="RHEL-07-030444" selected="true" />
-    <select idref="RHEL-07-030490" selected="true" />
-    <select idref="RHEL-07-030491" selected="true" />
-    <select idref="RHEL-07-030492" selected="true" />
-    <select idref="RHEL-07-030510" selected="true" />
-    <select idref="RHEL-07-030511" selected="true" />
-    <select idref="RHEL-07-030512" selected="true" />
-    <select idref="RHEL-07-030513" selected="true" />
-    <select idref="RHEL-07-030514" selected="true" />
-    <select idref="RHEL-07-030521" selected="true" />
-    <select idref="RHEL-07-030522" selected="true" />
-    <select idref="RHEL-07-030526" selected="true" />
-    <select idref="RHEL-07-030523" selected="true" />
-    <select idref="RHEL-07-030524" selected="true" />
-    <select idref="RHEL-07-030525" selected="true" />
-    <select idref="RHEL-07-030530" selected="true" />
-    <select idref="RHEL-07-030531" selected="true" />
-    <select idref="RHEL-07-030540" selected="true" />
-    <select idref="RHEL-07-030541" selected="true" />
-    <select idref="RHEL-07-030550" selected="true" />
-    <select idref="RHEL-07-030560" selected="true" />
-    <select idref="RHEL-07-030561" selected="true" />
-    <select idref="RHEL-07-030630" selected="true" />
-    <select idref="RHEL-07-030670" selected="true" />
-    <select idref="RHEL-07-030671" selected="true" />
-    <select idref="RHEL-07-030672" selected="true" />
-    <select idref="RHEL-07-030673" selected="true" />
-    <select idref="RHEL-07-030674" selected="true" />
-    <select idref="RHEL-07-030710" selected="true" />
-    <select idref="RHEL-07-030750" selected="true" />
-    <select idref="RHEL-07-030751" selected="true" />
-    <select idref="RHEL-07-030752" selected="true" />
-    <select idref="RHEL-07-030753" selected="true" />
-    <select idref="RHEL-07-030754" selected="true" />
-    <select idref="RHEL-07-030770" selected="true" />
-    <select idref="RHEL-07-030780" selected="true" />
-    <select idref="RHEL-07-030810" selected="true" />
-    <select idref="RHEL-07-030820" selected="true" />
-    <select idref="RHEL-07-040010" selected="true" />
-    <select idref="RHEL-07-040020" selected="true" />
-    <select idref="RHEL-07-040030" selected="true" />
-    <select idref="RHEL-07-040040" selected="true" />
-    <select idref="RHEL-07-040050" selected="true" />
-    <select idref="RHEL-07-040060" selected="true" />
-    <select idref="RHEL-07-040070" selected="true" />
-    <select idref="RHEL-07-040080" selected="true" />
-    <select idref="RHEL-07-040100" selected="true" />
-    <select idref="RHEL-07-040110" selected="true" />
-    <select idref="RHEL-07-040160" selected="true" />
-    <select idref="RHEL-07-040170" selected="true" />
-    <select idref="RHEL-07-040180" selected="true" />
-    <select idref="RHEL-07-040181" selected="true" />
-    <select idref="RHEL-07-040182" selected="true" />
-    <select idref="RHEL-07-040190" selected="true" />
-    <select idref="RHEL-07-040191" selected="true" />
-    <select idref="RHEL-07-040210" selected="true" />
-    <select idref="RHEL-07-040230" selected="true" />
-    <select idref="RHEL-07-040250" selected="true" />
-    <select idref="RHEL-07-040260" selected="true" />
-    <select idref="RHEL-07-040261" selected="true" />
-    <select idref="RHEL-07-040290" selected="true" />
-    <select idref="RHEL-07-040300" selected="true" />
-    <select idref="RHEL-07-040301" selected="true" />
-    <select idref="RHEL-07-040310" selected="true" />
-    <select idref="RHEL-07-040320" selected="true" />
-    <select idref="RHEL-07-040330" selected="true" />
-    <select idref="RHEL-07-040331" selected="true" />
-    <select idref="RHEL-07-040334" selected="true" />
-    <select idref="RHEL-07-040332" selected="true" />
-    <select idref="RHEL-07-040333" selected="true" />
-    <select idref="RHEL-07-040350" selected="true" />
-    <select idref="RHEL-07-040351" selected="true" />
-    <select idref="RHEL-07-040380" selected="true" />
-    <select idref="RHEL-07-040410" selected="true" />
-    <select idref="RHEL-07-040420" selected="true" />
-    <select idref="RHEL-07-040421" selected="true" />
-    <select idref="RHEL-07-040470" selected="true" />
-    <select idref="RHEL-07-040480" selected="true" />
-    <select idref="RHEL-07-040490" selected="true" />
-    <select idref="RHEL-07-040500" selected="true" />
-    <select idref="RHEL-07-040520" selected="true" />
-    <select idref="RHEL-07-040540" selected="true" />
-    <select idref="RHEL-07-040560" selected="true" />
-    <select idref="RHEL-07-040580" selected="true" />
-    <select idref="RHEL-07-040590" selected="true" />
-    <select idref="RHEL-07-040620" selected="true" />
-    <select idref="RHEL-07-040640" selected="true" />
-    <select idref="RHEL-07-040650" selected="true" />
-    <select idref="RHEL-07-040660" selected="true" />
-    <select idref="RHEL-07-040670" selected="true" />
-    <select idref="RHEL-07-040680" selected="true" />
-    <select idref="RHEL-07-040690" selected="true" />
-    <select idref="RHEL-07-040700" selected="true" />
-    <select idref="RHEL-07-040730" selected="true" />
-    <select idref="RHEL-07-040740" selected="true" />
-    <select idref="RHEL-07-040810" selected="true" />
-    <select idref="RHEL-07-040820" selected="true" />
-    <select idref="RHEL-07-040830" selected="true" />
-    <select idref="RHEL-07-040860" selected="true" />
-  </Profile>
-  <Profile id="MAC-3_Public">
-    <title>III - Administrative Public</title>
-    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
-    <select idref="RHEL-07-010010" selected="true" />
-    <select idref="RHEL-07-010020" selected="true" />
-    <select idref="RHEL-07-010030" selected="true" />
-    <select idref="RHEL-07-010031" selected="true" />
-    <select idref="RHEL-07-010040" selected="true" />
-    <select idref="RHEL-07-010060" selected="true" />
-    <select idref="RHEL-07-010070" selected="true" />
-    <select idref="RHEL-07-010074" selected="true" />
-    <select idref="RHEL-07-010071" selected="true" />
-    <select idref="RHEL-07-010072" selected="true" />
-    <select idref="RHEL-07-010073" selected="true" />
-    <select idref="RHEL-07-010090" selected="true" />
-    <select idref="RHEL-07-010100" selected="true" />
-    <select idref="RHEL-07-010110" selected="true" />
-    <select idref="RHEL-07-010120" selected="true" />
-    <select idref="RHEL-07-010130" selected="true" />
-    <select idref="RHEL-07-010140" selected="true" />
-    <select idref="RHEL-07-010150" selected="true" />
-    <select idref="RHEL-07-010160" selected="true" />
-    <select idref="RHEL-07-010170" selected="true" />
-    <select idref="RHEL-07-010180" selected="true" />
-    <select idref="RHEL-07-010190" selected="true" />
-    <select idref="RHEL-07-010200" selected="true" />
-    <select idref="RHEL-07-010210" selected="true" />
-    <select idref="RHEL-07-010220" selected="true" />
-    <select idref="RHEL-07-010230" selected="true" />
-    <select idref="RHEL-07-010240" selected="true" />
-    <select idref="RHEL-07-010250" selected="true" />
-    <select idref="RHEL-07-010260" selected="true" />
-    <select idref="RHEL-07-010270" selected="true" />
-    <select idref="RHEL-07-010280" selected="true" />
-    <select idref="RHEL-07-010371" selected="true" />
-    <select idref="RHEL-07-010372" selected="true" />
-    <select idref="RHEL-07-010373" selected="true" />
-    <select idref="RHEL-07-010380" selected="true" />
-    <select idref="RHEL-07-010381" selected="true" />
-    <select idref="RHEL-07-010400" selected="true" />
-    <select idref="RHEL-07-010401" selected="true" />
-    <select idref="RHEL-07-010402" selected="true" />
-    <select idref="RHEL-07-010420" selected="true" />
-    <select idref="RHEL-07-010430" selected="true" />
-    <select idref="RHEL-07-010431" selected="true" />
-    <select idref="RHEL-07-010440" selected="true" />
-    <select idref="RHEL-07-010441" selected="true" />
-    <select idref="RHEL-07-010442" selected="true" />
-    <select idref="RHEL-07-010460" selected="true" />
-    <select idref="RHEL-07-010470" selected="true" />
-    <select idref="RHEL-07-010490" selected="true" />
-    <select idref="RHEL-07-010500" selected="true" />
-    <select idref="RHEL-07-020000" selected="true" />
-    <select idref="RHEL-07-020010" selected="true" />
-    <select idref="RHEL-07-020090" selected="true" />
-    <select idref="RHEL-07-020130" selected="true" />
-    <select idref="RHEL-07-020140" selected="true" />
-    <select idref="RHEL-07-020150" selected="true" />
-    <select idref="RHEL-07-020151" selected="true" />
-    <select idref="RHEL-07-020152" selected="true" />
-    <select idref="RHEL-07-020160" selected="true" />
-    <select idref="RHEL-07-020161" selected="true" />
-    <select idref="RHEL-07-020170" selected="true" />
-    <select idref="RHEL-07-020200" selected="true" />
-    <select idref="RHEL-07-020210" selected="true" />
-    <select idref="RHEL-07-020211" selected="true" />
-    <select idref="RHEL-07-020220" selected="true" />
-    <select idref="RHEL-07-020230" selected="true" />
-    <select idref="RHEL-07-020240" selected="true" />
-    <select idref="RHEL-07-020250" selected="true" />
-    <select idref="RHEL-07-020290" selected="true" />
-    <select idref="RHEL-07-020300" selected="true" />
-    <select idref="RHEL-07-020310" selected="true" />
-    <select idref="RHEL-07-020360" selected="true" />
-    <select idref="RHEL-07-020370" selected="true" />
-    <select idref="RHEL-07-020620" selected="true" />
-    <select idref="RHEL-07-020630" selected="true" />
-    <select idref="RHEL-07-020640" selected="true" />
-    <select idref="RHEL-07-020650" selected="true" />
-    <select idref="RHEL-07-020660" selected="true" />
-    <select idref="RHEL-07-020670" selected="true" />
-    <select idref="RHEL-07-020680" selected="true" />
-    <select idref="RHEL-07-020690" selected="true" />
-    <select idref="RHEL-07-020700" selected="true" />
-    <select idref="RHEL-07-020840" selected="true" />
-    <select idref="RHEL-07-020850" selected="true" />
-    <select idref="RHEL-07-020860" selected="true" />
-    <select idref="RHEL-07-020870" selected="true" />
-    <select idref="RHEL-07-020880" selected="true" />
-    <select idref="RHEL-07-020940" selected="true" />
-    <select idref="RHEL-07-021010" selected="true" />
-    <select idref="RHEL-07-021011" selected="true" />
-    <select idref="RHEL-07-021012" selected="true" />
-    <select idref="RHEL-07-021050" selected="true" />
-    <select idref="RHEL-07-021060" selected="true" />
-    <select idref="RHEL-07-021160" selected="true" />
-    <select idref="RHEL-07-021190" selected="true" />
-    <select idref="RHEL-07-021200" selected="true" />
-    <select idref="RHEL-07-021230" selected="true" />
-    <select idref="RHEL-07-021240" selected="true" />
-    <select idref="RHEL-07-021250" selected="true" />
-    <select idref="RHEL-07-021260" selected="true" />
-    <select idref="RHEL-07-021270" selected="true" />
-    <select idref="RHEL-07-021280" selected="true" />
-    <select idref="RHEL-07-021600" selected="true" />
-    <select idref="RHEL-07-021610" selected="true" />
-    <select idref="RHEL-07-021620" selected="true" />
-    <select idref="RHEL-07-021760" selected="true" />
-    <select idref="RHEL-07-021910" selected="true" />
-    <select idref="RHEL-07-030010" selected="true" />
-    <select idref="RHEL-07-030090" selected="true" />
-    <select idref="RHEL-07-030310" selected="true" />
-    <select idref="RHEL-07-030330" selected="true" />
-    <select idref="RHEL-07-030331" selected="true" />
-    <select idref="RHEL-07-030340" selected="true" />
-    <select idref="RHEL-07-030350" selected="true" />
-    <select idref="RHEL-07-030351" selected="true" />
-    <select idref="RHEL-07-030352" selected="true" />
-    <select idref="RHEL-07-030380" selected="true" />
-    <select idref="RHEL-07-030381" selected="true" />
-    <select idref="RHEL-07-030382" selected="true" />
-    <select idref="RHEL-07-030383" selected="true" />
-    <select idref="RHEL-07-030390" selected="true" />
-    <select idref="RHEL-07-030391" selected="true" />
-    <select idref="RHEL-07-030392" selected="true" />
-    <select idref="RHEL-07-030400" selected="true" />
-    <select idref="RHEL-07-030401" selected="true" />
-    <select idref="RHEL-07-030402" selected="true" />
-    <select idref="RHEL-07-030403" selected="true" />
-    <select idref="RHEL-07-030404" selected="true" />
-    <select idref="RHEL-07-030405" selected="true" />
-    <select idref="RHEL-07-030420" selected="true" />
-    <select idref="RHEL-07-030421" selected="true" />
-    <select idref="RHEL-07-030422" selected="true" />
-    <select idref="RHEL-07-030423" selected="true" />
-    <select idref="RHEL-07-030424" selected="true" />
-    <select idref="RHEL-07-030425" selected="true" />
-    <select idref="RHEL-07-030441" selected="true" />
-    <select idref="RHEL-07-030442" selected="true" />
-    <select idref="RHEL-07-030443" selected="true" />
-    <select idref="RHEL-07-030444" selected="true" />
-    <select idref="RHEL-07-030490" selected="true" />
-    <select idref="RHEL-07-030491" selected="true" />
-    <select idref="RHEL-07-030492" selected="true" />
-    <select idref="RHEL-07-030510" selected="true" />
-    <select idref="RHEL-07-030511" selected="true" />
-    <select idref="RHEL-07-030512" selected="true" />
-    <select idref="RHEL-07-030513" selected="true" />
-    <select idref="RHEL-07-030514" selected="true" />
-    <select idref="RHEL-07-030521" selected="true" />
-    <select idref="RHEL-07-030522" selected="true" />
-    <select idref="RHEL-07-030526" selected="true" />
-    <select idref="RHEL-07-030523" selected="true" />
-    <select idref="RHEL-07-030524" selected="true" />
-    <select idref="RHEL-07-030525" selected="true" />
-    <select idref="RHEL-07-030530" selected="true" />
-    <select idref="RHEL-07-030531" selected="true" />
-    <select idref="RHEL-07-030540" selected="true" />
-    <select idref="RHEL-07-030541" selected="true" />
-    <select idref="RHEL-07-030550" selected="true" />
-    <select idref="RHEL-07-030560" selected="true" />
-    <select idref="RHEL-07-030561" selected="true" />
-    <select idref="RHEL-07-030630" selected="true" />
-    <select idref="RHEL-07-030670" selected="true" />
-    <select idref="RHEL-07-030671" selected="true" />
-    <select idref="RHEL-07-030672" selected="true" />
-    <select idref="RHEL-07-030673" selected="true" />
-    <select idref="RHEL-07-030674" selected="true" />
-    <select idref="RHEL-07-030710" selected="true" />
-    <select idref="RHEL-07-030750" selected="true" />
-    <select idref="RHEL-07-030751" selected="true" />
-    <select idref="RHEL-07-030752" selected="true" />
-    <select idref="RHEL-07-030753" selected="true" />
-    <select idref="RHEL-07-030754" selected="true" />
-    <select idref="RHEL-07-030770" selected="true" />
-    <select idref="RHEL-07-030780" selected="true" />
-    <select idref="RHEL-07-030810" selected="true" />
-    <select idref="RHEL-07-030820" selected="true" />
-    <select idref="RHEL-07-040010" selected="true" />
-    <select idref="RHEL-07-040020" selected="true" />
-    <select idref="RHEL-07-040030" selected="true" />
-    <select idref="RHEL-07-040040" selected="true" />
-    <select idref="RHEL-07-040050" selected="true" />
-    <select idref="RHEL-07-040060" selected="true" />
-    <select idref="RHEL-07-040070" selected="true" />
-    <select idref="RHEL-07-040080" selected="true" />
-    <select idref="RHEL-07-040100" selected="true" />
-    <select idref="RHEL-07-040110" selected="true" />
-    <select idref="RHEL-07-040160" selected="true" />
-    <select idref="RHEL-07-040170" selected="true" />
-    <select idref="RHEL-07-040180" selected="true" />
-    <select idref="RHEL-07-040181" selected="true" />
-    <select idref="RHEL-07-040182" selected="true" />
-    <select idref="RHEL-07-040190" selected="true" />
-    <select idref="RHEL-07-040191" selected="true" />
-    <select idref="RHEL-07-040210" selected="true" />
-    <select idref="RHEL-07-040230" selected="true" />
-    <select idref="RHEL-07-040250" selected="true" />
-    <select idref="RHEL-07-040260" selected="true" />
-    <select idref="RHEL-07-040261" selected="true" />
-    <select idref="RHEL-07-040290" selected="true" />
-    <select idref="RHEL-07-040300" selected="true" />
-    <select idref="RHEL-07-040301" selected="true" />
-    <select idref="RHEL-07-040310" selected="true" />
-    <select idref="RHEL-07-040320" selected="true" />
-    <select idref="RHEL-07-040330" selected="true" />
-    <select idref="RHEL-07-040331" selected="true" />
-    <select idref="RHEL-07-040334" selected="true" />
-    <select idref="RHEL-07-040332" selected="true" />
-    <select idref="RHEL-07-040333" selected="true" />
-    <select idref="RHEL-07-040350" selected="true" />
-    <select idref="RHEL-07-040351" selected="true" />
-    <select idref="RHEL-07-040380" selected="true" />
-    <select idref="RHEL-07-040410" selected="true" />
-    <select idref="RHEL-07-040420" selected="true" />
-    <select idref="RHEL-07-040421" selected="true" />
-    <select idref="RHEL-07-040470" selected="true" />
-    <select idref="RHEL-07-040480" selected="true" />
-    <select idref="RHEL-07-040490" selected="true" />
-    <select idref="RHEL-07-040500" selected="true" />
-    <select idref="RHEL-07-040520" selected="true" />
-    <select idref="RHEL-07-040540" selected="true" />
-    <select idref="RHEL-07-040560" selected="true" />
-    <select idref="RHEL-07-040580" selected="true" />
-    <select idref="RHEL-07-040590" selected="true" />
-    <select idref="RHEL-07-040620" selected="true" />
-    <select idref="RHEL-07-040640" selected="true" />
-    <select idref="RHEL-07-040650" selected="true" />
-    <select idref="RHEL-07-040660" selected="true" />
-    <select idref="RHEL-07-040670" selected="true" />
-    <select idref="RHEL-07-040680" selected="true" />
-    <select idref="RHEL-07-040690" selected="true" />
-    <select idref="RHEL-07-040700" selected="true" />
-    <select idref="RHEL-07-040730" selected="true" />
-    <select idref="RHEL-07-040740" selected="true" />
-    <select idref="RHEL-07-040810" selected="true" />
-    <select idref="RHEL-07-040820" selected="true" />
-    <select idref="RHEL-07-040830" selected="true" />
-    <select idref="RHEL-07-040860" selected="true" />
-  </Profile>
-  <Profile id="MAC-3_Sensitive">
-    <title>III - Administrative Sensitive</title>
-    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
-    <select idref="RHEL-07-010010" selected="true" />
-    <select idref="RHEL-07-010020" selected="true" />
-    <select idref="RHEL-07-010030" selected="true" />
-    <select idref="RHEL-07-010031" selected="true" />
-    <select idref="RHEL-07-010040" selected="true" />
-    <select idref="RHEL-07-010060" selected="true" />
-    <select idref="RHEL-07-010070" selected="true" />
-    <select idref="RHEL-07-010074" selected="true" />
-    <select idref="RHEL-07-010071" selected="true" />
-    <select idref="RHEL-07-010072" selected="true" />
-    <select idref="RHEL-07-010073" selected="true" />
-    <select idref="RHEL-07-010090" selected="true" />
-    <select idref="RHEL-07-010100" selected="true" />
-    <select idref="RHEL-07-010110" selected="true" />
-    <select idref="RHEL-07-010120" selected="true" />
-    <select idref="RHEL-07-010130" selected="true" />
-    <select idref="RHEL-07-010140" selected="true" />
-    <select idref="RHEL-07-010150" selected="true" />
-    <select idref="RHEL-07-010160" selected="true" />
-    <select idref="RHEL-07-010170" selected="true" />
-    <select idref="RHEL-07-010180" selected="true" />
-    <select idref="RHEL-07-010190" selected="true" />
-    <select idref="RHEL-07-010200" selected="true" />
-    <select idref="RHEL-07-010210" selected="true" />
-    <select idref="RHEL-07-010220" selected="true" />
-    <select idref="RHEL-07-010230" selected="true" />
-    <select idref="RHEL-07-010240" selected="true" />
-    <select idref="RHEL-07-010250" selected="true" />
-    <select idref="RHEL-07-010260" selected="true" />
-    <select idref="RHEL-07-010270" selected="true" />
-    <select idref="RHEL-07-010280" selected="true" />
-    <select idref="RHEL-07-010371" selected="true" />
-    <select idref="RHEL-07-010372" selected="true" />
-    <select idref="RHEL-07-010373" selected="true" />
-    <select idref="RHEL-07-010380" selected="true" />
-    <select idref="RHEL-07-010381" selected="true" />
-    <select idref="RHEL-07-010400" selected="true" />
-    <select idref="RHEL-07-010401" selected="true" />
-    <select idref="RHEL-07-010402" selected="true" />
-    <select idref="RHEL-07-010420" selected="true" />
-    <select idref="RHEL-07-010430" selected="true" />
-    <select idref="RHEL-07-010431" selected="true" />
-    <select idref="RHEL-07-010440" selected="true" />
-    <select idref="RHEL-07-010441" selected="true" />
-    <select idref="RHEL-07-010442" selected="true" />
-    <select idref="RHEL-07-010460" selected="true" />
-    <select idref="RHEL-07-010470" selected="true" />
-    <select idref="RHEL-07-010490" selected="true" />
-    <select idref="RHEL-07-010500" selected="true" />
-    <select idref="RHEL-07-020000" selected="true" />
-    <select idref="RHEL-07-020010" selected="true" />
-    <select idref="RHEL-07-020090" selected="true" />
-    <select idref="RHEL-07-020130" selected="true" />
-    <select idref="RHEL-07-020140" selected="true" />
-    <select idref="RHEL-07-020150" selected="true" />
-    <select idref="RHEL-07-020151" selected="true" />
-    <select idref="RHEL-07-020152" selected="true" />
-    <select idref="RHEL-07-020160" selected="true" />
-    <select idref="RHEL-07-020161" selected="true" />
-    <select idref="RHEL-07-020170" selected="true" />
-    <select idref="RHEL-07-020200" selected="true" />
-    <select idref="RHEL-07-020210" selected="true" />
-    <select idref="RHEL-07-020211" selected="true" />
-    <select idref="RHEL-07-020220" selected="true" />
-    <select idref="RHEL-07-020230" selected="true" />
-    <select idref="RHEL-07-020240" selected="true" />
-    <select idref="RHEL-07-020250" selected="true" />
-    <select idref="RHEL-07-020290" selected="true" />
-    <select idref="RHEL-07-020300" selected="true" />
-    <select idref="RHEL-07-020310" selected="true" />
-    <select idref="RHEL-07-020360" selected="true" />
-    <select idref="RHEL-07-020370" selected="true" />
-    <select idref="RHEL-07-020620" selected="true" />
-    <select idref="RHEL-07-020630" selected="true" />
-    <select idref="RHEL-07-020640" selected="true" />
-    <select idref="RHEL-07-020650" selected="true" />
-    <select idref="RHEL-07-020660" selected="true" />
-    <select idref="RHEL-07-020670" selected="true" />
-    <select idref="RHEL-07-020680" selected="true" />
-    <select idref="RHEL-07-020690" selected="true" />
-    <select idref="RHEL-07-020700" selected="true" />
-    <select idref="RHEL-07-020840" selected="true" />
-    <select idref="RHEL-07-020850" selected="true" />
-    <select idref="RHEL-07-020860" selected="true" />
-    <select idref="RHEL-07-020870" selected="true" />
-    <select idref="RHEL-07-020880" selected="true" />
-    <select idref="RHEL-07-020940" selected="true" />
-    <select idref="RHEL-07-021010" selected="true" />
-    <select idref="RHEL-07-021011" selected="true" />
-    <select idref="RHEL-07-021012" selected="true" />
-    <select idref="RHEL-07-021050" selected="true" />
-    <select idref="RHEL-07-021060" selected="true" />
-    <select idref="RHEL-07-021160" selected="true" />
-    <select idref="RHEL-07-021190" selected="true" />
-    <select idref="RHEL-07-021200" selected="true" />
-    <select idref="RHEL-07-021230" selected="true" />
-    <select idref="RHEL-07-021240" selected="true" />
-    <select idref="RHEL-07-021250" selected="true" />
-    <select idref="RHEL-07-021260" selected="true" />
-    <select idref="RHEL-07-021270" selected="true" />
-    <select idref="RHEL-07-021280" selected="true" />
-    <select idref="RHEL-07-021600" selected="true" />
-    <select idref="RHEL-07-021610" selected="true" />
-    <select idref="RHEL-07-021620" selected="true" />
-    <select idref="RHEL-07-021760" selected="true" />
-    <select idref="RHEL-07-021910" selected="true" />
-    <select idref="RHEL-07-030010" selected="true" />
-    <select idref="RHEL-07-030090" selected="true" />
-    <select idref="RHEL-07-030310" selected="true" />
-    <select idref="RHEL-07-030330" selected="true" />
-    <select idref="RHEL-07-030331" selected="true" />
-    <select idref="RHEL-07-030340" selected="true" />
-    <select idref="RHEL-07-030350" selected="true" />
-    <select idref="RHEL-07-030351" selected="true" />
-    <select idref="RHEL-07-030352" selected="true" />
-    <select idref="RHEL-07-030380" selected="true" />
-    <select idref="RHEL-07-030381" selected="true" />
-    <select idref="RHEL-07-030382" selected="true" />
-    <select idref="RHEL-07-030383" selected="true" />
-    <select idref="RHEL-07-030390" selected="true" />
-    <select idref="RHEL-07-030391" selected="true" />
-    <select idref="RHEL-07-030392" selected="true" />
-    <select idref="RHEL-07-030400" selected="true" />
-    <select idref="RHEL-07-030401" selected="true" />
-    <select idref="RHEL-07-030402" selected="true" />
-    <select idref="RHEL-07-030403" selected="true" />
-    <select idref="RHEL-07-030404" selected="true" />
-    <select idref="RHEL-07-030405" selected="true" />
-    <select idref="RHEL-07-030420" selected="true" />
-    <select idref="RHEL-07-030421" selected="true" />
-    <select idref="RHEL-07-030422" selected="true" />
-    <select idref="RHEL-07-030423" selected="true" />
-    <select idref="RHEL-07-030424" selected="true" />
-    <select idref="RHEL-07-030425" selected="true" />
-    <select idref="RHEL-07-030441" selected="true" />
-    <select idref="RHEL-07-030442" selected="true" />
-    <select idref="RHEL-07-030443" selected="true" />
-    <select idref="RHEL-07-030444" selected="true" />
-    <select idref="RHEL-07-030490" selected="true" />
-    <select idref="RHEL-07-030491" selected="true" />
-    <select idref="RHEL-07-030492" selected="true" />
-    <select idref="RHEL-07-030510" selected="true" />
-    <select idref="RHEL-07-030511" selected="true" />
-    <select idref="RHEL-07-030512" selected="true" />
-    <select idref="RHEL-07-030513" selected="true" />
-    <select idref="RHEL-07-030514" selected="true" />
-    <select idref="RHEL-07-030521" selected="true" />
-    <select idref="RHEL-07-030522" selected="true" />
-    <select idref="RHEL-07-030526" selected="true" />
-    <select idref="RHEL-07-030523" selected="true" />
-    <select idref="RHEL-07-030524" selected="true" />
-    <select idref="RHEL-07-030525" selected="true" />
-    <select idref="RHEL-07-030530" selected="true" />
-    <select idref="RHEL-07-030531" selected="true" />
-    <select idref="RHEL-07-030540" selected="true" />
-    <select idref="RHEL-07-030541" selected="true" />
-    <select idref="RHEL-07-030550" selected="true" />
-    <select idref="RHEL-07-030560" selected="true" />
-    <select idref="RHEL-07-030561" selected="true" />
-    <select idref="RHEL-07-030630" selected="true" />
-    <select idref="RHEL-07-030670" selected="true" />
-    <select idref="RHEL-07-030671" selected="true" />
-    <select idref="RHEL-07-030672" selected="true" />
-    <select idref="RHEL-07-030673" selected="true" />
-    <select idref="RHEL-07-030674" selected="true" />
-    <select idref="RHEL-07-030710" selected="true" />
-    <select idref="RHEL-07-030750" selected="true" />
-    <select idref="RHEL-07-030751" selected="true" />
-    <select idref="RHEL-07-030752" selected="true" />
-    <select idref="RHEL-07-030753" selected="true" />
-    <select idref="RHEL-07-030754" selected="true" />
-    <select idref="RHEL-07-030770" selected="true" />
-    <select idref="RHEL-07-030780" selected="true" />
-    <select idref="RHEL-07-030810" selected="true" />
-    <select idref="RHEL-07-030820" selected="true" />
-    <select idref="RHEL-07-040010" selected="true" />
-    <select idref="RHEL-07-040020" selected="true" />
-    <select idref="RHEL-07-040030" selected="true" />
-    <select idref="RHEL-07-040040" selected="true" />
-    <select idref="RHEL-07-040050" selected="true" />
-    <select idref="RHEL-07-040060" selected="true" />
-    <select idref="RHEL-07-040070" selected="true" />
-    <select idref="RHEL-07-040080" selected="true" />
-    <select idref="RHEL-07-040100" selected="true" />
-    <select idref="RHEL-07-040110" selected="true" />
-    <select idref="RHEL-07-040160" selected="true" />
-    <select idref="RHEL-07-040170" selected="true" />
-    <select idref="RHEL-07-040180" selected="true" />
-    <select idref="RHEL-07-040181" selected="true" />
-    <select idref="RHEL-07-040182" selected="true" />
-    <select idref="RHEL-07-040190" selected="true" />
-    <select idref="RHEL-07-040191" selected="true" />
-    <select idref="RHEL-07-040210" selected="true" />
-    <select idref="RHEL-07-040230" selected="true" />
-    <select idref="RHEL-07-040250" selected="true" />
-    <select idref="RHEL-07-040260" selected="true" />
-    <select idref="RHEL-07-040261" selected="true" />
-    <select idref="RHEL-07-040290" selected="true" />
-    <select idref="RHEL-07-040300" selected="true" />
-    <select idref="RHEL-07-040301" selected="true" />
-    <select idref="RHEL-07-040310" selected="true" />
-    <select idref="RHEL-07-040320" selected="true" />
-    <select idref="RHEL-07-040330" selected="true" />
-    <select idref="RHEL-07-040331" selected="true" />
-    <select idref="RHEL-07-040334" selected="true" />
-    <select idref="RHEL-07-040332" selected="true" />
-    <select idref="RHEL-07-040333" selected="true" />
-    <select idref="RHEL-07-040350" selected="true" />
-    <select idref="RHEL-07-040351" selected="true" />
-    <select idref="RHEL-07-040380" selected="true" />
-    <select idref="RHEL-07-040410" selected="true" />
-    <select idref="RHEL-07-040420" selected="true" />
-    <select idref="RHEL-07-040421" selected="true" />
-    <select idref="RHEL-07-040470" selected="true" />
-    <select idref="RHEL-07-040480" selected="true" />
-    <select idref="RHEL-07-040490" selected="true" />
-    <select idref="RHEL-07-040500" selected="true" />
-    <select idref="RHEL-07-040520" selected="true" />
-    <select idref="RHEL-07-040540" selected="true" />
-    <select idref="RHEL-07-040560" selected="true" />
-    <select idref="RHEL-07-040580" selected="true" />
-    <select idref="RHEL-07-040590" selected="true" />
-    <select idref="RHEL-07-040620" selected="true" />
-    <select idref="RHEL-07-040640" selected="true" />
-    <select idref="RHEL-07-040650" selected="true" />
-    <select idref="RHEL-07-040660" selected="true" />
-    <select idref="RHEL-07-040670" selected="true" />
-    <select idref="RHEL-07-040680" selected="true" />
-    <select idref="RHEL-07-040690" selected="true" />
-    <select idref="RHEL-07-040700" selected="true" />
-    <select idref="RHEL-07-040730" selected="true" />
-    <select idref="RHEL-07-040740" selected="true" />
-    <select idref="RHEL-07-040810" selected="true" />
-    <select idref="RHEL-07-040820" selected="true" />
-    <select idref="RHEL-07-040830" selected="true" />
-    <select idref="RHEL-07-040860" selected="true" />
-  </Profile>
-  <Profile id="MAC-3_Classified">
-    <title>III - Administrative Classified</title>
-    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
-    <select idref="RHEL-07-010010" selected="true" />
-    <select idref="RHEL-07-010020" selected="true" />
-    <select idref="RHEL-07-010030" selected="true" />
-    <select idref="RHEL-07-010031" selected="true" />
-    <select idref="RHEL-07-010040" selected="true" />
-    <select idref="RHEL-07-010060" selected="true" />
-    <select idref="RHEL-07-010070" selected="true" />
-    <select idref="RHEL-07-010074" selected="true" />
-    <select idref="RHEL-07-010071" selected="true" />
-    <select idref="RHEL-07-010072" selected="true" />
-    <select idref="RHEL-07-010073" selected="true" />
-    <select idref="RHEL-07-010090" selected="true" />
-    <select idref="RHEL-07-010100" selected="true" />
-    <select idref="RHEL-07-010110" selected="true" />
-    <select idref="RHEL-07-010120" selected="true" />
-    <select idref="RHEL-07-010130" selected="true" />
-    <select idref="RHEL-07-010140" selected="true" />
-    <select idref="RHEL-07-010150" selected="true" />
-    <select idref="RHEL-07-010160" selected="true" />
-    <select idref="RHEL-07-010170" selected="true" />
-    <select idref="RHEL-07-010180" selected="true" />
-    <select idref="RHEL-07-010190" selected="true" />
-    <select idref="RHEL-07-010200" selected="true" />
-    <select idref="RHEL-07-010210" selected="true" />
-    <select idref="RHEL-07-010220" selected="true" />
-    <select idref="RHEL-07-010230" selected="true" />
-    <select idref="RHEL-07-010240" selected="true" />
-    <select idref="RHEL-07-010250" selected="true" />
-    <select idref="RHEL-07-010260" selected="true" />
-    <select idref="RHEL-07-010270" selected="true" />
-    <select idref="RHEL-07-010280" selected="true" />
-    <select idref="RHEL-07-010371" selected="true" />
-    <select idref="RHEL-07-010372" selected="true" />
-    <select idref="RHEL-07-010373" selected="true" />
-    <select idref="RHEL-07-010380" selected="true" />
-    <select idref="RHEL-07-010381" selected="true" />
-    <select idref="RHEL-07-010400" selected="true" />
-    <select idref="RHEL-07-010401" selected="true" />
-    <select idref="RHEL-07-010402" selected="true" />
-    <select idref="RHEL-07-010420" selected="true" />
-    <select idref="RHEL-07-010430" selected="true" />
-    <select idref="RHEL-07-010431" selected="true" />
-    <select idref="RHEL-07-010440" selected="true" />
-    <select idref="RHEL-07-010441" selected="true" />
-    <select idref="RHEL-07-010442" selected="true" />
-    <select idref="RHEL-07-010460" selected="true" />
-    <select idref="RHEL-07-010470" selected="true" />
-    <select idref="RHEL-07-010490" selected="true" />
-    <select idref="RHEL-07-010500" selected="true" />
-    <select idref="RHEL-07-020000" selected="true" />
-    <select idref="RHEL-07-020010" selected="true" />
-    <select idref="RHEL-07-020090" selected="true" />
-    <select idref="RHEL-07-020130" selected="true" />
-    <select idref="RHEL-07-020140" selected="true" />
-    <select idref="RHEL-07-020150" selected="true" />
-    <select idref="RHEL-07-020151" selected="true" />
-    <select idref="RHEL-07-020152" selected="true" />
-    <select idref="RHEL-07-020160" selected="true" />
-    <select idref="RHEL-07-020161" selected="true" />
-    <select idref="RHEL-07-020170" selected="true" />
-    <select idref="RHEL-07-020200" selected="true" />
-    <select idref="RHEL-07-020210" selected="true" />
-    <select idref="RHEL-07-020211" selected="true" />
-    <select idref="RHEL-07-020220" selected="true" />
-    <select idref="RHEL-07-020230" selected="true" />
-    <select idref="RHEL-07-020240" selected="true" />
-    <select idref="RHEL-07-020250" selected="true" />
-    <select idref="RHEL-07-020290" selected="true" />
-    <select idref="RHEL-07-020300" selected="true" />
-    <select idref="RHEL-07-020310" selected="true" />
-    <select idref="RHEL-07-020360" selected="true" />
-    <select idref="RHEL-07-020370" selected="true" />
-    <select idref="RHEL-07-020620" selected="true" />
-    <select idref="RHEL-07-020630" selected="true" />
-    <select idref="RHEL-07-020640" selected="true" />
-    <select idref="RHEL-07-020650" selected="true" />
-    <select idref="RHEL-07-020660" selected="true" />
-    <select idref="RHEL-07-020670" selected="true" />
-    <select idref="RHEL-07-020680" selected="true" />
-    <select idref="RHEL-07-020690" selected="true" />
-    <select idref="RHEL-07-020700" selected="true" />
-    <select idref="RHEL-07-020840" selected="true" />
-    <select idref="RHEL-07-020850" selected="true" />
-    <select idref="RHEL-07-020860" selected="true" />
-    <select idref="RHEL-07-020870" selected="true" />
-    <select idref="RHEL-07-020880" selected="true" />
-    <select idref="RHEL-07-020940" selected="true" />
-    <select idref="RHEL-07-021010" selected="true" />
-    <select idref="RHEL-07-021011" selected="true" />
-    <select idref="RHEL-07-021012" selected="true" />
-    <select idref="RHEL-07-021050" selected="true" />
-    <select idref="RHEL-07-021060" selected="true" />
-    <select idref="RHEL-07-021160" selected="true" />
-    <select idref="RHEL-07-021190" selected="true" />
-    <select idref="RHEL-07-021200" selected="true" />
-    <select idref="RHEL-07-021230" selected="true" />
-    <select idref="RHEL-07-021240" selected="true" />
-    <select idref="RHEL-07-021250" selected="true" />
-    <select idref="RHEL-07-021260" selected="true" />
-    <select idref="RHEL-07-021270" selected="true" />
-    <select idref="RHEL-07-021280" selected="true" />
-    <select idref="RHEL-07-021600" selected="true" />
-    <select idref="RHEL-07-021610" selected="true" />
-    <select idref="RHEL-07-021620" selected="true" />
-    <select idref="RHEL-07-021760" selected="true" />
-    <select idref="RHEL-07-021910" selected="true" />
-    <select idref="RHEL-07-030010" selected="true" />
-    <select idref="RHEL-07-030090" selected="true" />
-    <select idref="RHEL-07-030310" selected="true" />
-    <select idref="RHEL-07-030330" selected="true" />
-    <select idref="RHEL-07-030331" selected="true" />
-    <select idref="RHEL-07-030340" selected="true" />
-    <select idref="RHEL-07-030350" selected="true" />
-    <select idref="RHEL-07-030351" selected="true" />
-    <select idref="RHEL-07-030352" selected="true" />
-    <select idref="RHEL-07-030380" selected="true" />
-    <select idref="RHEL-07-030381" selected="true" />
-    <select idref="RHEL-07-030382" selected="true" />
-    <select idref="RHEL-07-030383" selected="true" />
-    <select idref="RHEL-07-030390" selected="true" />
-    <select idref="RHEL-07-030391" selected="true" />
-    <select idref="RHEL-07-030392" selected="true" />
-    <select idref="RHEL-07-030400" selected="true" />
-    <select idref="RHEL-07-030401" selected="true" />
-    <select idref="RHEL-07-030402" selected="true" />
-    <select idref="RHEL-07-030403" selected="true" />
-    <select idref="RHEL-07-030404" selected="true" />
-    <select idref="RHEL-07-030405" selected="true" />
-    <select idref="RHEL-07-030420" selected="true" />
-    <select idref="RHEL-07-030421" selected="true" />
-    <select idref="RHEL-07-030422" selected="true" />
-    <select idref="RHEL-07-030423" selected="true" />
-    <select idref="RHEL-07-030424" selected="true" />
-    <select idref="RHEL-07-030425" selected="true" />
-    <select idref="RHEL-07-030441" selected="true" />
-    <select idref="RHEL-07-030442" selected="true" />
-    <select idref="RHEL-07-030443" selected="true" />
-    <select idref="RHEL-07-030444" selected="true" />
-    <select idref="RHEL-07-030490" selected="true" />
-    <select idref="RHEL-07-030491" selected="true" />
-    <select idref="RHEL-07-030492" selected="true" />
-    <select idref="RHEL-07-030510" selected="true" />
-    <select idref="RHEL-07-030511" selected="true" />
-    <select idref="RHEL-07-030512" selected="true" />
-    <select idref="RHEL-07-030513" selected="true" />
-    <select idref="RHEL-07-030514" selected="true" />
-    <select idref="RHEL-07-030521" selected="true" />
-    <select idref="RHEL-07-030522" selected="true" />
-    <select idref="RHEL-07-030526" selected="true" />
-    <select idref="RHEL-07-030523" selected="true" />
-    <select idref="RHEL-07-030524" selected="true" />
-    <select idref="RHEL-07-030525" selected="true" />
-    <select idref="RHEL-07-030530" selected="true" />
-    <select idref="RHEL-07-030531" selected="true" />
-    <select idref="RHEL-07-030540" selected="true" />
-    <select idref="RHEL-07-030541" selected="true" />
-    <select idref="RHEL-07-030550" selected="true" />
-    <select idref="RHEL-07-030560" selected="true" />
-    <select idref="RHEL-07-030561" selected="true" />
-    <select idref="RHEL-07-030630" selected="true" />
-    <select idref="RHEL-07-030670" selected="true" />
-    <select idref="RHEL-07-030671" selected="true" />
-    <select idref="RHEL-07-030672" selected="true" />
-    <select idref="RHEL-07-030673" selected="true" />
-    <select idref="RHEL-07-030674" selected="true" />
-    <select idref="RHEL-07-030710" selected="true" />
-    <select idref="RHEL-07-030750" selected="true" />
-    <select idref="RHEL-07-030751" selected="true" />
-    <select idref="RHEL-07-030752" selected="true" />
-    <select idref="RHEL-07-030753" selected="true" />
-    <select idref="RHEL-07-030754" selected="true" />
-    <select idref="RHEL-07-030770" selected="true" />
-    <select idref="RHEL-07-030780" selected="true" />
-    <select idref="RHEL-07-030810" selected="true" />
-    <select idref="RHEL-07-030820" selected="true" />
-    <select idref="RHEL-07-040010" selected="true" />
-    <select idref="RHEL-07-040020" selected="true" />
-    <select idref="RHEL-07-040030" selected="true" />
-    <select idref="RHEL-07-040040" selected="true" />
-    <select idref="RHEL-07-040050" selected="true" />
-    <select idref="RHEL-07-040060" selected="true" />
-    <select idref="RHEL-07-040070" selected="true" />
-    <select idref="RHEL-07-040080" selected="true" />
-    <select idref="RHEL-07-040100" selected="true" />
-    <select idref="RHEL-07-040110" selected="true" />
-    <select idref="RHEL-07-040160" selected="true" />
-    <select idref="RHEL-07-040170" selected="true" />
-    <select idref="RHEL-07-040180" selected="true" />
-    <select idref="RHEL-07-040181" selected="true" />
-    <select idref="RHEL-07-040182" selected="true" />
-    <select idref="RHEL-07-040190" selected="true" />
-    <select idref="RHEL-07-040191" selected="true" />
-    <select idref="RHEL-07-040210" selected="true" />
-    <select idref="RHEL-07-040230" selected="true" />
-    <select idref="RHEL-07-040250" selected="true" />
-    <select idref="RHEL-07-040260" selected="true" />
-    <select idref="RHEL-07-040261" selected="true" />
-    <select idref="RHEL-07-040290" selected="true" />
-    <select idref="RHEL-07-040300" selected="true" />
-    <select idref="RHEL-07-040301" selected="true" />
-    <select idref="RHEL-07-040310" selected="true" />
-    <select idref="RHEL-07-040320" selected="true" />
-    <select idref="RHEL-07-040330" selected="true" />
-    <select idref="RHEL-07-040331" selected="true" />
-    <select idref="RHEL-07-040334" selected="true" />
-    <select idref="RHEL-07-040332" selected="true" />
-    <select idref="RHEL-07-040333" selected="true" />
-    <select idref="RHEL-07-040350" selected="true" />
-    <select idref="RHEL-07-040351" selected="true" />
-    <select idref="RHEL-07-040380" selected="true" />
-    <select idref="RHEL-07-040410" selected="true" />
-    <select idref="RHEL-07-040420" selected="true" />
-    <select idref="RHEL-07-040421" selected="true" />
-    <select idref="RHEL-07-040470" selected="true" />
-    <select idref="RHEL-07-040480" selected="true" />
-    <select idref="RHEL-07-040490" selected="true" />
-    <select idref="RHEL-07-040500" selected="true" />
-    <select idref="RHEL-07-040520" selected="true" />
-    <select idref="RHEL-07-040540" selected="true" />
-    <select idref="RHEL-07-040560" selected="true" />
-    <select idref="RHEL-07-040580" selected="true" />
-    <select idref="RHEL-07-040590" selected="true" />
-    <select idref="RHEL-07-040620" selected="true" />
-    <select idref="RHEL-07-040640" selected="true" />
-    <select idref="RHEL-07-040650" selected="true" />
-    <select idref="RHEL-07-040660" selected="true" />
-    <select idref="RHEL-07-040670" selected="true" />
-    <select idref="RHEL-07-040680" selected="true" />
-    <select idref="RHEL-07-040690" selected="true" />
-    <select idref="RHEL-07-040700" selected="true" />
-    <select idref="RHEL-07-040730" selected="true" />
-    <select idref="RHEL-07-040740" selected="true" />
-    <select idref="RHEL-07-040810" selected="true" />
-    <select idref="RHEL-07-040820" selected="true" />
-    <select idref="RHEL-07-040830" selected="true" />
-    <select idref="RHEL-07-040860" selected="true" />
-  </Profile>
-  <Group id="RHEL-07-010010">
-    <title>SRG-OS-000257-GPOS-00098</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010010_rule" severity="high" weight="10.0">
-      <version>RHEL-07-010010</version>
-      <title>The file permissions, ownership, and group membership of system files and commands must match the vendor values.</title>
-      <description>&lt;VulnDiscussion&gt;Discretionary access control is weakened if a user or group has access permissions to system files and directories greater than the default.
-
-Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000278-GPOS-00108&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001494</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001496</ident>
-      <fixtext fixref="F-RHEL-07-010010_fix">Run the following command to determine which package owns the file:
-
-# rpm -qf &lt;filename&gt;
-
-Reset the permissions of files within a package with the following command:
-
-#rpm --setperms &lt;packagename&gt;
-
-Reset the user and group ownership of files within a package with the following command:
-
-#rpm --setugids &lt;packagename&gt;</fixtext>
-      <fix id="F-RHEL-07-010010_fix" />
-      <check system="C-RHEL-07-010010_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the file permissions, ownership, and group membership of system files and commands match the vendor values.
-Check the file permissions, ownership, and group membership of system files and commands with the following command:
-
-# rpm -Va | grep '^.M'
-
-If there is any output from the command, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010020">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010020_rule" severity="high" weight="10.0">
-      <version>RHEL-07-010020</version>
-      <title>The cryptographic hash of system files and commands must match vendor values.</title>
-      <description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections, system command and files can be altered by unauthorized users without detection.
-
-Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000663</ident>
-      <fixtext fixref="F-RHEL-07-010020_fix">Run the following command to determine which package owns the file:
-
-# rpm -qf &lt;filename&gt;
-
-The package can be reinstalled from a yum repository using the command:
-
-# sudo yum reinstall &lt;packagename&gt;
-
-Alternatively, the package can be reinstalled from trusted media using the command:
-
-# sudo rpm -Uvh &lt;packagename&gt;</fixtext>
-      <fix id="F-RHEL-07-010020_fix" />
-      <check system="C-RHEL-07-010020_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the cryptographic hash of system files and commands match the vendor values.
-
-Check the cryptographic hash of system files and commands with the following command:
-
-Note: System configuration files (indicated by a "c" in the second column) are expected to change over time. Unusual modifications should be investigated through the system audit log.
-
-# rpm -Va | grep '^..5'
-
-If there is any output from the command for system binaries, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010030">
-    <title>SRG-OS-000023-GPOS-00006</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010030_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010030</version>
-      <title>The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon.</title>
-      <description>&lt;VulnDiscussion&gt;Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
-
-System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.
-
-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 &amp; consent to terms in IS user agreem't."
-
-Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000048</ident>
-      <fixtext fixref="F-RHEL-07-010030_fix">Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
-
-Note: If the system does not have GNOME installed, this requirement is Not Applicable.
-
-Create a database to contain the system-wide graphical user logon settings (if it does not already exist) with the following command:
-
-# touch /etc/dconf/db/local.d/01-banner-message
-
-Add the following line to the [org/gnome/login-screen] section of the /etc/dconf/db/local.d/01-banner-message:
-
-[org/gnome/login-screen]
-banner-message-enable=true</fixtext>
-      <fix id="F-RHEL-07-010030_fix" />
-      <check system="C-RHEL-07-010030_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a graphical user logon.
-
-Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
-
-Check to see if the operating system displays a banner at the logon screen with the following command:
-
-# grep banner-message-enable /etc/dconf/db/local.d/*
-banner-message-enable=true
-
-If banner-message-enable is set to false or is missing, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010031">
-    <title>SRG-OS-000023-GPOS-00006</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010031_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010031</version>
-      <title>The operating system must display the approved Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon.</title>
-      <description>&lt;VulnDiscussion&gt;Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
-
-System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.
-
-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 &amp; consent to terms in IS user agreem't."
-
-Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000048</ident>
-      <fixtext fixref="F-RHEL-07-010031_fix">Configure the operating system to display the approved Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
-
-Note: If the system does not have GNOME installed, this requirement is Not Applicable.
-
-Create a database to contain the system-wide graphical user logon settings (if it does not already exist) with the following command:
-
-# touch /etc/dconf/db/local.d/01-banner-message
-
-Add the following lines to the [org/gnome/login-screen] section of the /etc/dconf/db/local.d/01-banner-message:
-
-[org/gnome/login-screen]
-banner-message-text=’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.’</fixtext>
-      <fix id="F-RHEL-07-010031_fix" />
-      <check system="C-RHEL-07-010031_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system displays the approved Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a graphical user logon.
-
-Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
-
-Check that the operating system displays the exact approved Standard Mandatory DoD Notice and Consent Banner text with the command:
-
-# grep banner-message-text /etc/dconf/db/local.d/*
-banner-message-text=
-‘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 does not match the approved Standard Mandatory DoD Notice and Consent Banner, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010040">
-    <title>SRG-OS-000023-GPOS-00006</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010040_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010040</version>
-      <title>The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a command line user logon.</title>
-      <description>&lt;VulnDiscussion&gt;Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
-
-System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.
-
-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 &amp; consent to terms in IS user agreem't."
-
-Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000048</ident>
-      <fixtext fixref="F-RHEL-07-010040_fix">Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via the command line by editing the /etc/issue file.
-
-Replace the default text with the Standard Mandatory DoD Notice and Consent Banner. The DoD required text is:
-
-"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."</fixtext>
-      <fix id="F-RHEL-07-010040_fix" />
-      <check system="C-RHEL-07-010040_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a command line user logon.
-
-Check to see if the operating system displays a banner at the command line logon screen with the following command:
-
-# more /etc/issue
-
-The command should return the following text:
-“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 operating system does not display a graphical logon banner or the banner does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding.
-
-If the text in the /etc/issue file does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010060">
-    <title>SRG-OS-000028-GPOS-00009</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010060_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010060</version>
-      <title>The operating system must enable a user session lock until that user re-establishes 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, the session lock must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system.
-
-Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000056</ident>
-      <fixtext fixref="F-RHEL-07-010060_fix">Configure the operating system to enable a user's session lock until that user re-establishes access using established identification and authentication procedures.
-
-Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command:
-
-# touch /etc/dconf/db/local.d/00-screensaver
-
-Add the setting to enable screensaver locking to the file:
-
-[org/gnome/desktop/screensaver]
-lock-enabled=true
-
-After the setting has been set, run dconf update.</fixtext>
-      <fix id="F-RHEL-07-010060_fix" />
-      <check system="C-RHEL-07-010060_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system enables a user's session lock until that user re-establishes access using established identification and authentication procedures. The screen program must be installed to lock sessions on the console.
-
-Note: If the system does not have GNOME installed, this requirement is Not Applicable.
-
-Check to see if the screen lock is enabled with the following command:
-
-# grep -i lock-enabled /etc/dconf/db/local.d/00-screensaver
-lock-enabled=true
-
-If the "lock-enabled" setting is missing or is not set to true, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010070">
-    <title>SRG-OS-000029-GPOS-00010</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010070_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010070</version>
-      <title>The operating system must initiate a screensaver after a 15-minute period of inactivity for graphical user interfaces.</title>
-      <description>&lt;VulnDiscussion&gt;A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
-
-The session lock is implemented at the point where session activity can be determined and/or controlled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000057</ident>
-      <fixtext fixref="F-RHEL-07-010070_fix">Configure the operating system to initiate a screensaver after a 15-minute period of inactivity for graphical user interfaces.
-
-Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: 
-
-# touch /etc/dconf/db/local.d/00-screensaver
-
-Add the setting to enable screensaver/session locking after 15 minutes of inactivity:
-
-[org/gnome/desktop/screensaver]
-
-idle-delay=uint32 900
-
-After the setting has been set, run dconf update.</fixtext>
-      <fix id="F-RHEL-07-010070_fix" />
-      <check system="C-RHEL-07-010070_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system initiates a screensaver after a 15-minute period of inactivity for graphical user interfaces. The screen program must be installed to lock sessions on the console.
-
-Note: If the system does not have GNOME installed, this requirement is Not Applicable.
-
-Check to see if GNOME is configured to display a screensaver after a 15 minute delay with the following command:
-
-# grep -i idle-delay /etc/dconf/db/local.d/*
-idle-delay=uint32 900
-
-If the "idle-delay" setting is missing or is not set to “900” or less, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010074">
-    <title>SRG-OS-000029-GPOS-00010</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010074_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010074</version>
-      <title>The operating system must initiate a session lock for graphical user interfaces when the screensaver is activated.</title>
-      <description>&lt;VulnDiscussion&gt;A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
-
-The session lock is implemented at the point where session activity can be determined and/or controlled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000057</ident>
-      <fixtext fixref="F-RHEL-07-010074_fix">Configure the operating system to initiate a session lock for graphical user interfaces when a screensaver is activated.
-
-Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: 
-
-# touch /etc/dconf/db/local.d/00-screensaver
-
-Add the setting to enable session locking when a screensaver is activated:
-
-[org/gnome/desktop/screensaver]
-lock-delay=uint32 5
-
-After the setting has been set, run dconf update.</fixtext>
-      <fix id="F-RHEL-07-010074_fix" />
-      <check system="C-RHEL-07-010074_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system initiates a session lock a for graphical user interfaces when the screensaver is activated. The screen program must be installed to lock sessions on the console.
-
-Note: If the system does not have GNOME installed, this requirement is Not Applicable.
-
-If GNOME is installed, check to see a session lock occurs when the screensaver is activated with the following command:
-
-# grep -i lock-delay /etc/dconf/db/local.d/*
-lock-delay=uint32 5
-
-If the “lock-delay” setting is missing, or is not set, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010071">
-    <title>SRG-OS-000029-GPOS-00010</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010071_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010071</version>
-      <title>The operating system must initiate a session lock after a 15-minute period of inactivity for all connection types.</title>
-      <description>&lt;VulnDiscussion&gt;A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
-
-The session lock is implemented at the point where session activity can be determined and/or controlled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000057</ident>
-      <fixtext fixref="F-RHEL-07-010071_fix">Configure the operating system to initiate a session lock after a 15-minute period of inactivity for graphical user interfaces.
-
-Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: 
-
-# touch /etc/dconf/db/local.d/locks/session
-
-Add the settings to enable screensaver/session locking after 15 minutes of inactivity:
-
-/org/gnome/desktop/screensaver/idle-delay
-/org/gnome/desktop/screensaver/lock-delay
-/org/gnome/desktop/session/idle-delay</fixtext>
-      <fix id="F-RHEL-07-010071_fix" />
-      <check system="C-RHEL-07-010071_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system prevents the user from overriding session lock after a 15-minute period of inactivity for graphical user interfaces. The screen program must be installed to lock sessions on the console.
-
-If it is installed, GNOME must be configured to prevent users from overriding the system-wide session lock settings. Check for the session lock settings with the following commands:
-
-# grep -i idle-delay /etc/dconf/db/local.d/locks/*
-
-/org/gnome/desktop/screensaver/idle-delay
-/org/gnome/desktop/session/idle-delay
-
-If the command does not return a result for the screensaver and session keywords, this is a finding.
-
-# grep -i lock-delay /etc/dconf/db/local.d/locks/*
-
-/org/gnome/desktop/screensaver/lock-delay
-
-If the command does not return a result, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010072">
-    <title>SRG-OS-000029-GPOS-00010</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010072_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010072</version>
-      <title>The operating system must have the screen package installed.</title>
-      <description>&lt;VulnDiscussion&gt;A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
-
-The screen package allows for a session lock to be implemented and configured.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000057</ident>
-      <fixtext fixref="F-RHEL-07-010072_fix">Install the screen package to allow the initiation a session lock after a 15-minute period of inactivity for graphical users interfaces.
-
-Install the screen program (if it is not on the system) with the following command:
-
-# yum install screen
-
-The console can now be locked with the following key combination: 
-
-ctrl+a x</fixtext>
-      <fix id="F-RHEL-07-010072_fix" />
-      <check system="C-RHEL-07-010072_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system has the screen package installed.
-
-Check to see if the screen package is installed with the following command:
-
-# yum list installed | grep screen
-screen-4.3.1-3-x86_64.rpm
-
-If is not installed, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010073">
-    <title>SRG-OS-000029-GPOS-00010</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010073_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010073</version>
-      <title>The operating system must initiate a session lock for the screensaver after a period of inactivity for graphical user interfaces.</title>
-      <description>&lt;VulnDiscussion&gt;A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
-
-The session lock is implemented at the point where session activity can be determined and/or controlled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000057</ident>
-      <fixtext fixref="F-RHEL-07-010073_fix">Configure the operating system to initiate a session lock after a 15-minute period of inactivity for graphical user interfaces.
-
-Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: 
-
-# touch /etc/dconf/db/local.d/00-screensaver
-
-Add the setting to enable screensaver locking after 15 minutes of inactivity:
-
-[org/gnome/desktop/screensaver]
-
-idle-activation-enabled=true</fixtext>
-      <fix id="F-RHEL-07-010073_fix" />
-      <check system="C-RHEL-07-010073_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system initiates a session lock after a 15-minute period of inactivity for graphical user interfaces. The screen program must be installed to lock sessions on the console.
-
-If it is installed, GNOME must be configured to enforce a session lock after a 15-minute delay. Check for the session lock settings with the following commands:
-
-# grep -i  idle_activation_enabled /etc/dconf/db/local.d/*
-[org/gnome/desktop/screensaver]   idle-activation-enabled=true
-
-If the idle-activation-enabled not set to “true”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010090">
-    <title>SRG-OS-000069-GPOS-00037</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010090_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010090</version>
-      <title>When passwords are changed or new passwords are established, the new password must contain at least one upper-case character.</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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000192</ident>
-      <fixtext fixref="F-RHEL-07-010090_fix">Configure the operating system to enforce password complexity by requiring that at least one upper-case character be used by setting the “ucredit” option.
-
-Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value):
-
-ucredit = -1</fixtext>
-      <fix id="F-RHEL-07-010090_fix" />
-      <check system="C-RHEL-07-010090_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Note: The value to require a number of upper-case characters to be set is expressed as a negative number in /etc/security/pwquality.conf.
-
-Check the value for "ucredit" in /etc/security/pwquality.conf with the following command:
-
-# grep ucredit /etc/security/pwquality.conf 
-ucredit = -1
-
-If the value of "ucredit" is not set to a negative value, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010100">
-    <title>SRG-OS-000070-GPOS-00038</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010100_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010100</version>
-      <title>When passwords are changed or new passwords are established, the new password must contain at least one lower-case character.</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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000193</ident>
-      <fixtext fixref="F-RHEL-07-010100_fix">Configure the operating system to enforce password complexity by requiring that at least one lower-case character be used by setting the “lcredit” option.
-
-Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value):
-
-lcredit = -1</fixtext>
-      <fix id="F-RHEL-07-010100_fix" />
-      <check system="C-RHEL-07-010100_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Note: The value to require a number of lower-case characters to be set is expressed as a negative number in /etc/security/pwquality.conf.
-
-Check the value for "lcredit" in /etc/security/pwquality.conf with the following command:
-
-# grep lcredit /etc/security/pwquality.conf 
-lcredit = -1 
-
-If the value of "lcredit" is not set to a negative value, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010110">
-    <title>SRG-OS-000071-GPOS-00039</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010110_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010110</version>
-      <title>When passwords are changed or new passwords are assigned, the new password must contain at least one numeric character.</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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000194</ident>
-      <fixtext fixref="F-RHEL-07-010110_fix">Configure the operating system to enforce password complexity by requiring that at least one numeric character be used by setting the “dcredit” option.
-
-Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value):
-
-dcredit = -1</fixtext>
-      <fix id="F-RHEL-07-010110_fix" />
-      <check system="C-RHEL-07-010110_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Note: The value to require a number of numeric characters to be set is expressed as a negative number in /etc/security/pwquality.conf.
-
-Check the value for "dcredit" in /etc/security/pwquality.conf with the following command:
-
-# grep dcredit /etc/security/pwquality.conf 
-dcredit = -1 
-
-If the value of “dcredit” is not set to a negative value, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010120">
-    <title>SRG-OS-000266-GPOS-00101</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010120_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010120</version>
-      <title>When passwords are changed or new passwords are assigned, the new password must contain at least one special character.</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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001619</ident>
-      <fixtext fixref="F-RHEL-07-010120_fix">Configure the operating system to enforce password complexity by requiring that at least one special character be used by setting the “dcredit” option.
-
-Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value):
-
-ocredit = -1</fixtext>
-      <fix id="F-RHEL-07-010120_fix" />
-      <check system="C-RHEL-07-010120_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system enforces password complexity by requiring that at least one special character be used.
-
-Note: The value to require a number of special characters to be set is expressed as a negative number in /etc/security/pwquality.conf.
-
-Check the value for “ocredit” in /etc/security/pwquality.conf with the following command:
-
-# grep ocredit /etc/security/pwquality.conf 
-ocredit=-1
-
-If the value of “ocredit” is not set to a negative value, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010130">
-    <title>SRG-OS-000072-GPOS-00040</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010130_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010130</version>
-      <title>When passwords are changed a minimum of eight of the total number of characters must be changed.</title>
-      <description>&lt;VulnDiscussion&gt;Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
-
-Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000195</ident>
-      <fixtext fixref="F-RHEL-07-010130_fix">Configure the operating system to require the change of at least eight of the total number of characters when passwords are changed by setting the “difok” option.
-
-Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value):
-
-difok = 8</fixtext>
-      <fix id="F-RHEL-07-010130_fix" />
-      <check system="C-RHEL-07-010130_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>The "difok" option sets the number of characters in a password that must not be present in the old password.
-
-Check for the value of the difok option in /etc/security/pwquality.conf with the following command:
-
-# grep difok /etc/security/pwquality.conf 
-difok = 8
-
-If the value of “difok” is set to less than 8, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010140">
-    <title>SRG-OS-000072-GPOS-00040</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010140_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010140</version>
-      <title>When passwords are changed a minimum of four character classes must be changed.</title>
-      <description>&lt;VulnDiscussion&gt;Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
-
-Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000195</ident>
-      <fixtext fixref="F-RHEL-07-010140_fix">Configure the operating system to require the change of at least four character classes when passwords are changed by setting the “minclass” option.
-
-Add the following line to /etc/security/pwquality.conf conf (or modify the line to have the required value):
-
-minclass = 4</fixtext>
-      <fix id="F-RHEL-07-010140_fix" />
-      <check system="C-RHEL-07-010140_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>The "minclass" option sets the minimum number of required classes of characters for the new password (digits, uppercase, lowercase, others).
-
-Check for the value of the “minclass” option in /etc/security/pwquality.conf with the following command:
-
-# grep minclass /etc/security/pwquality.conf 
-minclass = 4
-
-If the value of “minclass” is set to less than 4, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010150">
-    <title>SRG-OS-000072-GPOS-00040</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010150_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010150</version>
-      <title>When passwords are changed the number of repeating consecutive characters must not be more than four characters.</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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000195</ident>
-      <fixtext fixref="F-RHEL-07-010150_fix">Configure the operating system to require the change of the number of repeating consecutive characters when passwords are changed by setting the “maxrepeat” option.
-
-Add the following line to /etc/security/pwquality.conf conf (or modify the line to have the required value):
-
-maxrepeat = 2</fixtext>
-      <fix id="F-RHEL-07-010150_fix" />
-      <check system="C-RHEL-07-010150_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>The "maxrepeat" option sets the maximum number of allowed same consecutive characters in a new password.
-
-Check for the value of the “maxrepeat” option in /etc/security/pwquality.conf with the following command:
-
-# grep maxrepeat /etc/security/pwquality.conf 
-maxrepeat = 2
-
-If the value of “maxrepeat” is set to more than 2, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010160">
-    <title>SRG-OS-000072-GPOS-00040</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010160_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010160</version>
-      <title>When passwords are changed the number of repeating characters of the same character class must not be more than four characters.</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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000195</ident>
-      <fixtext fixref="F-RHEL-07-010160_fix">Configure the operating system to require the change of the number of repeating characters of the same character class when passwords are changed by setting the “maxclassrepeat” option.
-
-Add the following line to /etc/security/pwquality.conf conf (or modify the line to have the required value):
-
-maxclassrepeat = 4</fixtext>
-      <fix id="F-RHEL-07-010160_fix" />
-      <check system="C-RHEL-07-010160_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>The "maxclassrepeat" option sets the maximum number of allowed same consecutive characters in the same class in the new password.
-
-Check for the value of the maxclassrepeat option in /etc/security/pwquality.conf with the following command:
-
-# grep maxclassrepeat /etc/security/pwquality.conf 
-maxclassrepeat = 4
-
-If the value of “maxclassrepeat” is set to more than 4, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010170">
-    <title>SRG-OS-000073-GPOS-00041</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010170_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010170</version>
-      <title>The PAM system service must be configured to store only encrypted representations of passwords.</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. Passwords encrypted with a weak algorithm are no more protected than if they are kept in plain text.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000196</ident>
-      <fixtext fixref="F-RHEL-07-010170_fix">Configure the operating system to store only SHA512 encrypted representations of passwords.
-
-Add the following line in /etc/pam.d/system-auth:
-
-password sufficient pam_unix.so sha512</fixtext>
-      <fix id="F-RHEL-07-010170_fix" />
-      <check system="C-RHEL-07-010170_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the PAM system service is configured to store only encrypted representations of passwords. The strength of encryption that must be used to hash passwords for all accounts is SHA512.
-
-Check that the system is configured to create SHA512 hashed passwords with the following command:
-
-# grep password /etc/pam.d/system-auth
-password sufficient pam_unix.so sha512
-
-If the /etc/pam.d/system-auth configuration files allow for password hashes other than SHA512 to be used, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010180">
-    <title>SRG-OS-000073-GPOS-00041</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010180_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010180</version>
-      <title>The shadow file must be configured to store only encrypted representations of passwords.</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. Passwords encrypted with a weak algorithm are no more protected than if they are kept in plain text.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000196</ident>
-      <fixtext fixref="F-RHEL-07-010180_fix">Configure the operating system to store only SHA512 encrypted representations of passwords.
-
-Add or update the following line in /etc/login.defs:
-
-ENCRYPT_METHOD SHA512</fixtext>
-      <fix id="F-RHEL-07-010180_fix" />
-      <check system="C-RHEL-07-010180_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system's shadow file is configured to store only encrypted representations of passwords. The strength of encryption that must be used to hash passwords for all accounts is SHA512.
-
-Check that the system is configured to create SHA512 hashed passwords with the following command:
-
-# grep -i encrypt /etc/login.defs
-ENCRYPT_METHOD SHA512
-
-If the /etc/login.defs configuration file does not exist or allows for password hashes other than SHA512 to be used, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010190">
-    <title>SRG-OS-000073-GPOS-00041</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010190_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010190</version>
-      <title>User and group account administration utilities must be configured to store only encrypted representations of passwords.</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. Passwords encrypted with a weak algorithm are no more protected than if they are kept in plain text.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000196</ident>
-      <fixtext fixref="F-RHEL-07-010190_fix">Configure the operating system to store only SHA512 encrypted representations of passwords.
-
-Add or update the following line in /etc/libuser.conf in the [defaults] section: 
-
-crypt_style = sha512</fixtext>
-      <fix id="F-RHEL-07-010190_fix" />
-      <check system="C-RHEL-07-010190_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the user and group account administration utilities are configured to store only encrypted representations of passwords. The strength of encryption that must be used to hash passwords for all accounts is SHA512.
-
-Check that the system is configured to create SHA512 hashed passwords with the following command:
-
-# cat /etc/libuser.conf | grep -i sha512
-[defaults]
-
-crypt_style = sha512
-
-If the "crypt_style" variable is not set to "sha512", is not in the defaults section, or does not exist, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010200">
-    <title>SRG-OS-000075-GPOS-00043</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010200_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010200</version>
-      <title>Passwords for new users must be restricted to a 24 hours/1 day minimum lifetime.</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, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000198</ident>
-      <fixtext fixref="F-RHEL-07-010200_fix">Configure the operating system to enforce 24 hours/1 day as the minimum password lifetime.
-
-Add the following line in /etc/login.defs (or modify the line to have the required value):
-
-PASS_MIN_DAYS     1</fixtext>
-      <fix id="F-RHEL-07-010200_fix" />
-      <check system="C-RHEL-07-010200_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system enforces 24 hours/1 day as the minimum password lifetime for new user accounts.
-
-Check for the value of “PASS_MIN_DAYS” in /etc/login.defs with the following command: 
-
-# grep -i pass_min_days /etc/login.defs
-PASS_MIN_DAYS     1
-
-If the “PASS_MIN_DAYS” parameter value is not “1” or greater, or is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010210">
-    <title>SRG-OS-000075-GPOS-00043</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010210_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010210</version>
-      <title>Passwords must be restricted to a 24 hours/1 day minimum lifetime.</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, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000198</ident>
-      <fixtext fixref="F-RHEL-07-010210_fix">Configure non-compliant accounts to enforce a 24 hours/1 day minimum password lifetime:
-
-# chage -m 1 [user]</fixtext>
-      <fix id="F-RHEL-07-010210_fix" />
-      <check system="C-RHEL-07-010210_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Check whether the minimum time period between password changes for each user account is one day or greater.
-
-# awk -F: '$4 &lt; 1 {print $1}' /etc/shadow
-
-If any results are returned that are not associated with a system account, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010220">
-    <title>SRG-OS-000076-GPOS-00044</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010220_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010220</version>
-      <title>Passwords for new users must be restricted to a 60-day maximum lifetime.</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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000199</ident>
-      <fixtext fixref="F-RHEL-07-010220_fix">Configure the operating system to enforce a 60-day maximum password lifetime restriction.
-
-Add the following line in /etc/login.defs (or modify the line to have the required value):
-
-PASS_MAX_DAYS     60</fixtext>
-      <fix id="F-RHEL-07-010220_fix" />
-      <check system="C-RHEL-07-010220_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system enforces a 60-day maximum password lifetime restriction for new user accounts.
-
-Check for the value of “PASS_MAX_DAYS” in /etc/login.defs with the following command:
-
-# grep -i pass_max_days /etc/login.defs
-PASS_MAX_DAYS     60
-
-If the “PASS_MAX_DAYS” parameter value is not 60 or less, or is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010230">
-    <title>SRG-OS-000076-GPOS-00044</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010230_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010230</version>
-      <title>Existing passwords must be restricted to a 60-day maximum lifetime.</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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000199</ident>
-      <fixtext fixref="F-RHEL-07-010230_fix">Configure non-compliant accounts to enforce a 60-day maximum password lifetime restriction.
-
-# chage -M 60 [user]</fixtext>
-      <fix id="F-RHEL-07-010230_fix" />
-      <check system="C-RHEL-07-010230_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Check whether the maximum time period for existing passwords is restricted to 60 days.
-
-# awk -F: '$5 &gt; 60 {print $1}' /etc/shadow
-
-If any results are returned that are not associated with a system account, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010240">
-    <title>SRG-OS-000077-GPOS-00045</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010240_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010240</version>
-      <title>Passwords must be prohibited from reuse for a minimum of five generations.</title>
-      <description>&lt;VulnDiscussion&gt;Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000200</ident>
-      <fixtext fixref="F-RHEL-07-010240_fix">Configure the operating system to prohibit password reuse for a minimum of five generations.
-
-Add the following line in /etc/pam.d/system-auth (or modify the line to have the required value):
-
-password sufficient pam_unix.so use_authtok sha512 shadow remember=5</fixtext>
-      <fix id="F-RHEL-07-010240_fix" />
-      <check system="C-RHEL-07-010240_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system prohibits password reuse for a minimum of five generations.
-
-Check for the value of the “remember” argument in /etc/pam.d/system-auth with the following command:
-
-# grep -i remember /etc/pam.d/system-auth
-password sufficient pam_unix.so use_authtok sha512 shadow remember=5
-
-If the line containing the pam_unix.so line does not have the “remember” module argument set, or the value of the “remember” module argument is set to less than “5”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010250">
-    <title>SRG-OS-000078-GPOS-00046</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010250_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010250</version>
-      <title>Passwords must be a minimum of 15 characters in 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000205</ident>
-      <fixtext fixref="F-RHEL-07-010250_fix">Configure operating system to enforce a minimum 15-character password length.
-
-Add the following line to /etc/security/pwquality.conf conf (or modify the line to have the required value):
-
-minlen = 15</fixtext>
-      <fix id="F-RHEL-07-010250_fix" />
-      <check system="C-RHEL-07-010250_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system enforces a minimum 15-character password length. The “minlen” option sets the minimum number of characters in a new password.
-
-Check for the value of the “minlen” option in /etc/security/pwquality.conf with the following command:
-
-# grep minlen /etc/security/pwquality.conf
-minlen = 15
-
-If the command does not return a “minlen” value of 15 or greater, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010260">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010260_rule" severity="high" weight="10.0">
-      <version>RHEL-07-010260</version>
-      <title>The system must not have accounts configured with blank or null passwords.</title>
-      <description>&lt;VulnDiscussion&gt;If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-010260_fix">If an account is configured for password authentication but does not have an assigned password, it may be possible to log on to the account without authenticating.
-
-Remove any instances of the "nullok" option in "/etc/pam.d/system-auth" to prevent logons with empty passwords.</fixtext>
-      <fix id="F-RHEL-07-010260_fix" />
-      <check system="C-RHEL-07-010260_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>To verify that null passwords cannot be used, run the following command: 
-
-# grep nullok /etc/pam.d/system-auth
-
-If this produces any output, it may be possible to log on with accounts with empty passwords.
-
-If null passwords can be used, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010270">
-    <title>SRG-OS-000106-GPOS-00053</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010270_rule" severity="high" weight="10.0">
-      <version>RHEL-07-010270</version>
-      <title>The SSH daemon must not allow authentication using an empty password.</title>
-      <description>&lt;VulnDiscussion&gt;Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000766</ident>
-      <fixtext fixref="F-RHEL-07-010270_fix">To explicitly disallow remote logon from accounts with empty passwords, add or correct the following line in "/etc/ssh/sshd_config":
-
-PermitEmptyPasswords no
-
-Any accounts with empty passwords should be disabled immediately, and PAM configuration should prevent users from being able to assign themselves empty passwords.</fixtext>
-      <fix id="F-RHEL-07-010270_fix" />
-      <check system="C-RHEL-07-010270_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>To determine how the SSH daemon's "PermitEmptyPasswords" option is set, run the following command:
-
-# grep -i PermitEmptyPasswords /etc/ssh/sshd_config
-
-If no line, a commented line, or a line indicating the value "no" is returned, the required value is set.
-
-If the required value is not set, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010280">
-    <title>SRG-OS-000118-GPOS-00060</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010280_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010280</version>
-      <title>The operating system must disable account identifiers (individuals, groups, roles, and devices) if the password expires.</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 zero 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000795</ident>
-      <fixtext fixref="F-RHEL-07-010280_fix">Configure the operating system to disable account identifiers (individuals, groups, roles, and devices) after the password expires.
-
-Add the following line /etc/default/useradd (or modify the line to have the required value):
-
-INACTIVE=0</fixtext>
-      <fix id="F-RHEL-07-010280_fix" />
-      <check system="C-RHEL-07-010280_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system disables account identifiers (individuals, groups, roles, and devices) after the password expires with the following command:
-
-# grep -i inactive /etc/default/useradd
-INACTIVE=0
-
-If the value is not set to “0”, is commented out, or is not defined, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010371">
-    <title>SRG-OS-000329-GPOS-00128</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010371_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010371</version>
-      <title>If three unsuccessful logon attempts within 15 minutes occur the associated account must be locked.</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-000329-GPOS-00128, SRG-OS-000021-GPOS-00005&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002238</ident>
-      <fixtext fixref="F-RHEL-07-010371_fix">Configure the operating system to lock an account for the maximum period when three unsuccessful logon attempts in 15 minutes are made.
-
-Modify the first three lines of the auth section of the /etc/pam.d/system-auth and /etc/pam.d/password-auth files to match the following lines:
-
-auth        required       pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=604800
-auth        sufficient     pam_unix.so try_first_pass
-auth        [default=die]  pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=604800</fixtext>
-      <fix id="F-RHEL-07-010371_fix" />
-      <check system="C-RHEL-07-010371_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system automatically locks an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made.
-
-Check that the system locks the account after three unsuccessful logon attempts within a period of 15 minutes with the following command:
-
-# grep pam_faillock.so /etc/pam.d/password-auth
-auth        required       pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900
-auth        [default=die]  pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900
-
-If the “fail_interval” setting is greater than 900 on both lines with the pam_faillock.so module name or is missing from a line, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010372">
-    <title>SRG-OS-000329-GPOS-00128</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010372_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010372</version>
-      <title>Accounts subject to three unsuccessful login attempts within 15 minutes must be locked for the maximum configurable period.</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-000329-GPOS-00128, SRG-OS-000021-GPOS-00005&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002238</ident>
-      <fixtext fixref="F-RHEL-07-010372_fix">Configure the operating system to lock an account for the maximum period when three unsuccessful logon attempts in 15 minutes are made.
-
-Modify the first three lines of the auth section of the /etc/pam.d/system-auth and /etc/pam.d/password-auth files to match the following lines:
-
-auth        required       pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=604800
-auth        sufficient     pam_unix.so try_first_pass
-auth        [default=die]  pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=604800</fixtext>
-      <fix id="F-RHEL-07-010372_fix" />
-      <check system="C-RHEL-07-010372_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system automatically locks an account for the maximum period for which the system can be configured.
-
-Check that the system locks an account for the maximum period after three unsuccessful logon attempts within a period of 15 minutes with the following command:
-
-# grep pam_faillock.so /etc/pam.d/password-auth
-auth        required       pam_faillock.so preauth silent audit deny=3 even_deny_root unlock_time=604800
-auth        [default=die]  pam_faillock.so authfail audit deny=3 even_deny_root unlock_time=604800
-
-If the “unlock_time” setting is greater than 604800 on both lines with the pam_faillock.so module name or is missing from a line, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010373">
-    <title>SRG-OS-000329-GPOS-00128</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010373_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010373</version>
-      <title>If three unsuccessful root logon attempts within 15 minutes occur the associated account must be locked.</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-000329-GPOS-00128, SRG-OS-000021-GPOS-00005&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002238</ident>
-      <fixtext fixref="F-RHEL-07-010373_fix">Configure the operating system to automatically lock the root account until the locked is released by an administrator when three unsuccessful logon attempts in 15 minutes are made.
-
-Modify the first three lines of the auth section of the /etc/pam.d/system-auth and /etc/pam.d/password-auth files to match the following lines:
-
-auth        required       pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=604800
-auth        sufficient     pam_unix.so try_first_pass
-auth        [default=die]  pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=604800</fixtext>
-      <fix id="F-RHEL-07-010373_fix" />
-      <check system="C-RHEL-07-010373_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system automatically locks the root account until it is released by an administrator when three unsuccessful logon attempts in 15 minutes are made.
-
-# grep pam_faillock.so /etc/pam.d/password-auth
-auth        required       pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900
-auth        [default=die]  pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900
-
-If the “even_deny_root” setting is not defined on both lines with the pam_faillock.so module name, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010380">
-    <title>SRG-OS-000373-GPOS-00156</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010380_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010380</version>
-      <title>Users must provide a password for privilege escalation.</title>
-      <description>&lt;VulnDiscussion&gt;Without re-authentication, users may access resources or perform tasks for which they do not have authorization. 
-
-When operating systems provide the capability to escalate a functional capability, it is critical the user re-authenticate.
-
-Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002038</ident>
-      <fixtext fixref="F-RHEL-07-010380_fix">Configure the operating system to require users to supply a password for privilege escalation.
-
-Check the configuration of the /etc/sudoers and /etc/sudoers.d/* files with the following command:
-
-# grep -i nopasswd /etc/sudoers /etc/sudoers.d/*
-
-Remove any occurrences of "NOPASSWD" tags in the file.</fixtext>
-      <fix id="F-RHEL-07-010380_fix" />
-      <check system="C-RHEL-07-010380_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system requires users to supply a password for privilege escalation.
-
-Check the configuration of the /etc/sudoers and /etc/sudoers.d/* files with the following command:
-
-# grep -i nopasswd /etc/sudoers /etc/sudoers.d/*
-
-If any line is found with a "NOPASSWD" tag, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010381">
-    <title>SRG-OS-000373-GPOS-00156</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010381_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010381</version>
-      <title>Users must re-authenticate for privilege escalation.</title>
-      <description>&lt;VulnDiscussion&gt;Without re-authentication, users may access resources or perform tasks for which they do not have authorization. 
-
-When operating systems provide the capability to escalate a functional capability, it is critical the user reauthenticate.
-
-Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002038</ident>
-      <fixtext fixref="F-RHEL-07-010381_fix">Configure the operating system to require users to reauthenticate for privilege escalation.
-
-Check the configuration of the /etc/sudoers and /etc/sudoers.d/* files with the following command:
-
-Remove any occurrences of "!authenticate" tags in the file.</fixtext>
-      <fix id="F-RHEL-07-010381_fix" />
-      <check system="C-RHEL-07-010381_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system requires users to reauthenticate for privilege escalation.
-
-Check the configuration of the /etc/sudoers and /etc/sudoers.d/* files with the following command:
-
-# grep -i authenticate /etc/sudoers /etc/sudoers.d/*
-
-If any line is found with a "!authenticate" tag, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010400">
-    <title>SRG-OS-000383-GPOS-00166</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010400_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010400</version>
-      <title>The operating system must prohibit the use of cached nss authenticators 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002007</ident>
-      <fixtext fixref="F-RHEL-07-010400_fix">Configure the operating system to prohibit the use of cached nss authenticators after one day.
-
-If “nss” is in use on the system, set the “memcache_timeout” value to “86400” or less in /etc/sssd/sssd.conf:
-
-memcache_timeout = 86400</fixtext>
-      <fix id="F-RHEL-07-010400_fix" />
-      <check system="C-RHEL-07-010400_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system prohibits the use of cached nss authenticators after one day.
-
-Check to see if the “sssd” service is active with the following command:
-
-# systemctl status sssd.service
-
-If the service is active, the command will return:
-
-sssd.service - System Security Services Daemon
-   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled)
-   Active: active (running) since Thu 2014-09-25 10:46:43 CEST; 5s ago
-
-If the service is not active, this is a finding.
-
-Check the services option for the active services of each domain configured with the following command:
-
-# grep services /etc/sssd/sssd.conf
-
-The command will return one line for each domain. In the example:
-
-services = nss, pam
-services = nss, pam
-
-There are two services lines as the “nss” and “pam” services are being used by two domains (ldap and local).
-
-If nss is an active service, check the memcache_timeout option with the following command:
-
-# grep -i memcache_timeout /etc/sssd/sssd.conf
-memcache_timeout = 86400
-
-If the “memcache_timeout” is set to a value greater than “86400”, is commented out, or is missing, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010401">
-    <title>SRG-OS-000383-GPOS-00166</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010401_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010401</version>
-      <title>The operating system must prohibit the use of cached PAM authenticators 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002007</ident>
-      <fixtext fixref="F-RHEL-07-010401_fix">Configure the operating system to prohibit the use of cached PAM authenticators after one day.
-
-If “pam” is in use on the system, set the “offline_credentials_expiration” value to “1” in /etc/sssd/sssd.conf:
-
-offline_credentials_expiration = 1</fixtext>
-      <fix id="F-RHEL-07-010401_fix" />
-      <check system="C-RHEL-07-010401_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system prohibits the use of cached PAM authenticators after one day.
-
-Check to see if the “sssd” service is active with the following command:
-
-# systemctl status sssd.service
-
-If the service is active, the command will return:
-
-sssd.service - System Security Services Daemon
-   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled)
-   Active: active (running) since Thu 2014-09-25 10:46:43 CEST; 5s ago
-
-If the service is not active, this is a finding.
-
-Check the services option for the active services of each domain configured with the following command:
-
-# grep services /etc/sssd/sssd.conf
-
-The command will return one line for each domain. In the example:
-
-services = nss, pam
-services = nss, pam
-
-There are two services lines as the “nss” and “pam” services are being used by two domains (ldap and local).
-
-If “pam” is an active service, check the “offline_credentials_expiration” option with the following command:
-
-# grep -i offline_credentials_expiration /etc/sssd/sssd.conf 
-offline_credentials_expiration = 1
-
-If “pam” is not an active service, this requirement is Not Applicable.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010402">
-    <title>SRG-OS-000383-GPOS-00166</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010402_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010402</version>
-      <title>The operating system must prohibit the use of cached SSH authenticators 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002007</ident>
-      <fixtext fixref="F-RHEL-07-010402_fix">Configure the operating system to prohibit the use of cached SSH authenticators after one day.
-
-If “ssh” is in use on the system, set the “ssh_known_hosts_timeout” value to “86400” or less in /etc/sssd/sssd.conf:
-
-ssh_known_hosts_timeout = 86400</fixtext>
-      <fix id="F-RHEL-07-010402_fix" />
-      <check system="C-RHEL-07-010402_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system prohibits the use of cached SSH authenticators after one day.
-
-Check to see if the “sssd” service is active with the following command:
-
-# systemctl status sssd.service
-
-If the service is active, the command will return:
-
-sssd.service - System Security Services Daemon
-   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled)
-   Active: active (running) since Thu 2014-09-25 10:46:43 CEST; 5s ago
-
-If the service is not active, this is a finding.
-
-Check the services option for the active services of each domain configured with the following command:
-
-# grep services /etc/sssd/sssd.conf
-
-The command will return one line for each domain. In the example:
-
-services = nss, pam
-services = nss, pam
-
-There are two services lines as the “nss” and “pam” services are being used by two domains (ldap and local).
-
-If “pam” is an active service, check the “offline_credentials_expiration” option with the following command:
-
-# grep -i offline_credentials_expiration /etc/sssd/sssd.conf 
-offline_credentials_expiration = 1
-
-If “offline_credentials_expiration” is set to a value greater than “1”, is commented out, or is missing, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010420">
-    <title>SRG-OS-000480-GPOS-00226</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010420_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010420</version>
-      <title>The delay between logon prompts following a failed console logon attempt must be at least four seconds.</title>
-      <description>&lt;VulnDiscussion&gt;Configuring the operating system to implement organization-wide security implementation guides and security checklists verifies compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
-
-Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example, registry settings; account, file, and directory permission settings; and settings for functions, ports, protocols, services, and remote connections.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-010420_fix">Configure the operating system to enforce a delay of at least four seconds between logon prompts following a failed console logon attempt.
-
-Modify the “/etc/login.defs” file to set the “FAIL_DELAY” parameter to “4” or greater:
-
-FAIL_DELAY 4</fixtext>
-      <fix id="F-RHEL-07-010420_fix" />
-      <check system="C-RHEL-07-010420_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system enforces a delay of at least four seconds between console logon prompts following a failed logon attempt.
-
-Check the value of the fail_delay parameter in “/etc/login.defs” file with the following command:
-
-# grep -i fail_delay /etc/login.defs
-FAIL_DELAY 4
-
-If the value of “FAIL_DELAY” is not set to “4” or greater, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010430">
-    <title>SRG-OS-000480-GPOS-00229</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010430_rule" severity="high" weight="10.0">
-      <version>RHEL-07-010430</version>
-      <title>The operating system must not allow an unattended or automatic logon to the system via a graphical user interface.</title>
-      <description>&lt;VulnDiscussion&gt;Failure to restrict system access to authenticated users negatively impacts operating system 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-010430_fix">Configure the operating system to not allow an unattended or automatic logon to the system via a graphical user interface.
-
-Note: If the system does not have GNOME installed, this requirement is Not Applicable.
-
-Add or edit the line for the “AutomaticLoginEnable” parameter in the [daemon] section of the “/etc/gdm/custom.conf” file to “false”:
-
-[daemon]
-AutomaticLoginEnable=false</fixtext>
-      <fix id="F-RHEL-07-010430_fix" />
-      <check system="C-RHEL-07-010430_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system does not allow an unattended or automatic logon to the system via a graphical user interface.
-
-Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
-
-Check for the value of the “AutomaticLoginEnable” in “/etc/gdm/custom.conf” file with the following command:
-
-# grep -i automaticloginenable /etc/gdm/custom.conf
-AutomaticLoginEnable=false
-
-If the value of “AutomaticLoginEnable” is not set to “false”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010431">
-    <title>SRG-OS-000480-GPOS-00229</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010431_rule" severity="high" weight="10.0">
-      <version>RHEL-07-010431</version>
-      <title>The operating system must not allow guest logon to the system.</title>
-      <description>&lt;VulnDiscussion&gt;Failure to restrict system access to authenticated users negatively impacts operating system 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-010431_fix">Configure the operating system to not allow a guest account to log on to the system via a graphical user interface.
-
-Note: If the system does not have GNOME installed, this requirement is Not Applicable.
-
-Add or edit the line for the “TimedLoginEnable” parameter in the [daemon] section of the “/etc/gdm/custom.conf” file to “false”:
-
-[daemon]
-TimedLoginEnable=false</fixtext>
-      <fix id="F-RHEL-07-010431_fix" />
-      <check system="C-RHEL-07-010431_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system does not allow guest logon to the system via a graphical user interface.
-
-Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
-
-Check for the value of the “AutomaticLoginEnable” in “/etc/gdm/custom.conf” file with the following command:
-
-# grep -i timedloginenable /etc/gdm/custom.conf
-TimedLoginEnable=false
-
-If the value of “TimedLoginEnable” is not set to “false”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010440">
-    <title>SRG-OS-000480-GPOS-00229</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010440_rule" severity="high" weight="10.0">
-      <version>RHEL-07-010440</version>
-      <title>The operating system must not allow empty passwords for SSH logon to the system.</title>
-      <description>&lt;VulnDiscussion&gt;Failure to restrict system access to authenticated users negatively impacts operating system 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-010440_fix">Configure the operating system to not allow empty passwords for SSH logon to the system.
-
-Edit the /etc/ssh/sshd_config file to uncomment or add the line for “PermitEmptyPasswords” keyword and set the value to “no”:
-
-PermitEmptyPasswords no</fixtext>
-      <fix id="F-RHEL-07-010440_fix" />
-      <check system="C-RHEL-07-010440_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system does not allow empty passwords to be used for SSH logon to the system.
-
-Check for the value of the PermitEmptyPasswords keyword with the following command:
-
-# grep -i permitemptypassword /etc/ssh/sshd_config
-PermitEmptyPasswords no
-
-If the “PermitEmptyPasswords” keyword is not set to “no”, is missing, or is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010441">
-    <title>SRG-OS-000480-GPOS-00229</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010441_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010441</version>
-      <title>The operating system must not allow users to override SSH environment variables.</title>
-      <description>&lt;VulnDiscussion&gt;Failure to restrict system access to authenticated users negatively impacts operating system 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-010441_fix">Configure the operating system to not allow users to override environment variables to the SSH daemon.
-
-Edit the /etc/ssh/sshd_config file to uncomment or add the line for “PermitUserEnvironment” keyword and set the value to “no”:
-
-PermitUserEnvironment no</fixtext>
-      <fix id="F-RHEL-07-010441_fix" />
-      <check system="C-RHEL-07-010441_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system does not allow users to override environment variables to the SSH daemon.
-
-Check for the value of the PermitUserEnvironment keyword with the following command:
-
-# grep -i permituserenvironment /etc/ssh/sshd_config
-PermitUserEnvironment no
-
-If the “PermitUserEnvironment” keyword is not set to “no”, is missing, or is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010442">
-    <title>SRG-OS-000480-GPOS-00229</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010442_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010442</version>
-      <title>The operating system must not allow a non-certificate trusted host SSH logon to the system.</title>
-      <description>&lt;VulnDiscussion&gt;Failure to restrict system access to authenticated users negatively impacts operating system 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-010442_fix">Configure the operating system to not allow a non-certificate trusted host SSH logon to the system.
-
-Edit the /etc/ssh/sshd_config file to uncomment or add the line for “HostbasedAuthentication” keyword and set the value to “no”:
-
-HostbasedAuthentication no</fixtext>
-      <fix id="F-RHEL-07-010442_fix" />
-      <check system="C-RHEL-07-010442_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system does not allow a non-certificate trusted host SSH logon to the system.
-
-Check for the value of the HostbasedAuthentication keyword with the following command:
-
-# grep -i hostbasedauthentication /etc/ssh/sshd_config
-HostbasedAuthentication no
-
-If the “HostbasedAuthentication” keyword is not set to “no”, is missing, or is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010460">
-    <title>SRG-OS-000080-GPOS-00048</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010460_rule" severity="high" weight="10.0">
-      <version>RHEL-07-010460</version>
-      <title>Systems with a Basic Input/Output System (BIOS) must require authentication upon booting into single-user and maintenance modes.</title>
-      <description>&lt;VulnDiscussion&gt;If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 7 and is designed to require a password to boot into single-user mode or make modifications to the boot menu.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000213</ident>
-      <fixtext fixref="F-RHEL-07-010460_fix">Configure the system to encrypt the boot password for root.
-
-Generate an encrypted grub2 password for root with the following command:
-
-Note: The hash generated is an example.
-
-# grub-mkpasswd-pbkdf2
-Enter Password:
-Reenter Password:
-PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45
-
-Using this hash, modify the “/etc/grub.d/10_linux” file with the following commands to add the password to the root entry:
-
-# cat &lt;&lt; EOF
-&gt; set superusers="root" password_pbkdf2 smithj grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45
-&gt; EOF
-
-Generate a new grub.conf file with the new password with the following commands:
-
-# grub2-mkconfig --output=/tmp/grub2.cfg
-# mv /tmp/grub2.cfg /boot/grub2/grub.cfgirement</fixtext>
-      <fix id="F-RHEL-07-010460_fix" />
-      <check system="C-RHEL-07-010460_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Check to see if an encrypted root password is set. On systems that use a BIOS, use the following command:
-
-# grep -i password /boot/grub2/grub.cfg
-password_pbkdf2 superusers-account password-hash
-
-If the root password entry does not begin with “password_pbkdf2”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010470">
-    <title>SRG-OS-000080-GPOS-00048</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010470_rule" severity="high" weight="10.0">
-      <version>RHEL-07-010470</version>
-      <title>Systems using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes.</title>
-      <description>&lt;VulnDiscussion&gt;If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 7 and is designed to require a password to boot into single-user mode or make modifications to the boot menu.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000213</ident>
-      <fixtext fixref="F-RHEL-07-010470_fix">Configure the system to encrypt the boot password for root.
-
-Generate an encrypted grub2 password for root with the following command:
-
-Note: The hash generated is an example.
-
-# grub-mkpasswd-pbkdf2
-Enter Password:
-Reenter Password:
-
-PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45
-
-Using this hash, modify the “/etc/grub.d/10_linux” file with the following commands to add the password to the root entry:
-
-# cat &lt;&lt; EOF
-&gt; set superusers="root" password_pbkdf2 smithj grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45
-&gt; EOF
-
-Generate a new grub.conf file with the new password with the following commands:
-
-# grub2-mkconfig --output=/tmp/grub2.cfg
-# mv /tmp/grub2.cfg /boot/efi/EFI/redhat/grub.cfg</fixtext>
-      <fix id="F-RHEL-07-010470_fix" />
-      <check system="C-RHEL-07-010470_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Check to see if an encrypted root password is set. On systems that use UEFI, use the following command:
-
-# grep -i password /boot/efi/EFI/redhat/grub.cfg
-password_pbkdf2 superusers-account password-hash
-
-If the root password entry does not begin with “password_pbkdf2”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010490">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010490_rule" severity="low" weight="10.0">
-      <version>RHEL-07-010490</version>
-      <title>Unnecessary default system accounts must be removed.</title>
-      <description>&lt;VulnDiscussion&gt;Default system accounts created at install time but never used by the system may inadvertently be configured for interactive logon. Vendor accounts and software may contain accounts that provide unauthorized access to the system. All accounts that are not used to support the system and application operation must be removed from 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-010490_fix">Remove unnecessary default accounts from the system by using the account management tool or manually editing the “/etc/password” and “/etc/shadow” files.</fixtext>
-      <fix id="F-RHEL-07-010490_fix" />
-      <check system="C-RHEL-07-010490_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify unnecessary default system accounts have been removed.
-
-Check the accounts that are on the system with the following command:
-
-# more /etc/passwd
-root:x:0:0:root:/root:/bin/bash
-bin:x:1:1:bin:/bin:/sbin/nologin
-daemon:x:2:2:daemon:/sbin:/sbin/nologin
-adm:x:3:4:adm:/var/adm:/sbin/nologin
-lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin
-sync:x:5:0:sync:/sbin:/bin/sync
-
-If unnecessary default accounts such as games or ftp exist in the “/etc/passwd” file, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-010500">
-    <title>SRG-OS-000104-GPOS-00051</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-010500_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-010500</version>
-      <title>The operating system must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users) using multi-factor authentication.</title>
-      <description>&lt;VulnDiscussion&gt;To assure 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-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000109-GPOS-00056, SRG-OS-000108-GPOS-00055, SRG-OS-000108-GPOS-00057, SRG-OS-000108-GPOS-00058&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000766</ident>
-      <fixtext fixref="F-RHEL-07-010500_fix">Configure the operating system to require individuals to be authenticated with a multi-factor authenticator.
-
-Enable smartcard logins with the following commands:
-
-# authconfig --enablesmartcard --smartcardaction=1 --update
-# authconfig --enablerequiresmartcard -update
-
-Modify the /etc/pam_pkcs11/pkcs11_eventmgr.conf file to uncomment the following line:
-
-#/usr/X11R6/bin/xscreensaver-command -lock
-
-Modify the /etc/pam_pkcs11/pam_pkcs11.conf file to use the cackey module if required.</fixtext>
-      <fix id="F-RHEL-07-010500_fix" />
-      <check system="C-RHEL-07-010500_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system requires multifactor authentication to uniquely identify organizational users using multi-factor authentication.
-
-Check to see if smartcard authentication is enforced on the system:
-
-# authconfig --test | grep -i smartcard
-
-The entry for use only smartcard for login may be enabled, and the smartcard module and smartcard removal actions must not be blank.
-
-If smartcard authentication is disabled or the smartcard and smartcard removal actions are blank, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020000">
-    <title>SRG-OS-000095-GPOS-00049</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020000_rule" severity="high" weight="10.0">
-      <version>RHEL-07-020000</version>
-      <title>The rsh-server package must not be 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.
-
-Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
-
-The rsh-server service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session and has very weak authentication.
-
-If a privileged user were to log on using this service, the privileged user password could be compromised.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000381</ident>
-      <fixtext fixref="F-RHEL-07-020000_fix">Configure the operating system to disable non-essential capabilities by removing the rsh-server package from the system with the following command:
-
-# yum remove rsh-server</fixtext>
-      <fix id="F-RHEL-07-020000_fix" />
-      <check system="C-RHEL-07-020000_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Check to see if the rsh-server package is installed with the following command:
-
-# yum list installed | grep rsh-server
-
-If the rsh-server package is installed, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020010">
-    <title>SRG-OS-000095-GPOS-00049</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020010_rule" severity="high" weight="10.0">
-      <version>RHEL-07-020010</version>
-      <title>The ypserv package must not be installed.</title>
-      <description>&lt;VulnDiscussion&gt;Removing the "ypserv" package decreases the risk of the accidental (or intentional) activation of NIS or NIS+ services.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000381</ident>
-      <fixtext fixref="F-RHEL-07-020010_fix">Configure the operating system to disable non-essential capabilities by removing the “ypserv” package from the system with the following command:
-
-# yum remove ypserv</fixtext>
-      <fix id="F-RHEL-07-020010_fix" />
-      <check system="C-RHEL-07-020010_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>The NIS service provides an unencrypted authentication service that does not provide for the confidentiality and integrity of user passwords or the remote session.
-
-Check to see if the “ypserve” package is installed with the following command:
-
-# yum list installed | grep ypserv
-
-If the “ypserv” package is installed, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020090">
-    <title>SRG-OS-000324-GPOS-00125</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020090_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020090</version>
-      <title>The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.</title>
-      <description>&lt;VulnDiscussion&gt;Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
-
-Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals who do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002165</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002235</ident>
-      <fixtext fixref="F-RHEL-07-020090_fix">Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
-
-Use the following command to map a new user to the sysdam_u role: 
-
-#semanage login -a -s sysadm_u &lt;username&gt;
-
-Use the following command to map an existing user to the sysdam_u role:
-
-#semanage login -m -s sysadm_u &lt;username&gt;
-
-Use the following command to map a new user to the staff_u role:
-
-#semanage login -a -s staff_u &lt;username&gt;
-
-Use the following command to map an existing user to the staff_u role:
-
-#semanage login -m -s staff_u &lt;username&gt;
-
-Use the following command to map a new user to the user_u role:
-
-# semanage login -a -s user_u &lt;username&gt;
-
-Use the following command to map an existing user to the user_u role:
-
-# semanage login -m -s user_u &lt;username&gt;</fixtext>
-      <fix id="F-RHEL-07-020090_fix" />
-      <check system="C-RHEL-07-020090_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
-
-Get a list of authorized users (other than system administrator and guest accounts) for the system.
-
-Check the list against the system by using the following command:
-
-# semanage login -l | more
-Login Name  SELinux User   MLS/MCS Range  Service
-__default__  user_u    s0-s0:c0.c1023   *
-root   unconfined_u   s0-s0:c0.c1023   *
-system_u  system_u   s0-s0:c0.c1023   *
-joe  staff_u   s0-s0:c0.c1023   *
-
-All administrators must be mapped to the sysadm_u or staff_u users with the appropriate domains (sysadm_t and staff_t).
-
-All authorized non-administrative users must be mapped to the user_u role or the appropriate domain (user_t).
-
-If they are not mapped in this way, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020130">
-    <title>SRG-OS-000363-GPOS-00150</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020130_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020130</version>
-      <title>A file integrity tool must verify the baseline operating system configuration at least weekly.</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 Information Management Officer (IMO)/Information System Security Officer (ISSO) and System Administrators (SAs) must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001744</ident>
-      <fixtext fixref="F-RHEL-07-020130_fix">Configure the file integrity tool to automatically run on the system at least weekly. The following example output is generic. It will set cron to run AIDE daily, but other file integrity tools may be used:
-
-# cat /etc/cron.daily/aide 
-0 0 * * * /usr/sbin/aide --check | /bin/mail -s "aide integrity check run for &lt;system name&gt;" root@sysname.mil</fixtext>
-      <fix id="F-RHEL-07-020130_fix" />
-      <check system="C-RHEL-07-020130_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system routinely checks that baseline configuration changes are not performed in an authorized manner.
-
-Note: A file integrity tool other than Advanced Intrusion Detection Environment (AIDE) may be used, but the tool must be executed at least once per week.
-
-Check for the presence of a cron job running daily or weekly on the system that executes AIDE daily to scan for changes to the system baseline. The command used in the example will use a daily occurrence.
-
-Check the /etc/cron.daily subdirectory for a crontab file controlling the execution of the file integrity application. For example, if AIDE is installed on the system, use the following command:
-
-# ls -al /etc/cron.* | grep aide
--rwxr-xr-x  1 root root        29 Nov  22  2015 aide
-
-If the file integrity application is not executed on the system with the required frequency, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020140">
-    <title>SRG-OS-000363-GPOS-00150</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020140_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020140</version>
-      <title>Designated personnel must be notified if baseline configurations are changed in an unauthorized manner.</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 Information Management Officer (IMO)/Information System Security Officer (ISSO) and System Administrators (SAs) must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001744</ident>
-      <fixtext fixref="F-RHEL-07-020140_fix">Configure the operating system to notify designated personnel if baseline configurations are changed in an unauthorized manner. The AIDE tool can be configured to email designated personnel through the use of the cron system.  
-
-The following example output is generic. It will set cron to run AIDE daily and to send email at the completion of the analysis. 
-
-# more /etc/cron.daily/aide
-0 0 * * * /usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily aide integrity check run" root@sysname.mil</fixtext>
-      <fix id="F-RHEL-07-020140_fix" />
-      <check system="C-RHEL-07-020140_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system notifies designated personnel if baseline configurations are changed in an unauthorized manner.
-
-Note: A file integrity tool other than Advanced Intrusion Detection Environment (AIDE) may be used, but the tool must be executed and notify specified individuals via email or an alert.
-
-Check for the presence of a cron job running routinely on the system that executes AIDE to scan for changes to the system baseline. The commands used in the example will use a daily occurrence.
-
-Check the /etc/cron.daily subdirectory for a crontab file controlling the execution of the file integrity application. For example, if AIDE is installed on the system, use the following commands:
-
-# ls -al /etc/cron.daily | grep aide
--rwxr-xr-x  1 root root        32 Jul  1  2011 aide
-
-AIDE does not have a configuration that will send a notification, so the cron job uses the mail application on the system to email the results of the file integrity run as in the following example:
-
-# more /etc/cron.daily/aide
-0 0 * * * /usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily aide integrity check run" root@sysname.mil
-
-If the file integrity application does not notify designated personnel of changes, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020150">
-    <title>SRG-OS-000366-GPOS-00153</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020150_rule" severity="high" weight="10.0">
-      <version>RHEL-07-020150</version>
-      <title>The operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization.</title>
-      <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 verifies the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001749</ident>
-      <fixtext fixref="F-RHEL-07-020150_fix">Configure the operating system to verify the signature of packages from a repository prior to install by setting the following option in the /etc/yum.conf file:
-
-gpgcheck=1</fixtext>
-      <fix id="F-RHEL-07-020150_fix" />
-      <check system="C-RHEL-07-020150_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components from a repository without verification that they have been digitally signed using a certificate that is recognized and approved by the organization.
-
-Check that yum verifies the signature of packages from a repository prior to install with the following command:
-
-# grep gpgcheck /etc/yum.conf
-gpgcheck=1
-
-If "gpgcheck" is not set to ”1”, or if options are missing or commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020151">
-    <title>SRG-OS-000366-GPOS-00153</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020151_rule" severity="high" weight="10.0">
-      <version>RHEL-07-020151</version>
-      <title>The operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization.</title>
-      <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 verifies the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001749</ident>
-      <fixtext fixref="F-RHEL-07-020151_fix">Configure the operating system to verify the signature of local packages prior to install by setting the following option in the /etc/yum.conf file:
-
-localpkg_gpgcheck=1</fixtext>
-      <fix id="F-RHEL-07-020151_fix" />
-      <check system="C-RHEL-07-020151_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components of local packages without verification that they have been digitally signed using a certificate that is recognized and approved by the organization.
-
-Check that yum verifies the signature of local packages prior to install with the following command:
-
-# grep localpkg_gpgcheck /etc/yum.conf
-localpkg_gpgcheck=1
-
-If "localpkg_gpgcheck" is not set to ”1”, or if options are missing or commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020152">
-    <title>SRG-OS-000366-GPOS-00153</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020152_rule" severity="high" weight="10.0">
-      <version>RHEL-07-020152</version>
-      <title>The operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of packages without verification of the repository metadata.</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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001749</ident>
-      <fixtext fixref="F-RHEL-07-020152_fix">Configure the operating system to verify the repository metadata by setting the following options in the /etc/yum.conf file:
-
-repo_gpgcheck=1</fixtext>
-      <fix id="F-RHEL-07-020152_fix" />
-      <check system="C-RHEL-07-020152_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components of local packages without verification of the repository metadata.
-
-Check that yum verifies the package metadata prior to install with the following command:
-
-# grep repo_gpgcheck /etc/yum.conf
-repo_gpgcheck=1
-
-If "repo_gpgcheck" is not set to ”1”, or if options are missing or commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020160">
-    <title>SRG-OS-000114-GPOS-00059</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020160_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020160</version>
-      <title>USB mass storage must be disabled.</title>
-      <description>&lt;VulnDiscussion&gt;USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity.
-
-Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000778</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001958</ident>
-      <fixtext fixref="F-RHEL-07-020160_fix">Configure the operating system to disable the ability to use USB mass storage devices.
-
-Create a file under /etc/modprobe.d with the following command:
-
-#touch /etc/modprobe.d/nousbstorage
-
-Add the following line to the created file:
-
-install usb-storage /bin/true</fixtext>
-      <fix id="F-RHEL-07-020160_fix" />
-      <check system="C-RHEL-07-020160_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>If there is an HBSS with a Device Control Module and a Data Loss Prevention mechanism, this requirement is not applicable.
-
-Verify the operating system disables the ability to use USB mass storage devices.
-
-Check to see if USB mass storage is disabled with the following command:
-
-#grep -i usb-storage /etc/modprobe.d/*
-
-install usb-storage /bin/true
-
-If the command does not return any output, and use of USB storage devices is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020161">
-    <title>SRG-OS-000114-GPOS-00059</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020161_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020161</version>
-      <title>File system automounter must be disabled unless required.</title>
-      <description>&lt;VulnDiscussion&gt;Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity.
-
-Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000778</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001958</ident>
-      <fixtext fixref="F-RHEL-07-020161_fix">Configure the operating system to disable the ability to automount devices.
-
-Turn off the automount service with the following command:
-
-# systemctl disable autofs
-
-If “autofs” is required for Network File System (NFS), it must be documented with the ISSO.</fixtext>
-      <fix id="F-RHEL-07-020161_fix" />
-      <check system="C-RHEL-07-020161_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system disables the ability to automount devices.
-
-Check to see if automounter service is active with the following command:
-
-# systemctl status autofs
-autofs.service - Automounts filesystems on demand
-   Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled)
-   Active: inactive (dead)
-
-If the “autofs” status is set to “active” and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020170">
-    <title>SRG-OS-000405-GPOS-00184</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020170_rule" severity="high" weight="10.0">
-      <version>RHEL-07-020170</version>
-      <title>Operating systems handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.</title>
-      <description>&lt;VulnDiscussion&gt;Selection of a cryptographic mechanism is based on the need to protect the integrity and confidentiality of sensitive 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). This requirement is applicable if the organization determines that its sensitive information is to be protected at the storage device level.
-
-Satisfies: SRG-OS-000405-GPOS-00184, SRG-OS-000185-GPOS-00079&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002476</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001199</ident>
-      <fixtext fixref="F-RHEL-07-020170_fix">Configure the operating system to implement cryptographic mechanisms to prevent unauthorized disclosure of all sensitive information at rest on operating system storage devices. This must be performed during the creation of the operating system as attempting to encrypt the system partitions afterward is not a trivial operation.</fixtext>
-      <fix id="F-RHEL-07-020170_fix" />
-      <check system="C-RHEL-07-020170_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system, if handling data that requires protection to prevent the unauthorized discloser or modification of information at rest, is using disk encryption. 
-
-Note: If the organization determines that no data resident on the system requires protection, or that sensitive data is being protected through an application encryption mechanism, this requirement is Not Applicable.
-
-Check the system partitions to determine if they are all encrypted with the following command:
-
-# blkid
-/dev/sda1: UUID=" ab12c3de-4f56-789a-8f33-3850cc8ce3a2
-" TYPE="crypto_LUKS"
-/dev/sda2: UUID=" bc98d7ef-6g54-321h-1d24-9870de2ge1a2
-" TYPE="crypto_LUKS"
-
-Pseudo-file systems, such as /proc, /sys, and tmpfs, are not required to use disk encryption and are not a finding. 
-
-If any other partitions do not have a type of “crypto_LUKS”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020200">
-    <title>SRG-OS-000437-GPOS-00194</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020200_rule" severity="low" weight="10.0">
-      <version>RHEL-07-020200</version>
-      <title>The operating system must remove 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002617</ident>
-      <fixtext fixref="F-RHEL-07-020200_fix">Configure the operating system to remove all software components after updated versions have been installed.
-
-Set the “clean_requirements_on_remove” option to “1” in the /etc/yum.conf file:
-
-clean_requirements_on_remove=1</fixtext>
-      <fix id="F-RHEL-07-020200_fix" />
-      <check system="C-RHEL-07-020200_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system removes all software components after updated versions have been installed.
-
-Check if yum is configured to remove unneeded packages with the following command:
-
-# grep -i clean_requirements_on_remove /etc/yum.conf
-clean_requirements_on_remove=1
-
-If “clean_requirements_on_remove” is not set to “1”, “True”, or “yes”, or is not set in /etc/yum.conf, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020210">
-    <title>SRG-OS-000445-GPOS-00199</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020210_rule" severity="high" weight="10.0">
-      <version>RHEL-07-020210</version>
-      <title>The operating system must enable SELinux.</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 operating systems 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002165</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002696</ident>
-      <fixtext fixref="F-RHEL-07-020210_fix">Configure the operating system to verify correct operation of all security functions.
-
-Set the “Selinux” status and the “enforcing” mode by modifying the /etc/selinux/config file to have the following line:
-
-SELINUX=enforcing
-
-A reboot is required for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-020210_fix" />
-      <check system="C-RHEL-07-020210_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system verifies correct operation of all security functions.
-
-Check if SELinux is active and in enforcing mode with the following command:
-
-# getenforce
-Enforcing
-
-If the “SELinux” mode is not set to “Enforcing”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020211">
-    <title>SRG-OS-000445-GPOS-00199</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020211_rule" severity="high" weight="10.0">
-      <version>RHEL-07-020211</version>
-      <title>The operating system must enable the SELinux targeted policy.</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 operating systems 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002165</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002696</ident>
-      <fixtext fixref="F-RHEL-07-020211_fix">Configure the operating system to verify correct operation of all security functions.
-
-Set the “Selinuxtype” to the “targeted” policy by modifying the /etc/selinux/config file to have the following line:
-
-SELINUXTYPE=targeted
-
-A reboot is required for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-020211_fix" />
-      <check system="C-RHEL-07-020211_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system verifies correct operation of all security functions.
-
-Check if SELinux is active and is enforcing the targeted policy with the following command:
-
-# sestatus
-SELinux status:                 enabled
-SELinuxfs mount:                /selinux
-Current mode:                   enforcing
-Mode from config file:          enforcing
-Policy version:                 24
-Policy from config file:        targeted
-
-If the “Policy from config file”  not set to “targeted”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020220">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020220_rule" severity="high" weight="10.0">
-      <version>RHEL-07-020220</version>
-      <title>The x86 Ctrl-Alt-Delete key sequence must be disabled.</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 GNOME 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020220_fix">Configure the system to disable the Ctrl-Alt_Delete sequence for the command line with the following command:
-
-# systemctl mask ctrl-alt-del.target
-
-If Gnome is active on the system, create a database to contain the system-wide setting (if it does not already exist) with the following command: 
-
-# cat /etc/dconf/db/local.d/00-disable-CAD 
-
-Add the setting to disable the Ctrl-Alt_Delete sequence for Gnome:
-
-[org/gnome/settings-daemon/plugins/media-keys]
-logout=’’</fixtext>
-      <fix id="F-RHEL-07-020220_fix" />
-      <check system="C-RHEL-07-020220_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system is not configured to reboot the system when Ctrl-Alt-Delete is pressed.
-
-Check that the ctrl-alt-del.service is not active with the following command:
-
-# systemctl status ctrl-alt-del.service
-reboot.target - Reboot
-   Loaded: loaded (/usr/lib/systemd/system/reboot.target; disabled)
-   Active: inactive (dead)
-     Docs: man:systemd.special(7)
-
-If the ctrl-alt-del.service is active , this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020230">
-    <title>SRG-OS-000480-GPOS-00228</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020230_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020230</version>
-      <title>The operating system must define default permissions for all authenticated users in such a way that the user can only read and modify their own files.</title>
-      <description>&lt;VulnDiscussion&gt;Setting the most restrictive default permissions ensures that when new accounts are created, they 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020230_fix">Configure the operating system to define default permissions for all authenticated users in such a way that the user can only read and modify their own files.
-
-Add or edit the line for the “UMASK” parameter in “/etc/login.defs” file to “077”:
-
-UMASK  077</fixtext>
-      <fix id="F-RHEL-07-020230_fix" />
-      <check system="C-RHEL-07-020230_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system defines default permissions for all authenticated users in such a way that the user can only read and modify their own files.
-
-Check for the value of the “UMASK” parameter in “/etc/login.defs” file with the following command:
-
-Note: If the value of the “UMASK” parameter is set to “000” in “/etc/login.defs” file, the Severity is raised to a CAT I.
-
-# grep -i umask /etc/login.defs
-UMASK  077
-
-If the value for the “UMASK” parameter is not “077”, or the “UMASK” parameter is missing or is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020240">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020240_rule" severity="high" weight="10.0">
-      <version>RHEL-07-020240</version>
-      <title>The operating system must be a supported release.</title>
-      <description>&lt;VulnDiscussion&gt;An operating system release is considered "supported" if the vendor continues to provide security patches for the product. With an unsupported release, it will not be possible to resolve security issues discovered in the system software.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020240_fix">Upgrade to a supported version of the operating system.</fixtext>
-      <fix id="F-RHEL-07-020240_fix" />
-      <check system="C-RHEL-07-020240_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Severity Override Guidance: 
-
-Check the version of the operating system with the following command:
-
-# cat /etc/redhat-release
-
-Red Hat Enterprise Linux Server release 7.2 (Maipo)
-Current End of Life for RHEL 7 is June 30, 2024.
-
-If the release is not supported by the vendor, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020250">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020250_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020250</version>
-      <title>System security patches and updates must be installed and up to date.</title>
-      <description>&lt;VulnDiscussion&gt;Timely patching is critical for maintaining the operational availability, confidentiality, and integrity of information technology (IT) systems. However, failure to keep operating system and application software patched is a common mistake made by IT professionals. New patches are released daily, and it is often difficult for even experienced system administrators to keep abreast of all the new patches. When new weaknesses in an operating system exist, patches are usually made available by the vendor to resolve the problems. If the most recent security patches and updates are not installed, unauthorized users may take advantage of weaknesses in the unpatched software. The lack of prompt attention to patching could result in a system compromise.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;Control value is 30 days.&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020250_fix">Install the operating system patches or updated packages available from Red Hat within 30 days or sooner as local policy dictates.</fixtext>
-      <fix id="F-RHEL-07-020250_fix" />
-      <check system="C-RHEL-07-020250_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system security patches and updates are installed and up to date. Updates are required to be applied with a frequency determined by the site or Program Management Office (PMO). 
-
-Obtain the list of available package security updates from Red Hat. The URL for updates is https://rhn.redhat.com/errata/. It is important to note that updates provided by Red Hat may not be present on the system if the underlying packages are not installed.
-
-Check that the available package security updates have been installed on the system with the following command:
-
-# yum history list | more
-Loaded plugins: langpacks, product-id, subscription-manager
-ID     | Command line             | Date and time    | Action(s)      | Altered
--------------------------------------------------------------------------------
-    70 | install aide             | 2016-05-05 10:58 | Install        |    1   
-    69 | update -y                | 2016-05-04 14:34 | Update         |   18 EE
-    68 | install vlc              | 2016-04-21 17:12 | Install        |   21   
-    67 | update -y                | 2016-04-21 17:04 | Update         |    7 EE
-    66 | update -y                | 2016-04-15 16:47 | E, I, U        |   84 EE
-
-If package updates have not been performed on the system within the timeframe that the site/program documentation requires, this is a finding. 
-
-Typical update frequency may be overridden by information assurance vulnerability alert (IAVA) notifications from CYBERCOM.
-
-If the operating system is in non-compliance with the IAVM process, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020290">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020290_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020290</version>
-      <title>The system must not have unnecessary accounts.</title>
-      <description>&lt;VulnDiscussion&gt;Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for individuals not requiring access to the system and application accounts for applications not installed 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020290_fix">Configure the system so all accounts on the system are assigned to an active system, application, or user account. Remove accounts that do not support approved system activities or that allow for a normal user to perform administrative-level actions. Document all authorized accounts on the system.</fixtext>
-      <fix id="F-RHEL-07-020290_fix" />
-      <check system="C-RHEL-07-020290_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify all accounts on the system are assigned to an active system, application, or user account.
-
-Obtain the list of authorized system accounts from the Information System Security Officer (ISSO).
-
-Check the system accounts on the system with the following command:
-
-# more /etc/passwd
-root:x:0:0:root:/root:/bin/bash
-bin:x:1:1:bin:/bin:/sbin/nologin
-daemon:x:2:2:daemon:/sbin:/sbin/nologin
-sync:x:5:0:sync:/sbin:/bin/sync
-shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown
-halt:x:7:0:halt:/sbin:/sbin/halt
-games:x:12:100:games:/usr/games:/sbin/nologin
-gopher:x:13:30:gopher:/var/gopher:/sbin/nologin
-
-Accounts such as “games” and “gopher” are not authorized accounts as they do not support authorized system functions. 
-
-If the accounts on the system do not match the provided documentation, or accounts that do not support an authorized system function are present, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020300">
-    <title>SRG-OS-000104-GPOS-00051</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020300_rule" severity="low" weight="10.0">
-      <version>RHEL-07-020300</version>
-      <title>All Group Identifiers (GIDs) referenced in the /etc/passwd file must be defined in the /etc/group file.</title>
-      <description>&lt;VulnDiscussion&gt;If a user is assigned the GID of a group not existing on the system, and a group with the GID is subsequently created, the user may have unintended rights to any files associated with the group.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000764</ident>
-      <fixtext fixref="F-RHEL-07-020300_fix">Configure the system to define all GIDs found in the “/etc/passwd” file by modifying the “/etc/group” file to add any non-existent group referenced in the “/etc/passwd” file, or change the GIDs referenced in the “/etc/passwd” file to a group that exists in “/etc/group”.</fixtext>
-      <fix id="F-RHEL-07-020300_fix" />
-      <check system="C-RHEL-07-020300_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify all GIDs referenced in the “/etc/passwd” file are defined in the “/etc/group” file.
-
-Check that all referenced GIDs exist with the following command:
-
-# pwck -r
-
-If GIDs referenced in “/etc/passwd” file are returned as not defined in “/etc/group” file, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020310">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020310_rule" severity="high" weight="10.0">
-      <version>RHEL-07-020310</version>
-      <title>The root account must be the only account having unrestricted access to the system.</title>
-      <description>&lt;VulnDiscussion&gt;If an account other than root also has a User Identifier (UID) of “0”, it has root authority, giving that account unrestricted access to the entire operating system. Multiple accounts with a UID of “0” afford an opportunity for potential intruders to guess a password for a privileged account.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020310_fix">Change the UID of any account on the system, other than root, that has a UID of “0”. 
-
-If the account is associated with system commands or applications, the UID should be changed to one greater than “0” but less than “1000”. Otherwise, assign a UID of greater than “1000” that has not already been assigned.</fixtext>
-      <fix id="F-RHEL-07-020310_fix" />
-      <check system="C-RHEL-07-020310_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Check the system for duplicate UID “0” assignments with the following command:
-
-# awk -F: '$3 == 0 {print $1}' /etc/passwd
-
-If any accounts other than root have a UID of “0”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020360">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020360_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020360</version>
-      <title>All files and directories must have a valid owner.</title>
-      <description>&lt;VulnDiscussion&gt;Unowned files and directories may be unintentionally inherited if a user is assigned the same User Identifier “UID” as the UID of the un-owned 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002165</ident>
-      <fixtext fixref="F-RHEL-07-020360_fix">Either remove all files and directories from the system that do not have a valid user, or assign a valid user to all unowned files and directories on the system with the chown command:
-
-# chown &lt;user&gt; &lt;file&gt;</fixtext>
-      <fix id="F-RHEL-07-020360_fix" />
-      <check system="C-RHEL-07-020360_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify all files and directories on the system have a valid owner.
-
-Check the owner of all files and directories with the following command:
-
-# find / -fstype local -xdev -nouser
-
-If any files on the system do not have an assigned owner, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020370">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020370_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020370</version>
-      <title>All files and directories must have a valid group owner.</title>
-      <description>&lt;VulnDiscussion&gt;Files without a valid group owner may be unintentionally inherited if a group is assigned the same Group Identifier (GID) as the GID of the files without a valid group owner.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002165</ident>
-      <fixtext fixref="F-RHEL-07-020370_fix">Either remove all files and directories from the system that do not have a valid group, or assign a valid group to all files and directories on the system with the chgrp command:
-
-# chgrp &lt;group&gt; &lt;file&gt;</fixtext>
-      <fix id="F-RHEL-07-020370_fix" />
-      <check system="C-RHEL-07-020370_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify all files and directories on the system have a valid group.
-
-Check the owner of all files and directories with the following command:
-
-# find / -fstype local -xdev -nogroup
-
-If any files on the system do not have an assigned group, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020620">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020620_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020620</version>
-      <title>All local interactive users must have a home directory assigned in the /etc/passwd file.</title>
-      <description>&lt;VulnDiscussion&gt;If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020620_fix">Assign home directories to all local interactive users that currently do not have a home directory assigned.</fixtext>
-      <fix id="F-RHEL-07-020620_fix" />
-      <check system="C-RHEL-07-020620_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify local interactive users on the system have a home directory assigned.
-
-Check for missing local interactive user home directories with the following command:
-
-# pwck -r
-user 'lp': directory '/var/spool/lpd' does not exist
-user 'news': directory '/var/spool/news' does not exist
-user 'uucp': directory '/var/spool/uucp' does not exist
-user 'smithj': directory '/home/smithj' does not exist
-
-Ask the System Administrator (SA) if any users found without home directories are local interactive users. If the SA is unable to provide a response, check for users with a User Identifier (UID) of 1000 or greater with the following command:
-
-# cut -d: -f 1,3 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$"
-
-If any interactive users do not have a home directory assigned, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020630">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020630_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020630</version>
-      <title>All local interactive user accounts, upon creation, must be assigned a home directory.</title>
-      <description>&lt;VulnDiscussion&gt;If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020630_fix">Configure the operating system to assign home directories to all new local interactive users by setting the “CREATE_HOME” parameter in “/etc/login.defs” to “yes” as follows.
-
-CREATE_HOME yes</fixtext>
-      <fix id="F-RHEL-07-020630_fix" />
-      <check system="C-RHEL-07-020630_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify all local interactive users on the system are assigned a home directory upon creation.
-
-Check to see if the system is configured to create home directories for local interactive users with the following command:
-
-# grep -i create_home /etc/login.defs
-CREATE_HOME yes
-
-If the value for “CREATE_HOME” parameter is not set to "yes", the line is missing, or the line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020640">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020640_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020640</version>
-      <title>All local interactive user home directories defined in the /etc/passwd file must exist.</title>
-      <description>&lt;VulnDiscussion&gt;If a local interactive user has a home directory defined that does not exist, the user may be given access to the / directory as the current working directory upon logon. This could create a Denial of Service because the user would not be able to access their logon configuration files, and it may give them visibility to system files they normally would not be able to 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020640_fix">Create home directories to all local interactive users that currently do not have a home directory assigned. Use the following commands to create the user home directory assigned in “/etc/ passwd”:
-
-Note: The example will be for the user smithj, who has a home directory of “/home/smithj”, a UID of “smithj”, and a Group Identifier (GID) of “users assigned” in “/etc/passwd”.
-
-# mkdir /home/smithj 
-# chown smithj /home/smithj
-# chgrp users /home/smithj
-# chmod 0750 /home/smithj</fixtext>
-      <fix id="F-RHEL-07-020640_fix" />
-      <check system="C-RHEL-07-020640_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the assigned home directory of all local interactive users on the system exists.
-
-Check the home directory assignment for all local interactive non-privileged users on the system with the following command:
-
-# cut -d: -f 1,3 /etc/passwd | egrep ":[1-9][0-9]{2}$|:[0-9]{1,2}$"
-smithj /home/smithj
-
-Note: This may miss interactive users that have been assigned a privileged UID. Evidence of interactive use may be obtained from a number of log files containing system logon information.
-
-Check that all referenced home directories exist with the following command:
-
-# pwck -r
-user 'smithj': directory '/home/smithj' does not exist
-
-If any home directories referenced in “/etc/passwd” are returned as not defined, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020650">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020650_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020650</version>
-      <title>All local interactive user home directories must have mode 0750 or less permissive.</title>
-      <description>&lt;VulnDiscussion&gt;Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020650_fix">Change the mode of interactive user’s home directories to “0750”. To change the mode of a local interactive user’s home directory, use the following command:
-
-Note: The example will be for the user “smithj”.
-
-# chmod 0750 /home/smithj</fixtext>
-      <fix id="F-RHEL-07-020650_fix" />
-      <check system="C-RHEL-07-020650_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the assigned home directory of all local interactive users has a mode of “0750” or less permissive.
-
-Check the home directory assignment for all non-privileged users on the system with the following command:
-
-# cut -d: -f 1,3 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$"
-smithj /home/smithj
-
-Note: This may miss interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information.
-
-Check the mode on all local interactive users’ home directories with the following command:
-
-# ls -al &lt;users home directory&gt;
-drwxr-x---  1 smithj users        860 Nov 28 06:43 smithj
-
-If home directories referenced in “/etc/passwd” do not have a mode of “0750” or less permissive, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020660">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020660_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020660</version>
-      <title>All local interactive user home directories must be owned by their respective users.</title>
-      <description>&lt;VulnDiscussion&gt;If a local interactive user does not own their home directory, unauthorized users could access or modify the user's files, and the users may not be able to access their own 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020660_fix">Change the owner of a local interactive user’s home directories to that owner. To change the owner of a local interactive user’s home directory use the following command:
-
-Note: The example will be for the user smithj, who has a home directory of “/home/smithj”.
-
-# chown smithj /home/smithj</fixtext>
-      <fix id="F-RHEL-07-020660_fix" />
-      <check system="C-RHEL-07-020660_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the assigned home directory of all local interactive users is owned by that user.
-
-Check the home directory assignment for all non-privileged users on the system with the following command:
-
-# cut -d: -f 1,3 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$"
-smithj /home/smithj
-
-Note: This may miss local interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information.
-
-Check the owner of all local interactive users home directories with the following command:
-
-# ls -al &lt;users home directory&gt;
-drwxr-x---  1 smithj users        860 Nov 28 06:43 smithj
-
-If user home directory referenced in “/etc/passwd” is not owned by that user, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020670">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020670_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020670</version>
-      <title>All local interactive user home directories must be group-owned by the home directory owners primary group.</title>
-      <description>&lt;VulnDiscussion&gt;If the Group Identifier (GID) of a local interactive user’s home directory is not the same as the primary GID of the user, this would allow unauthorized access to the user’s files, and users that share the same group may not be able to access files that they legitimately should.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020670_fix">Change the group owner of a local interactive user’s home directory to the group found in “/etc/passwd”. To change the group owner of a local interactive user’s home directory, use the following command:
-
-Note: The example will be for the user “smithj”, who has a home directory of “/home/smithj”, and has a primary group of users.
-
-# chgrp users /home/smithj</fixtext>
-      <fix id="F-RHEL-07-020670_fix" />
-      <check system="C-RHEL-07-020670_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the assigned home directory of all local interactive users is group-owned by that user’s primary GID.
-
-Check the home directory assignment for all non-privileged users on the system with the following command:
-
-# cut -d: -f 1,3,4 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$"
-smithj /home/smithj 250
-
-# grep 250 /etc/group
-users:x:250:smithj,jonesj,jacksons
-
-Note: This may miss local interactive users that have been assigned a privileged UID. Evidence of interactive use may be obtained from a number of log files containing system logon information.
-
-Check the group owner of all local interactive users’ home directories with the following command:
-
-# ls -al &lt;users home directory&gt;
-drwxr-x---  1 smithj users        860 Nov 28 06:43 smithj
-
-If the user home directory referenced in “/etc/passwd” is not group-owned by that user’s primary GID, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020680">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020680_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020680</version>
-      <title>All files and directories contained in local interactive user home directories must be owned by the owner of the home directory.</title>
-      <description>&lt;VulnDiscussion&gt;If local interactive users do not own the files in their directories, unauthorized users may be able to access them. Additionally, if files are not owned by the user, this could be an indication of system compromise.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020680_fix">Change the owner of a local interactive user’s files and rectories to that owner. To change the owner of a local interactive user’s files and directories, use the following command:
-
-Note: The example will be for the user smithj, who has a home directory of “/home/smithj”.
-
-# chown smithj /home/smithj/&lt;file or directory&gt;</fixtext>
-      <fix id="F-RHEL-07-020680_fix" />
-      <check system="C-RHEL-07-020680_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify all files and directories in a local interactive user’s home directory are owned by the user.
-
-Check the owner of all files and directories in a local interactive user’s home directory with the following command:
-
-# ls -lLR /&lt;home directory path&gt;/&lt;users home directory&gt;/
-/home/smithj
--rw-r--r-- 1 smithj smithj  18 Mar  5 17:06 file1
--rw-r--r-- 1 smithj smithj 193 Mar  5 17:06 file2
--rw-r--r-- 1 smithj smithj 231 Mar  5 17:06 file3
-
-If any files are found with an owner different than the home directory user, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020690">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020690_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020690</version>
-      <title>All files and directories contained in local interactive user home directories must be group-owned by a group of which the home directory owner is a member.</title>
-      <description>&lt;VulnDiscussion&gt;If a local interactive user’s files are group-owned by a group of which the user is not a member, unintended users may be able to access them.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020690_fix">Change the group of a local interactive user’s files and directories to a group that the interactive user is a member of. To change the group owner of a local interactive user’s files and directories, use the following command:
-
-Note: The example will be for the user smithj, who has a home directory of “/home/smithj” and is a member of the users group.
-
-# chgrp users /home/smithj/&lt;file&gt;</fixtext>
-      <fix id="F-RHEL-07-020690_fix" />
-      <check system="C-RHEL-07-020690_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify all files and directories in a local interactive user home directory are group-owned by a group the user is a member of.
-
-Check the group owner of all files and directories in a local interactive user’s home directory with the following command:
-
-Note: The example will be for the user “smithj”, who has a home directory of “/home/smithj/home/smithj”.
-
-# ls -lLR /&lt;home directory&gt;/&lt;users home directory&gt;/
--rw-r--r-- 1 smithj smithj  18 Mar  5 17:06 file1
--rw-r--r-- 1 smithj smithj 193 Mar  5 17:06 file2
--rw-r--r-- 1 smithj sa        231 Mar  5 17:06 file3
-
-If any files are found with an owner different than the group home directory user, check to see if the user is a member of that group with the following command:
-
-# grep smithj /etc/group
-sa:x:100:juan,shelley,bob,smithj 
-smithj:x:521:smithj
-
-If the user is not a member of a group that group owns file(s) in a local interactive user’s home directory, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020700">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020700_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020700</version>
-      <title>All files and directories contained in local interactive user home directories must have mode 0750 or less permissive.</title>
-      <description>&lt;VulnDiscussion&gt;If a local interactive user files have excessive permissions, unintended users may be able to access or modify them.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020700_fix">Set the mode on files and directories in the local interactive user home directory with the following command:
-
-# chmod 0750  /&lt;home directory&gt;/&lt;users home directory&gt;/&lt;file&gt;</fixtext>
-      <fix id="F-RHEL-07-020700_fix" />
-      <check system="C-RHEL-07-020700_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify all files and directories contained in a local interactive user home directory, excluding local initialization files, have a mode of “0750”.
-
-Check the mode of all non-initialization files in a local interactive user home directory with the following command:
-
-Files that begin with a “.” are excluded from this requirement.
-
-Note: The example will be for the user “smithj”, who has a home directory of “/home/smithj/home/smithj”
-
-# ls -lLR /&lt;home directory&gt;/&lt;users home directory&gt;/
--rwxr-x--- 1 smithj smithj  18 Mar  5 17:06 file1
--rwxr----- 1 smithj smithj 193 Mar  5 17:06 file2
--rw-r-x--- 1 smithj sa        231 Mar  5 17:06 file3
-
-If any files are found with a mode more permissive than “0750”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020840">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020840_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020840</version>
-      <title>All local initialization files for interactive users must be owned by the home directory user or root.</title>
-      <description>&lt;VulnDiscussion&gt;Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020840_fix">Set the owner of the local initialization files for interactive users to either the directory owner or root with the following command:
-
-Note: The example will be for the smithj user, who has a home directory of “/home/smithj”.
-
-# chown smithj /home/smithj/.*</fixtext>
-      <fix id="F-RHEL-07-020840_fix" />
-      <check system="C-RHEL-07-020840_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify all local initialization files for interactive users are owned by the home directory user or root.
-
-Check the owner on all local initialization files with the following command:
-
-Note: The example will be for the “smithj” user, who has a home directory of “/home/smithj”.
-
-# ls -al /home/smithj/.* | more
--rwxr-xr-x  1 smithj users        896 Mar 10  2011 .bash_profile
--rwxr-xr-x  1 smithj users        497 Jan  6  2007 .login
--rwxr-xr-x  1 smithj users        886 Jan  6  2007 .profile
-
-If any file that sets a local interactive user’s environment variables to override the system is not owned by the home directory owner or root, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020850">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020850_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020850</version>
-      <title>Local initialization files for local interactive users must be group-owned by the users primary group or root.</title>
-      <description>&lt;VulnDiscussion&gt;Local initialization files for interactive users are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020850_fix">Change the group owner of a local interactive user’s files to the group found in “/etc/passwd” for the user. To change the group owner of a local interactive user home directory, use the following command:
-
-Note: The example will be for the user smithj, who has a home directory of “/home/smithj”, and has a primary group of users.
-
-# chgrp users /home/smithj/&lt;file&gt;</fixtext>
-      <fix id="F-RHEL-07-020850_fix" />
-      <check system="C-RHEL-07-020850_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the local initialization files of all local interactive users are group-owned by that user’s primary Group Identifier (GID).
-
-Check the home directory assignment for all non-privileged users on the system with the following command:
-
-Note: The example will be for the smithj user, who has a home directory of “/home/smithj” and a primary group of users.
-
-# cut -d: -f 1,3,4 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$"
-smithj /home/smithj 250
-
-# grep 250 /etc/group
-users:x:250:smithj,jonesj,jacksons 
-
-Note: This may miss interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information.
-
-Check the group owner of all local interactive users’ initialization files with the following command:
-
-# ls -al /home/smithj/.*
--rwxr-xr-x  1 smithj users        896 Mar 10  2011 .profile
--rwxr-xr-x  1 smithj users        497 Jan  6  2007 .login
--rwxr-xr-x  1 smithj users        886 Jan  6  2007 .something
-
-If all local interactive users’ initialization files are not group-owned by that user’s primary GID, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020860">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020860_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020860</version>
-      <title>All local initialization files must have mode 0740 or less permissive.</title>
-      <description>&lt;VulnDiscussion&gt;Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020860_fix">Set the mode of the local initialization files to “0740” with the following command:
-
-Note: The example will be for the smithj user, who has a home directory of “/home/smithj”.
-
-# chmod 0740 /home/smithj/.*</fixtext>
-      <fix id="F-RHEL-07-020860_fix" />
-      <check system="C-RHEL-07-020860_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that all local initialization files have a mode of “0740” or less permissive.
-
-Check the mode on all local initialization files with the following command:
-
-Note: The example will be for the smithj user, who has a home directory of “/home/smithj”.
-
-# ls -al /home/smithj/.* | more
--rwxr-xr-x  1 smithj users        896 Mar 10  2011 .profile
--rwxr-xr-x  1 smithj users        497 Jan  6  2007 .login
--rwxr-xr-x  1 smithj users        886 Jan  6  2007 .something
-
-If any local initialization files have a mode more permissive than “0740”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020870">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020870_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020870</version>
-      <title>All local interactive user initialization files executable search paths must contain only absolute paths.</title>
-      <description>&lt;VulnDiscussion&gt;The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If this path includes the current working directory (other than the user’s home directory), executables in these directories may be executed instead of system commands. This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon or two consecutive colons, this is interpreted as the current working directory. If deviations from the default system search path for the local interactive user are required, they must be documented with the Information System Security Officer (ISSO).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020870_fix">Edit the local interactive user initialization files to change any PATH variable statements that reference directories other than their home directory. If a local interactive user requires path variables to reference a directory owned by the application, it must be documented with the ISSO.</fixtext>
-      <fix id="F-RHEL-07-020870_fix" />
-      <check system="C-RHEL-07-020870_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that all local interactive user initialization files path statements do not contain statements that will reference a working directory other than the users’ home directory.
-
-Check the path statement for all local interactive user initialization files in the users' home directory with the following commands:
-
-Note: The example will be for the smithj user, which has a home directory of “/home/smithj”.
-
-# grep -i path /home/smithj/.*
-/home/smithj/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin
-/home/smithj/.bash_profile:export PATH
-
-If any local interactive user initialization files have path statements that include directories outside of their home directory, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020880">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020880_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020880</version>
-      <title>Local initialization files must not execute world-writable programs.</title>
-      <description>&lt;VulnDiscussion&gt;If user start-up files execute world-writable programs, especially in unprotected directories, they could be maliciously modified to destroy user files or otherwise compromise the system at the user level. If the system is compromised at the user level, it is easier to elevate privileges to eventually compromise the system at the root and network level.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-020880_fix">Set the mode on files being executed by the local initialization files with the following command:
-
-# chmod 0755  &lt;file&gt;</fixtext>
-      <fix id="F-RHEL-07-020880_fix" />
-      <check system="C-RHEL-07-020880_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that local initialization files do not execute world-writable programs.
-
-Check the system for world-writable files with the following command:
-# find / -perm -002 -type f -exec ls -ld {} \; | more
-
-For all files listed, check for their presence in the local initialization files with the following commands:
-
-Note: The example will be for a system that is configured to create users’ home directories in the /home directory.
-
-# grep &lt;file&gt; /home/*/.*
-
-If any local initialization files are found to reference world-writable files, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-020940">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-020940_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-020940</version>
-      <title>All system device files must be correctly labeled to prevent unauthorized modification.</title>
-      <description>&lt;VulnDiscussion&gt;If an unauthorized or modified device is allowed to exist on the system, there is the possibility the system may perform unintended or unauthorized operations.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
-      <fixtext fixref="F-RHEL-07-020940_fix">Run the following command to determine which package owns the device file:
-
-# rpm -qf &lt;filename&gt;
-
-The package can be reinstalled from a yum repository using the command:
-
-# sudo yum reinstall &lt;packagename&gt;
-
-Alternatively, the package can be reinstalled from trusted media using the command:
-
-# sudo rpm -Uvh &lt;packagename&gt;</fixtext>
-      <fix id="F-RHEL-07-020940_fix" />
-      <check system="C-RHEL-07-020940_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that all system device files are correctly labeled to prevent unauthorized modification.
-
-List all device files on the system that are incorrectly labeled with the following commands:
-
-Note: Device files are normally found under “/dev”, but applications may place device files in other directories, necessitating a search of the entire system.
-
-#find /dev -context *:device_t:* \( -type c -o -type b \) -printf "%p %Z\n"
-
-#find /dev -context *:unlabeled_t:* \( -type c -o -type b \) -printf "%p %Z\n"
-
-If there is output from either of these commands, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021010">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021010_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-021010</version>
-      <title>Files systems that contain user home directories must be mounted to prevent files with the setuid and setgid bit set from being executed.</title>
-      <description>&lt;VulnDiscussion&gt;The "nosuid" mount option causes the system to not execute setuid and setgid files with owner privileges. This option must be used for mounting any file system not containing approved setuid and setguid files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021010_fix">Configure the “/etc/fstab” to use the “nosuid” option on file systems that contain user home directories.</fixtext>
-      <fix id="F-RHEL-07-021010_fix" />
-      <check system="C-RHEL-07-021010_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify file systems that contain user home directories are mounted with the “nosetuid” option.
-
-Find the file system(s) that contain the user home directories with the following command:
-
-Note: If a separate file system has not been created for the user home directories (user home directories are mounted under “/”) this is not a finding as the “nosetuid” option cannot be used on the “/” system.
-
-# cut -d: -f 1,7 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$"
-smithj /home/smithj
-thomasr /home/thomasr
-
-Check the file systems that are mounted at boot time with the following command:
-
-# more /etc/fstab
-
-UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /home   ext4   rw,relatime,discard,data=ordered,nosuid                                                                         0 2
-
-If a file system found in “/etc/fstab” refers to the user home directory file system and it does not have the “nosetuid” option set, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021011">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021011_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-021011</version>
-      <title>Files systems that are used with removable media must be mounted to prevent files with the setuid and setgid bit set from being executed.</title>
-      <description>&lt;VulnDiscussion&gt;The "nosuid" mount option causes the system to not execute setuid and setgid files with owner privileges. This option must be used for mounting any file system not containing approved setuid and setguid files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021011_fix">Configure the “/etc/fstab” to use the “nosuid” option on file systems that are associated with removable media.</fixtext>
-      <fix id="F-RHEL-07-021011_fix" />
-      <check system="C-RHEL-07-021011_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify file systems that are used for removable media are mounted with the “nosetuid” option.
-
-Check the file systems that are mounted at boot time with the following command:
-
-# more /etc/fstab
-
-UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222     /mnt/usbflash      vfat   noauto,owner,ro,nosuid                        0 0
-
-If a file system found in “/etc/fstab” refers to removable media and it does not have the “nosetuid” option set, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021012">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021012_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-021012</version>
-      <title>Files systems that are being imported via Network File System (NFS) must be mounted to prevent files with the setuid and setgid bit set from being executed.</title>
-      <description>&lt;VulnDiscussion&gt;The "nosuid" mount option causes the system to not execute setuid and setgid files with owner privileges. This option must be used for mounting any file system not containing approved setuid and setguid files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021012_fix">Configure the “/etc/fstab” to use the “nosuid” option on file systems that are being exported via NFS.</fixtext>
-      <fix id="F-RHEL-07-021012_fix" />
-      <check system="C-RHEL-07-021012_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify file systems that are being NFS exported are mounted with the “nosetuid” option.
-
-Find the file system(s) that contain the directories being exported with the following command:
-
-# more /etc/fstab | grep nfs
-
-UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d    /store           nfs           rw,nosuid                                                    0 0
-
-If a file system found in “/etc/fstab” refers to NFS and it does not have the “nosuid” option set, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021050">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021050_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-021050</version>
-      <title>All world-writable directories must be group-owned by root, sys, bin, or an application group.</title>
-      <description>&lt;VulnDiscussion&gt;If a world-writable directory has the sticky bit set and is not group-owned by a privileged Group Identifier (GID), unauthorized users may be able to modify files created by others.
-
-The only authorized public directories are those temporary directories supplied with the system or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system and by users for temporary file storage, (e.g., /tmp), and for directories requiring global read/write 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021050_fix">Change the group of the world-writable directories to root with the following command:
-
-# chgrp root &lt;directory&gt;</fixtext>
-      <fix id="F-RHEL-07-021050_fix" />
-      <check system="C-RHEL-07-021050_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify all world-writable directories are group-owned by root, sys, bin, or an application group.
-
-Check the system for world-writable directories with the following command:
-
-# find / -perm -002 -type d -exec ls -lLd {} \;
-drwxrwxrwt. 2 root root 40 Aug 26 13:07 /dev/mqueue
-drwxrwxrwt. 2 root root 220 Aug 26 13:23 /dev/shm
-drwxrwxrwt. 14 root root 4096 Aug 26 13:29 /tmp
-
-If any world-writable directories are not owned by root, sys, bin, or an application group associated with the directory, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021060">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021060_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-021060</version>
-      <title>The umask must be set to 077 for all local interactive user accounts.</title>
-      <description>&lt;VulnDiscussion&gt;The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 700 or less permissive. Although umask can be represented as a four-digit number, the first digit representing special access modes is typically ignored or required to be “0”. This requirement applies to the globally configured system defaults and the local interactive user defaults for each account 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
-      <fixtext fixref="F-RHEL-07-021060_fix">Remove the umask statement from all local interactive users’ initialization files. 
-
-If the account is for an application, the requirement for a umask less restrictive than "077" can be documented with the Information System Security Manager (ISSM), but the user agreement for access to the account must specify that the local interactive user must log on to their account first and then switch the user to the application account with the correct option to gain the account’s environment variables.</fixtext>
-      <fix id="F-RHEL-07-021060_fix" />
-      <check system="C-RHEL-07-021060_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that the default umask for all local interactive users is “077”.
-
-Identify the locations of all local interactive user home directories by looking at the “/etc/passwd” file.
-
-Check all local interactive user initialization files for interactive users with the following command:
-
-Note: The example is for a system that is configured to create users home directories in the /home directory.
-
-# grep -i umask /home/*/.*
-
-If any local interactive user initialization files are found to have a umask statement that has a value less restrictive than “077”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021160">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021160_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-021160</version>
-      <title>Cron logging must be implemented.</title>
-      <description>&lt;VulnDiscussion&gt;Cron logging can be used to trace the successful or unsuccessful execution of cron jobs. It can also be used to spot intrusions into the use of the cron facility by unauthorized and malicious users.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021160_fix">Configure rsyslog to log all cron messages by adding or updating the following line to /etc/rsyslog.conf:
-
-cron.* /var/log/cron.log
-
-Note: The line must be added before the following entry if it exists in /etc/rsyslog.conf:
-*.* ~ # discards everything</fixtext>
-      <fix id="F-RHEL-07-021160_fix" />
-      <check system="C-RHEL-07-021160_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that rsyslog is configured to log cron events.
-
-Check the configuration of /etc/rsyslog.conf for the cron facility with the following command:
-
-Note: If another logging package is used, substitute the utility configuration file for /etc/rsyslog.conf. 
-
-# grep cron /etc/rsyslog.conf
-cron.* /var/log/cron.log
-
-If the command does not return a response, check for cron logging all facilities by inspecting the /etc/rsyslog.conf file:
-
-# more /etc/rsyslog.conf
-
-Look for the following entry:
-
-*.* /var/log/messages
-
-If rsyslog is not logging messages for the cron facility or all facilities, this is a finding.  
-
-If the entry is in the “/etc/rsyslog.conf” file but is after the entry: *.*', this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021190">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021190_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-021190</version>
-      <title>If the cron.allow file exists it must be owned by root.</title>
-      <description>&lt;VulnDiscussion&gt;If the owner of the "cron.allow" file is not set to root, the possibility exists for an unauthorized user to view or to edit sensitive 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021190_fix">Set the owner on the “/etc/cron.allow” file to root with the following command:
-
-# chown root /etc/cron.allow</fixtext>
-      <fix id="F-RHEL-07-021190_fix" />
-      <check system="C-RHEL-07-021190_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that the "cron.allow" file is owned by root.
-
-Check the owner of the "cron.allow" file with the following command:
-
-# l s -al /etc/cron.allow
--rw------- 1 root root 6 Mar  5  2011 /etc/cron.allow
-
-If the “cron.allow” file exists and has an owner other than root, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021200">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021200_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-021200</version>
-      <title>If the cron.allow file exists it must be group-owned by root.</title>
-      <description>&lt;VulnDiscussion&gt;If the group owner of the “cron.allow” file is not set to root, sensitive information could be viewed or edited by unauthorized users.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021200_fix">Set the group owner on the “/etc/cron.allow” file to root with the following command:
-
-# chgrp root /etc/cron.allow</fixtext>
-      <fix id="F-RHEL-07-021200_fix" />
-      <check system="C-RHEL-07-021200_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that the “cron.allow” file is group-owned by root.
-
-Check the group owner of the “cron.allow” file with the following command:
-
-# ls -al /etc/cron.allow
--rw------- 1 root root 6 Mar  5  2011 /etc/cron.allow
-
-If the “cron.allow” file exists and has a group owner other than root, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021230">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021230_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-021230</version>
-      <title>Kernel core dumps must be disabled unless needed.</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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021230_fix">If kernel core dumps are not required, disable the “kdump” service with the following command:
-
-# systemctl disable kdump.service
-
-If kernel core dumps are required, document the need with the ISSM.</fixtext>
-      <fix id="F-RHEL-07-021230_fix" />
-      <check system="C-RHEL-07-021230_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that kernel core dumps are disabled unless needed.
-
-Check the status of the “kdump” service with the following command:
-
-# systemctl status kdump.service
-kdump.service - Crash recovery kernel arming
-   Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled)
-   Active: active (exited) since Wed 2015-08-26 13:08:09 EDT; 43min ago
- Main PID: 1130 (code=exited, status=0/SUCCESS)
-kernel arming.
-
-If the “kdump” service is active, ask the System Administrator (SA) if the use of the service is required and documented with the Information System Security Manager (ISSM).
-
-If the service is active and is not documented, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021240">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021240_rule" severity="low" weight="10.0">
-      <version>RHEL-07-021240</version>
-      <title>A separate file system must be used for user home directories (such as /home or an equivalent).</title>
-      <description>&lt;VulnDiscussion&gt;The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021240_fix">Migrate the /home directory onto a separate file system/partition.</fixtext>
-      <fix id="F-RHEL-07-021240_fix" />
-      <check system="C-RHEL-07-021240_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that a separate file system/partition has been created for non-privileged local interactive user home directories.
-
-Check the home directory assignment for all non-privileged users (those with a UID greater than 1000) on the system with the following command:
-
-#cut -d: -f 1,3,6,7 /etc/passwd | egrep ":[1-4][0-9]{3}" | tr ":" "\t"
-
-adamsj /home/adamsj /bin/bash
-jacksonm /home/jacksonm /bin/bash
-smithj /home/smithj /bin/bash
-
-The output of the command will give the directory/partition that contains the home directories for the non-privileged users on the system (in this example, /home) and users’ shell. All accounts with a valid shell (such as /bin/bash) are considered interactive users.
-
-Check that a file system/partition has been created for the non-privileged interactive users with the following command:
-
-Note: The partition of /home is used in the example.
-
-# grep /home /etc/fstab
-UUID=333ada18    /home                   ext4    noatime,nobarrier,nodev  1 2
-
-If a separate entry for the file system/partition that contains the non-privileged interactive users' home directories does not exist, or the file system/partition for the non-privileged interactive users is not /home, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021250">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021250_rule" severity="low" weight="10.0">
-      <version>RHEL-07-021250</version>
-      <title>The system must use a separate file system for /var.</title>
-      <description>&lt;VulnDiscussion&gt;The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021250_fix">Migrate the /var path onto a separate file system.</fixtext>
-      <fix id="F-RHEL-07-021250_fix" />
-      <check system="C-RHEL-07-021250_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that a separate file system/partition has been created for /var.
-
-Check that a file system/partition has been created for /var with the following command:
-
-# grep /var /etc/fstab
-UUID=c274f65f    /var                    ext4    noatime,nobarrier        1 2
-
-If a separate entry for /var is not in use, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021260">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021260_rule" severity="low" weight="10.0">
-      <version>RHEL-07-021260</version>
-      <title>The system must use /var/log/audit for the system audit data path.</title>
-      <description>&lt;VulnDiscussion&gt;The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021260_fix">Migrate the system audit data path onto a separate file system.</fixtext>
-      <fix id="F-RHEL-07-021260_fix" />
-      <check system="C-RHEL-07-021260_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that a separate file system/partition has been created for the system audit data path.
-
-Check that a file system/partition has been created for the system audit data path with the following command:
-
-#grep /var/log/audit /etc/fstab
-UUID=3645951a    /var/log/audit          ext4    defaults                 1 2
-
-If a separate entry for /var/log/audit does not exist, ask the System Administrator (SA) if the system audit logs are being written to a different file system/partition on the system, then grep for that file system/partition. 
-
-If a separate file system/partition does not exist for the system audit data path, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021270">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021270_rule" severity="low" weight="10.0">
-      <version>RHEL-07-021270</version>
-      <title>The system must use a separate file system for /tmp (or equivalent).</title>
-      <description>&lt;VulnDiscussion&gt;The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021270_fix">Migrate the /tmp path onto a separate file system.</fixtext>
-      <fix id="F-RHEL-07-021270_fix" />
-      <check system="C-RHEL-07-021270_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that a separate file system/partition has been created for /tmp.
-
-Check that a file system/partition has been created for “/tmp” with the following command:
-
-# grep /tmp /etc/fstab
-UUID=7835718b    /tmp    ext4    nodev,nosetuid,noexec      1 2
-
-If a separate entry for /tmp is not in use, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021280">
-    <title>SRG-OS-000033-GPOS-00014</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021280_rule" severity="high" weight="10.0">
-      <version>RHEL-07-021280</version>
-      <title>The operating system must implement NIST FIPS-validated cryptography 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 using 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-000033-GPOS-00014, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000068</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002450</ident>
-      <fixtext fixref="F-RHEL-07-021280_fix">Configure the operating system to implement DoD-approved encryption by installing the dracut-fips package.
-
-To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel command line during system installation so key generation is done with FIPS-approved algorithms and continuous monitoring tests in place.
-
-Placing a system into FIPS mode after system creation involves a number of modifications to the GRUB2 configuration that are not trivial to implement.</fixtext>
-      <fix id="F-RHEL-07-021280_fix" />
-      <check system="C-RHEL-07-021280_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system implements DoD-approved encryption to protect the confidentiality of remote access sessions.
-
-Check to see if the dracut-fips package is installed with the following command:
-
-# yum list installed | grep dracut-fips
-
-dracut-fips-033-360.el7_2.x86_64.rpm
-
-If the dracut-fips package is installed, check to see if the kernel command line is configured to use FIPS mode with the following command:
-
-Note: GRUB 2 reads its configuration from the “/boot/grub2/grub.cfg” file on traditional BIOS-based machines and from the “/boot/efi/EFI/redhat/grub.cfg” file on UEFI machines.
-
-#grep fips /boot/grub2/grub.cfg
-/vmlinuz-3.8.0-0.40.el7.x86_64 root=/dev/mapper/rhel-root ro rd.md=0 rd.dm=0 rd.lvm.lv=rhel/swap crashkernel=auto rd.luks=0 vconsole.keymap=us rd.lvm.lv=rhel/root rhgb fips=1 quiet
-
-If the kernel command line is configured to use FIPS mode, check to see if the system is in FIPS mode with the following command:
-
-# cat /proc/sys/crypto/fips_enabled 1
-
-If the dracut-fips package is not installed, the kernel command line does not have a fips entry, or the system has a value of “0” for fips_enabled in /proc/sys/crypto, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021600">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021600_rule" severity="low" weight="10.0">
-      <version>RHEL-07-021600</version>
-      <title>The file integrity tool must be configured to verify Access Control Lists (ACLs).</title>
-      <description>&lt;VulnDiscussion&gt;ACLs can provide permissions beyond those permitted through the file mode and must be verified by file integrity tools.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021600_fix">Configure the file integrity tool to check file and directory acls. If “aide” is installed, ensure the “acl” rule is present on all file and directory selection lists.</fixtext>
-      <fix id="F-RHEL-07-021600_fix" />
-      <check system="C-RHEL-07-021600_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the file integrity tool is configured to verify ACLs.
-
-Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command:
-
-# yum list installed | grep aide
-
-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.
-
-Note: AIDE is highly configurable at install time. These commands assume the “aide.conf” file is under the “/etc directory”. 
-
-Use the following command to determine if the file is in another location:
-
-# find / -name aide.conf
-
-Check the “aide.conf” file to determine if the “acl” rule has been added to the rule list being applied to the files and directories selection lists.
-
-An example rule that includes the “acl” rule is below:
-
-All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux
-/bin All            # apply the custom rule to the files in bin 
-/sbin All          # apply the same custom rule to the files in sbin 
-
-If the “acl” rule is not being used on all selection lines in the “/etc/aide.conf” file, or acls are not being checked by another file integrity tool, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021610">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021610_rule" severity="low" weight="10.0">
-      <version>RHEL-07-021610</version>
-      <title>The file integrity tool must be configured to verify extended attributes.</title>
-      <description>&lt;VulnDiscussion&gt;Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021610_fix">Configure the file integrity tool to check file and directory extended attributes. If AIDE is installed, ensure the “xattrs” rule is present on all file and directory selection lists.</fixtext>
-      <fix id="F-RHEL-07-021610_fix" />
-      <check system="C-RHEL-07-021610_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the file integrity tool is configured to verify extended attributes.
-
-Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command:
-
-# yum list installed | grep aide
-
-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.
-
-Note: AIDE is highly configurable at install time. These commands assume the “aide.conf” file is under the “/etc directory”.  
-
-Use the following command to determine if the file is in another location:
-
-# find / -name aide.conf
-
-Check the “aide.conf” file to determine if the “xattrs” rule has been added to the rule list being applied to the files and directories selection lists.
-
-An example rule that includes the “xattrs” rule follows:
-
-All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux
-/bin All            # apply the custom rule to the files in bin 
-/sbin All          # apply the same custom rule to the files in sbin 
-
-If the "xattrs" rule is not being used on all selection lines in the “/etc/aide.conf” file, or extended attributes are not being checked by another file integrity tool, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021620">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021620_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-021620</version>
-      <title>The file integrity tool must use FIPS 140-2 approved cryptographic hashes for validating file contents and directories.</title>
-      <description>&lt;VulnDiscussion&gt;File integrity tools use cryptographic hashes for verifying file contents and directories have not been altered. These hashes must be FIPS 140-2 approved cryptographic hashes.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-021620_fix">Configure the file integrity tool to use FIPS 140-2 cryptographic hashes for validating file and directory contents. If AIDE is installed, ensure the “sha512” rule is present on all file and directory selection lists.</fixtext>
-      <fix id="F-RHEL-07-021620_fix" />
-      <check system="C-RHEL-07-021620_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the file integrity tool is configured to use FIPS 140-2 approved cryptographic hashes for validating file contents and directories.
-
-Note: If RHEL-07-021280 is a finding, this is automatically a finding as the system cannot implement FIPS 140-2 approved cryptographic algorithms and hashes.
-
-Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command:
-
-# yum list installed | grep aide
-
-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.
-
-Note: AIDE is highly configurable at install time. These commands assume the “aide.conf” file is under the “/etc directory”. 
-
-Use the following command to determine if the file is in another location:
-
-# find / -name aide.conf
-
-Check the “aide.conf” file to determine if the “sha512” rule has been added to the rule list being applied to the files and directories selection lists.
-
-An example rule that includes the sha512 rule follows:
-
-All=p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux
-/bin All            # apply the custom rule to the files in bin 
-/sbin All          # apply the same custom rule to the files in sbin 
-
-If the “sha512” rule is not being used on all selection lines in the “/etc/aide.conf” file, or another file integrity tool is not using FIPS 140-2 approved cryptographic hashes for validating file contents and directories, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021760">
-    <title>SRG-OS-000364-GPOS-00151</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021760_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-021760</version>
-      <title>The system must not allow removable media to be used as the boot loader unless approved.</title>
-      <description>&lt;VulnDiscussion&gt;Malicious users with removable boot media can gain access to a system configured to use removable media as the boot loader. If removable media is designed to be used as the boot loader, the requirement must be documented with the Information System Security Officer (ISSO).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
-      <fixtext fixref="F-RHEL-07-021760_fix">Remove alternate methods of booting the system from removable media or document the configuration to boot from removable media with the ISSO.</fixtext>
-      <fix id="F-RHEL-07-021760_fix" />
-      <check system="C-RHEL-07-021760_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system is not configured to use a boot loader on removable media.
-
-Note: GRUB 2 reads its configuration from the “/boot/grub2/grub.cfg” file on traditional BIOS-based machines and from the “/boot/efi/EFI/redhat/grub.cfg” file on UEFI machines.
-
-Check for the existence of alternate boot loader configuration files with the following command:
-
-# find / -name grub.conf
-/boot/grub2/grub.cfg
-
-If a “grub.cfg” is found in any subdirectories other than “/boot/grub2” and “/boot/efi/EFI/redhat”, ask the System Administrator (SA) if there is documentation signed by the ISSO to approve the use of removable media as a boot loader. 
-
-Check that the grub configuration file has the set root command in each menu entry with the following commands:
-
-# grep -c menuentry /boot/grub2/grub.cfg
-1
-# grep ‘set root’ /boot/grub2/grub.cfg
-set root=(hd0,1)
-
-If the system is using an alternate boot loader on removable media, and documentation does not exist approving the alternate configuration, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-021910">
-    <title>SRG-OS-000095-GPOS-00049</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-021910_rule" severity="high" weight="10.0">
-      <version>RHEL-07-021910</version>
-      <title>The telnet-server package must not be 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.
-
-Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
-
-Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000381</ident>
-      <fixtext fixref="F-RHEL-07-021910_fix">Configure the operating system to disable non-essential capabilities by removing the telnet-server package from the system with the following command:
-
-# yum remove telnet-server</fixtext>
-      <fix id="F-RHEL-07-021910_fix" />
-      <check system="C-RHEL-07-021910_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system is configured to disable non-essential capabilities. The most secure way of ensuring a non-essential capability is disabled is to not have the capability installed.
-
-The telnet service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session.
-
-If a privileged user were to log on using this service, the privileged user password could be compromised. 
-
-Check to see if the telnet-server package is installed with the following command:
-
-# yum list installed | grep telnet-server
-
-If the telnet-server package is installed, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030010">
-    <title>SRG-OS-000038-GPOS-00016</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030010_rule" severity="high" weight="10.0">
-      <version>RHEL-07-030010</version>
-      <title>Auditing must be configured to produce records containing information to establish what type of events occurred, where the events occurred, the source of the events, and the outcome of the events.
-
-These audit records must also identify individual identities of group account users.</title>
-      <description>&lt;VulnDiscussion&gt;Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
-
-Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
-
-Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.
-
-Satisfies: SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000042-GPOS-00021, SRG-OS-000254-GPOS-00095, SRG-OS-000255-GPOS-00096&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000131</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
-      <fixtext fixref="F-RHEL-07-030010_fix">Configure the operating system to produce audit records containing information to establish when (date and time) the events occurred.
-
-Enable the auditd service with the following command:
-
-# chkconfig auditd on</fixtext>
-      <fix id="F-RHEL-07-030010_fix" />
-      <check system="C-RHEL-07-030010_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system produces audit records containing information to establish when (date and time) the events occurred.
-
-Check to see if auditing is active by issuing the following command:
-
-# systemctl is-active auditd.service
-Active: active (running) since Tue 2015-01-27 19:41:23 EST; 22h ago
-
-If the auditd status is not active, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030090">
-    <title>SRG-OS-000046-GPOS-00022</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030090_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030090</version>
-      <title>The operating system must shut down upon audit processing failure, unless availability is an overriding concern. If availability is a concern, the system must alert the designated staff (System Administrator [SA] and Information System Security Officer [ISSO] at a minimum) 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.
-
-Satisfies: SRG-OS-000046-GPOS-00022, SRG-OS-000047-GPOS-00023&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000139</ident>
-      <fixtext fixref="F-RHEL-07-030090_fix">Configure the operating system to shut down in the event of an audit processing failure.
-
-Add or correct the following line in the /etc/audit/auditd.confs file:
-
-auditctl -f 2
-
-If availability has been determined to be more important, and this decision is documented with the ISSO, configure the operating system to notify system administration staff and ISSO staff in the event of audit processing failure.
-
-Add or correct the following line in the /etc/audit/auditd.conf file:
-
-auditctl -f 1
-
-Kernel log monitoring must also be configured to properly alert designed staff.
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030090_fix" />
-      <check system="C-RHEL-07-030090_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Confirm the audit configuration regarding how auditing processing failures are handled.
-
-Check to see what level auditctl is set to in /etc/audit/auditd.conf with the following command: 
-
-# grep \-f /etc/audit/auditd.conf
-auditctl -f 2
-
-If the value of "-f" is set to “2”, the system is configured to panic (shut down) in the event of an auditing failure.
-
-If the value of "-f" is set to “1”, the system is configured to only send information to the kernel log regarding the failure.
-
-If the "-f" flag is not set, this is a CAT I finding.
-
-If the "-f" flag is set to any value other than “1” or “2”, this is a CAT II finding.
-
-If the "-f" flag is set to “1” but the availability concern is not documented or there is no monitoring of the kernel log, this is a CAT III finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030310">
-    <title>SRG-OS-000327-GPOS-00127</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030310_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030310</version>
-      <title>All privileged function executions must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002234</ident>
-      <fixtext fixref="F-RHEL-07-030310_fix">Configure the operating system to audit the execution of privileged functions.
-
-To find the relevant setuid/setgid programs, run the following command for each local partition [PART]:
-
-# find [PART] -xdev -type f \( -perm -4000 -o -perm -2000 \) 2&gt;/dev/null
-
-For each setuid/setgid program on the system, which is not covered by an audit rule for a (sub) directory (such as /usr/sbin), add a line of the following form to "/etc/audit/rules.d/audit.rules", where &lt;suid_prog_with_full_path&gt; is the full path to each setuid/setgid program in the list:
-
-a always,exit -F &lt;suid_prog_with_full_path&gt; -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k setuid/setgid</fixtext>
-      <fix id="F-RHEL-07-030310_fix" />
-      <check system="C-RHEL-07-030310_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system audits the execution of privileged functions.
-
-To find relevant setuid and setgid programs, use the following command once for each local partition [PART]:
-
-# find [PART] -xdev -local -type f \( -perm -4000 -o -perm -2000 \) 2&gt;/dev/null
-
-Run the following command to verify entries in the audit rules for all programs found with the previous command:
-
-#grep &lt;suid_prog_with_full_path&gt;
-a always,exit -F &lt;suid_prog_with_full_path&gt; -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k setuid/setgid
-
-All setuid and setgid files on the system must have a corresponding audit rule, or must have an audit rule for the (sub) directory that contains the setuid/setgid file.
-
-If all setuid/setgid files on the system do not have audit rule coverage, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030330">
-    <title>SRG-OS-000342-GPOS-00133</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030330_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030330</version>
-      <title>The operating system must off-load audit records onto a different system or media from the system being audited.</title>
-      <description>&lt;VulnDiscussion&gt;Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
-
-Off-loading is a common process in information systems with limited audit storage capacity.
-
-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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001851</ident>
-      <fixtext fixref="F-RHEL-07-030330_fix">Configure the operating system to off-load audit records onto a different system or media from the system being audited.
-
-Set the remote server option in /etc/audisp/audisp-remote.conf with the IP address of the log aggregation server.</fixtext>
-      <fix id="F-RHEL-07-030330_fix" />
-      <check system="C-RHEL-07-030330_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system off-loads audit records onto a different system or media from the system being audited.
-
-To determine the remote server that the records are being sent to, use the following command:
-
-# grep -i remote_server /etc/audisp/audisp-remote.conf
-remote_server = 10.0.21.1
-
-If a remote server is not configured, or the line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030331">
-    <title>SRG-OS-000342-GPOS-00133</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030331_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030331</version>
-      <title>The operating system must encrypt the transfer of audit records off-loaded onto a different system or media from the system being audited.</title>
-      <description>&lt;VulnDiscussion&gt;Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
-
-Off-loading is a common process in information systems with limited audit storage capacity.
-
-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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001851</ident>
-      <fixtext fixref="F-RHEL-07-030331_fix">Configure the operating system to encrypt the transfer of off-loaded audit records onto a different system or media from the system being audited.
-
-Uncomment the enable_krb5 option in /etc/audisp/audisp-remote.conf and set it with the following line:
-
-enable_krb5 = yes</fixtext>
-      <fix id="F-RHEL-07-030331_fix" />
-      <check system="C-RHEL-07-030331_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system encrypts audit records off-loaded onto a different system or media from the system being audited.
-
-To determine if the transfer is encrypted, use the following command:
-
-# grep -i enable_krb5 /etc/audisp/audisp-remote.conf
-enable_krb5 = yes
-
-If the value of the “enable_krb5” option is not set to "yes" or the line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030340">
-    <title>SRG-OS-000342-GPOS-00133</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030340_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030340</version>
-      <title>The audit system must take appropriate action when the audit storage volume is full.</title>
-      <description>&lt;VulnDiscussion&gt;Taking appropriate action in case of a filled audit storage volume will minimize the possibility of losing audit records.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001851</ident>
-      <fixtext fixref="F-RHEL-07-030340_fix">Configure the operating system to off-load audit records onto a different system or media from the system being audited.
-
-Uncomment or edit the "disk_full_action" option in /etc/audisp/audisp-remote.conf and set it to syslog, single, or halt, such as the following line:
-
-disk_full_action = single
-
-Uncomment the network_failure_action option in /etc/audisp/audisp-remote.conf and set it to syslog, single, or halt.</fixtext>
-      <fix id="F-RHEL-07-030340_fix" />
-      <check system="C-RHEL-07-030340_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the action the operating system takes if the disk the audit records are written to becomes full.
-
-To determine the action that takes place if the disk is full on the remote server, use the following command:
-
-# grep -i disk_full_action /etc/audisp/audisp-remote.conf
-disk_full_action = single
-
-To determine the action that takes place if the network connection fails, use the following command:
-
-# grep -i network_failure_action /etc/audisp/audisp-remote.conf
-network_failure_action = stop
-
-If the value of the “network_failure_action” option is not “syslog”, “single”, or “halt”, or the line is commented out, this is a finding.
-
-If the value of the “disk_full_action” option is not "syslog", "single", or "halt", or the line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030350">
-    <title>SRG-OS-000343-GPOS-00134</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030350_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030350</version>
-      <title>The operating system must immediately notify the System Administrator (SA) and Information System Security Officer ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity.</title>
-      <description>&lt;VulnDiscussion&gt;If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storage capacity expansion.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001855</ident>
-      <fixtext fixref="F-RHEL-07-030350_fix">Configure the operating system to immediately notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.
-
-Check the system configuration to determine the partition the audit records are being written to: 
-
-# grep log_file /etc/audit/auditd.conf
-
-Determine the size of the partition that audit records are written to (with the example being /var/log/audit/):
-
-# df -h /var/log/audit/
-
-Set the value of the “space_left” keyword in /etc/audit/auditd.conf to 75 percent of the partition size.</fixtext>
-      <fix id="F-RHEL-07-030350_fix" />
-      <check system="C-RHEL-07-030350_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system immediately notifies the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.
-
-Check the system configuration to determine the partition the audit records are being written to with the following command:
-
-# grep log_file /etc/audit/auditd.conf
-log_file = /var/log/audit/audit.log
-
-Check the size of the partition that audit records are written to (with the example being /var/log/audit/):
-
-# df -h /var/log/audit/
-0.9G /var/log/audit
-
-If the audit records are not being written to a partition specifically created for audit records (in this example /var/log/audit is a separate partition), determine the amount of space other files in the partition are currently occupying with the following command:
-
-# du -sh &lt;partition&gt;
-1.8G /var
-
-Determine what the threshold is for the system to take action when 75 percent of the repository maximum audit record storage capacity is reached:
-
-# grep -i space_left /etc/audit/auditd.conf
-space_left = 225 
-
-If the value of the “space_left” keyword is not set to 75 percent of the total partition size, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030351">
-    <title>SRG-OS-000343-GPOS-00134</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030351_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030351</version>
-      <title>The operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) via email when the threshold for the repository maximum audit record storage capacity is reached.</title>
-      <description>&lt;VulnDiscussion&gt;If security personnel are not notified immediately when the threshold for the repository maximum audit record storage capacity is reached, they are unable to expand the audit record storage capacity before records are lost.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001855</ident>
-      <fixtext fixref="F-RHEL-07-030351_fix">Configure the operating system to immediately notify the SA and ISSO (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached.
-
-Uncomment or edit the “space_left_action” keyword in /etc/audit/auditd.conf and set it to email. 
- 
-space_left_action = email</fixtext>
-      <fix id="F-RHEL-07-030351_fix" />
-      <check system="C-RHEL-07-030351_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system immediately notifies the SA and ISSO (at a minimum) via email when the allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.
-
-Check what action the operating system takes when the threshold for the repository maximum audit record storage capacity is reached with the following command:
-
-# grep -I space_left_action  /etc/audit/auditd.conf
-space_left_action = email
-
-If the value of the “space_left_action” keyword is not set to email, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030352">
-    <title>SRG-OS-000343-GPOS-00134</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030352_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030352</version>
-      <title>The operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached.</title>
-      <description>&lt;VulnDiscussion&gt;If security personnel are not notified immediately when the threshold for the repository maximum audit record storage capacity is reached, they are unable to expand the audit record storage capacity before records are lost.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001855</ident>
-      <fixtext fixref="F-RHEL-07-030352_fix">Configure the operating system to immediately notify the SA and ISSO (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached.
-
-Uncomment or edit the action_mail_acct keyword in /etc/audit/auditd.conf and set it to root and any other accounts associated with security personnel. 
- 
-action_mail_acct = root</fixtext>
-      <fix id="F-RHEL-07-030352_fix" />
-      <check system="C-RHEL-07-030352_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system immediately notifies the SA and ISSO (at a minimum) via email when the threshold for the repository maximum audit record storage capacity is reached.
-
-Check what account the operating system emails when the threshold for the repository maximum audit record storage capacity is reached with the following command:
-
-# grep -i action_mail_acct  /etc/audit/auditd.conf
-action_mail_acct = root
-
-If the value of the “action_mail_acct” keyword is not set to “root” and other accounts for security personnel, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030380">
-    <title>SRG-OS-000064-GPOS-00033</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030380_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030380</version>
-      <title>All uses of the chown command must be audited.</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).
-
-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
-      <fixtext fixref="F-RHEL-07-030380_fix">Verify the operating system generates audit records when successful/unsuccessful attempts to use the “chown” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S chown -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S chown -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030380_fix" />
-      <check system="C-RHEL-07-030380_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “chown” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i chown /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S chown -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S chown -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030381">
-    <title>SRG-OS-000064-GPOS-00033</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030381_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030381</version>
-      <title>All uses of the fchown command must be audited.</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).
-
-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
-      <fixtext fixref="F-RHEL-07-030381_fix">Verify the operating system generates audit records when successful/unsuccessful attempts to use the fchown command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S fchown -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S fchown -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030381_fix" />
-      <check system="C-RHEL-07-030381_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fchown” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i fchown /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S fchown -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S fchown -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030382">
-    <title>SRG-OS-000064-GPOS-00033</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030382_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030382</version>
-      <title>All uses of the lchown command must be audited.</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).
-
-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
-      <fixtext fixref="F-RHEL-07-030382_fix">Verify the operating system generates audit records when successful/unsuccessful attempts to use the “lchown” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S lchown -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S lchown -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030382_fix" />
-      <check system="C-RHEL-07-030382_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “lchown” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i lchown /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S lchown -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S lchown -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030383">
-    <title>SRG-OS-000064-GPOS-00033</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030383_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030383</version>
-      <title>All uses of the fchownat command must be audited.</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).
-
-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
-      <fixtext fixref="F-RHEL-07-030383_fix">Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fchownat” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S fchownat -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S fchownat -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030383_fix" />
-      <check system="C-RHEL-07-030383_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fchownat” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i fchownat /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S fchownat -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S fchownat -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030390">
-    <title>SRG-OS-000458-GPOS-00203</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030390_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030390</version>
-      <title>All uses of the chmod command must be audited.</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).
-
-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030390_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “chmod” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S chmod -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S chmod -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030390_fix" />
-      <check system="C-RHEL-07-030390_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “chmod” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following command:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i chmod /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S chmod -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S chmod -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030391">
-    <title>SRG-OS-000458-GPOS-00203</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030391_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030391</version>
-      <title>All uses of the fchmod command must be audited.</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).
-
-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030391_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “fchmod” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S fchmod -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S fchmod -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030391_fix" />
-      <check system="C-RHEL-07-030391_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fchmod” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following command:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i fchmod /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S fchmod -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S fchmod -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030392">
-    <title>SRG-OS-000458-GPOS-00203</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030392_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030392</version>
-      <title>All uses of the fchmodat command must be audited.</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).
-
-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030392_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “fchmodat” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030392_fix" />
-      <check system="C-RHEL-07-030392_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fchmodat” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following command:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i fchmodat /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030400">
-    <title>SRG-OS-000458-GPOS-00203</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030400_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030400</version>
-      <title>All uses of the setxattr command must be audited.</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).
-
-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030400_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “setxattr” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S setxattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S setxattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030400_fix" />
-      <check system="C-RHEL-07-030400_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “setxattr” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i setxattr /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S setxattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S setxattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030401">
-    <title>SRG-OS-000458-GPOS-00203</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030401_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030401</version>
-      <title>All uses of the fsetxattr command must be audited.</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).
-
-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030401_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “fsetxattr” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S fsetxattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S fsetxattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030401_fix" />
-      <check system="C-RHEL-07-030401_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fsetxattr” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i fsetxattr /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S fsetxattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S fsetxattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030402">
-    <title>SRG-OS-000458-GPOS-00203</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030402_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030402</version>
-      <title>All uses of the lsetxattr command must be audited.</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).
-
-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030402_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “lsetxattr” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S lsetxattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S lsetxattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030402_fix" />
-      <check system="C-RHEL-07-030402_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “lsetxattr” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i lsetxattr /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S lsetxattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S lsetxattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030403">
-    <title>SRG-OS-000458-GPOS-00203</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030403_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030403</version>
-      <title>All uses of the removexattr command must be audited.</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).
-
-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030403_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “removexattr” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S removexattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S removexattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030403_fix" />
-      <check system="C-RHEL-07-030403_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “removexattr” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i removexattr /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S removexattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S removexattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030404">
-    <title>SRG-OS-000458-GPOS-00203</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030404_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030404</version>
-      <title>All uses of the fremovexattr command must be audited.</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).
-
-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030404_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “fremovexattr” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030404_fix" />
-      <check system="C-RHEL-07-030404_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “fremovexattr” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i fremovexattr /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030405">
-    <title>SRG-OS-000458-GPOS-00203</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030405_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030405</version>
-      <title>All uses of the lremovexattr command must be audited.</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).
-
-Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030405_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “lremovexattr” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S lremovexattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S lremovexattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030405_fix" />
-      <check system="C-RHEL-07-030405_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “lremovexattr” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i lremovexattr /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S lremovexattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
--a always,exit -F arch=b64 -S lremovexattr -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=perm_mod
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030420">
-    <title>SRG-OS-000064-GPOS-00033</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030420_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030420</version>
-      <title>All uses of the creat command must be audited.</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).
-
-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030420_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “creat” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
--a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030420_fix" />
-      <check system="C-RHEL-07-030420_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “creat” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i creat /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S creat  -Fexit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
--a always,exit -F arch=b64 -S creat  -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030421">
-    <title>SRG-OS-000064-GPOS-00033</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030421_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030421</version>
-      <title>All uses of the open command must be audited.</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).
-
-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030421_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “open” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
--a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030421_fix" />
-      <check system="C-RHEL-07-030421_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “open” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i open /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S open -Fexit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
--a always,exit -F arch=b64 -S  open -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030422">
-    <title>SRG-OS-000064-GPOS-00033</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030422_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030422</version>
-      <title>All uses of the openat command must be audited.</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).
-
-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030422_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “openat” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
--a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030422_fix" />
-      <check system="C-RHEL-07-030422_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “openat” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i openat /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S openat -Fexit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
--a always,exit -F arch=b64 -S  openat -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030423">
-    <title>SRG-OS-000064-GPOS-00033</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030423_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030423</version>
-      <title>All uses of the open_by_handle_at command must be audited.</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).
-
-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030423_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “open_by_handle_at” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
--a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030423_fix" />
-      <check system="C-RHEL-07-030423_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “open_by_handle_at” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i open_by_handle_at /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S open_by_handle_at -Fexit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
--a always,exit -F arch=b64 -S  open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030424">
-    <title>SRG-OS-000064-GPOS-00033</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030424_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030424</version>
-      <title>All uses of the truncate command must be audited.</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).
-
-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030424_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the truncate command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
--a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030424_fix" />
-      <check system="C-RHEL-07-030424_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “truncate” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i truncate /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S truncate -Fexit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
--a always,exit -F arch=b64 -S  truncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030425">
-    <title>SRG-OS-000064-GPOS-00033</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030425_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030425</version>
-      <title>All uses of the ftruncate command must be audited.</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).
-
-Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030425_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “ftruncate” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
--a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030425_fix" />
-      <check system="C-RHEL-07-030425_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “ftruncate” command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i ftruncate /etc/audit/rules.d/audit.rules
-
--a always,exit -F arch=b32 -S ftruncate -Fexit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
--a always,exit -F arch=b64 -S  ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=access
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030441">
-    <title>SRG-OS-000392-GPOS-00172</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030441_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030441</version>
-      <title>All uses of the semanage command must be audited.</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).
-
-Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030441_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the semanage command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules:
-
--a always,exit -F path=/usr/sbin/semanage
--F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030441_fix" />
-      <check system="C-RHEL-07-030441_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “semanage” command occur.
-
-Check the file system rule in /etc/audit/rules.d/audit.rules with the following command:
-
-# grep -i /usr/sbin/semanage /etc/audit/rules.d/audit.rules
-
-If the command does not return the following output, this is a finding.
-
--a always,exit -F path=/usr/sbin/semanage
--F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030442">
-    <title>SRG-OS-000392-GPOS-00172</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030442_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030442</version>
-      <title>All uses of the setsebool command must be audited.</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).
-
-Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030442_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “setsebool” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules:
-
--a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030442_fix" />
-      <check system="C-RHEL-07-030442_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “setsebool” command occur.
-
-Check the file system rule in /etc/audit/rules.d/audit.rules with the following command:
-
-# grep -i /usr/sbin/setsebool /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/sbin/setsebool
--F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030443">
-    <title>SRG-OS-000392-GPOS-00172</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030443_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030443</version>
-      <title>All uses of the chcon command must be audited.</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).
-
-Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030443_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “chcon” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules:
-
--a always,exit -F path=/usr/bin/chcon -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030443_fix" />
-      <check system="C-RHEL-07-030443_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “chcon” command occur.
-
-Check the file system rule in /etc/audit/rules.d/audit.rules with the following command:
-
-# grep -i /usr/bin/chcon /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/bin/chcon
--F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030444">
-    <title>SRG-OS-000392-GPOS-00172</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030444_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030444</version>
-      <title>All uses of the restorecon command must be audited.</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).
-
-Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030444_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “restorecon” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules:
-
--a always,exit -F path=/usr/sbin/restorecon -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 privileged-priv_change
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030444_fix" />
-      <check system="C-RHEL-07-030444_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “restorecon” command occur.
-
-Check the file system rule in /etc/audit/rules.d/audit.rules with the following command:
-
-# grep -i /usr/sbin/restorecon /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/sbin/restorecon
--F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030490">
-    <title>SRG-OS-000392-GPOS-00172</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030490_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030490</version>
-      <title>The operating system must generate audit records for all successful/unsuccessful account access count events.</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).
-
-Satisfies: SRG-OS-000392-GPOS-00172, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
-      <fixtext fixref="F-RHEL-07-030490_fix">Configure the operating system to generate audit records when successful/unsuccessful account access count events occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules: 
-
--w /var/log/tallylog -p wa -k logins
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030490_fix" />
-      <check system="C-RHEL-07-030490_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful account access count events occur. 
-
-Check the file system rule in /etc/audit/rules.d/audit.rules with the following commands: 
-
-# grep -i /var/log/tallylog etc/audit/audit.rules
-
--w /var/log/tallylog -p wa -k logins
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030491">
-    <title>SRG-OS-000392-GPOS-00172</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030491_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030491</version>
-      <title>The operating system must generate audit records for all unsuccessful account access events.</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).
-
-Satisfies: SRG-OS-000392-GPOS-00172, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
-      <fixtext fixref="F-RHEL-07-030491_fix">Configure the operating system to generate audit records when unsuccessful account access events occur. 
-
-Add or update the following rules in /etc/audit/rules.d/audit.rule: 
-
--w /var/run/faillock/ -p wa -k logins
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030491_fix" />
-      <check system="C-RHEL-07-030491_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when unsuccessful account access events occur. 
-
-Check the file system rule in /etc/audit/rules.d/audit.rules with the following commands: 
-
-# grep -i /var/run/faillock etc/audit/audit.rules
-
--w /var/run/faillock -p wa -k logins
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030492">
-    <title>SRG-OS-000392-GPOS-00172</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030492_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030492</version>
-      <title>The operating system must generate audit records for all successful account access events.</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).
-
-Satisfies: SRG-OS-000392-GPOS-00172, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
-      <fixtext fixref="F-RHEL-07-030492_fix">Configure the operating system to generate audit records when successful account access events occur. 
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules: 
-
--w /var/log/lastlog -p wa -k logins
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030492_fix" />
-      <check system="C-RHEL-07-030492_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful account access events occur. 
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands: 
-
-# grep -i /var/log/lastlog etc/audit/audit.rules
-
--w /var/log/lastlog -p wa -k logins 
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030510">
-    <title>SRG-OS-000042-GPOS-00020</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030510_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030510</version>
-      <title>All uses of the passwd command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000042-GPOS-00020, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030510_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “passwd” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules:
-
--a always,exit -F path=/usr/bin/passwd -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030510_fix" />
-      <check system="C-RHEL-07-030510_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “passwd” command occur.
-
-Check the file system rule in /etc/audit/rules.d/audit.rules with the following command:
-
-# grep -i /usr/bin/passwd /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/bin/passwd -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030511">
-    <title>SRG-OS-000042-GPOS-00020</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030511_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030511</version>
-      <title>All uses of the unix_chkpwd command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000042-GPOS-00020, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030511_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “unix_chkpwd” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules:
-
--a always,exit -F path=/sbin/unix_chkpwd -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030511_fix" />
-      <check system="C-RHEL-07-030511_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “unix_chkpwd” command occur.
-
-Check the file system rule in /etc/audit/rules.d/audit.rules with the following command:
-
-# grep -i /sbin/unix_chkpwd /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/sbin/unix_chkpwd -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030512">
-    <title>SRG-OS-000042-GPOS-00020</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030512_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030512</version>
-      <title>All uses of the gpasswd command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000042-GPOS-00020, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030512_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “gpasswd” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules:
-
--a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030512_fix" />
-      <check system="C-RHEL-07-030512_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “gpasswd” command occur.
-
-Check the file system rule in /etc/audit/rules.d/audit.rules with the following command:
-
-# grep -i /usr/bin/gpasswd /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030513">
-    <title>SRG-OS-000042-GPOS-00020</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030513_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030513</version>
-      <title>All uses of the chage command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000042-GPOS-00020, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030513_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “chage” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules:
-
--a always,exit -F path=/usr/bin/chage -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030513_fix" />
-      <check system="C-RHEL-07-030513_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “chage” command occur.
-
-Check the file system rule in /etc/audit/rules.d/audit.rules with the following command:
-
-# grep -i /usr/bin/chage /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/bin/chage -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030514">
-    <title>SRG-OS-000042-GPOS-00020</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030514_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030514</version>
-      <title>All uses of the userhelper command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000042-GPOS-00020, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030514_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “userhelper” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules:
-
--a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030514_fix" />
-      <check system="C-RHEL-07-030514_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “userhelper” command occur.
-
-Check the file system rule in /etc/audit/rules.d/audit.rules with the following command:
-
-# grep -i /usr/sbin/userhelper /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-passwd
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030521">
-    <title>SRG-OS-000037-GPOS-00015</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030521_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030521</version>
-      <title>All uses of the su command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000130</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030521_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “su” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/bin/su -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change 
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030521_fix" />
-      <check system="C-RHEL-07-030521_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “su” command occur.
-
-Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /bin/su /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/bin/su -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030522">
-    <title>SRG-OS-000037-GPOS-00015</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030522_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030522</version>
-      <title>All uses of the sudo command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000130</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030522_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “sudo” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/usr/bin/sudo -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change 
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030522_fix" />
-      <check system="C-RHEL-07-030522_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “sudo” command occur.
-
-Check for the following system calls being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /usr/bin/sudo /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/bin/sudo -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030526">
-    <title>SRG-OS-000037-GPOS-00015</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030526_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030526</version>
-      <title>All uses of the sudoedit command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000130</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030526_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “sudoedit” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/bin/sudoedit-F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change</fixtext>
-      <fix id="F-RHEL-07-030526_fix" />
-      <check system="C-RHEL-07-030526_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “sudoedit” command occur.
-
-Check for the following system calls being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /usr/bin/sudoedit /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/bin/sudoedit-F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030523">
-    <title>SRG-OS-000037-GPOS-00015</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030523_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030523</version>
-      <title>The operating system must generate audit records containing the full-text recording of modifications to sudo configuration files.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000130</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030523_fix">Configure the operating system to generate audit records containing the full-text recording of modifications to sudo configuration files. 
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules: 
-
--w /etc/sudoers -p wa -k privileged-actions
-
--w /etc/sudoers.d/ -p wa -k privileged-actions</fixtext>
-      <fix id="F-RHEL-07-030523_fix" />
-      <check system="C-RHEL-07-030523_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records containing the full-text recording of modifications to sudo configuration files. 
-
-Check for modification of the following files being audited by performing the following commands to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /etc/sudoers /etc/audit/rules.d/audit.rules
-
--w /etc/sudoers -p wa -k privileged-actions
-
-# grep -i /etc/sudoers.d/etc/audit/rules.d/audit.rules
-
--w /etc/sudoers.d/ -p wa -k privileged-actions
-
-If the command does not return output that does not match the examples, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030524">
-    <title>SRG-OS-000037-GPOS-00015</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030524_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030524</version>
-      <title>All uses of the newgrp command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000130</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030524_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “newgrp” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change</fixtext>
-      <fix id="F-RHEL-07-030524_fix" />
-      <check system="C-RHEL-07-030524_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “newgrp” command occur.
-
-Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /usr/bin/newgrp /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030525">
-    <title>SRG-OS-000037-GPOS-00015</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030525_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030525</version>
-      <title>All uses of the chsh command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000130</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030525_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “chsh” command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/usr/bin/chsh -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change</fixtext>
-      <fix id="F-RHEL-07-030525_fix" />
-      <check system="C-RHEL-07-030525_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “chsh” command occur.
-
-Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /usr/bin/chsh /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/bin/chsh -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-priv_change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030530">
-    <title>SRG-OS-000042-GPOS-00020</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030530_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030530</version>
-      <title>All uses of the mount command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged mount commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030530_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the “mount” command occur.
-
-Add or update the following rules in /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/bin/mount -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-mount
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030530_fix" />
-      <check system="C-RHEL-07-030530_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “mount” command occur.
-
-Check for the following system calls being audited by performing the following series of commands to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /bin/mount /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/bin/mount -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-mount
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030531">
-    <title>SRG-OS-000042-GPOS-00020</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030531_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030531</version>
-      <title>All uses of the umount command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged mount commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030531_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the umount command occur.
-
-Add or update the following rules in /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/bin/umount -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-mount
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030531_fix" />
-      <check system="C-RHEL-07-030531_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the “umount” command occur.
-
-Check for the following system calls being audited by performing the following series of commands to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /bin/umount /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/bin/umount -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-mount  
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030540">
-    <title>SRG-OS-000042-GPOS-00020</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030540_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030540</version>
-      <title>All uses of the postdrop command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged postfix commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030540_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the postdrop command occur.
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-postfix
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030540_fix" />
-      <check system="C-RHEL-07-030540_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the postdrop command occur.
-
-Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /usr/sbin/postdrop /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-postfix
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030541">
-    <title>SRG-OS-000042-GPOS-00020</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030541_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030541</version>
-      <title>All uses of the postqueue command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged postfix commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030541_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the postqueue command occur. 
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-postfix
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030541_fix" />
-      <check system="C-RHEL-07-030541_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the postdrop command occur.
-
-Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /usr/sbin/postqueue /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-postfix
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030550">
-    <title>SRG-OS-000042-GPOS-00020</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030550_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030550</version>
-      <title>All uses of the ssh-keysign command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged ssh commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000042-GPOS-00020, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030550_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the ssh-keysign command occur. 
-
-Add or update the following rule to /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-ssh
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030550_fix" />
-      <check system="C-RHEL-07-030550_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the ssh-keysign command occur. 
-
-Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /usr/libexec/openssh/ssh-keysign /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-ssh
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030560">
-    <title>SRG-OS-000042-GPOS-00020</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030560_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030560</version>
-      <title>All uses of the pt_chown command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000042-GPOS-00020, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030560_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the pt_chown command occur. 
-
-Add or update the following rule to /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/usr/libexec/pt_chown -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged_terminal
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030560_fix" />
-      <check system="C-RHEL-07-030560_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the pt_chown command occur. 
-
-Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /usr/libexec/pt_chown /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/libexec/pt_chown -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged_terminal
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030561">
-    <title>SRG-OS-000042-GPOS-00020</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030561_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030561</version>
-      <title>All uses of the crontab command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
-
-At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
-
-Satisfies: SRG-OS-000042-GPOS-00020, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030561_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the crontab command occur. 
-
-Add or update the following rule to /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/usr/bin/crontab -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-cron
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030561_fix" />
-      <check system="C-RHEL-07-030561_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the crontab command occur. 
-
-Check for the following system call being audited by performing the following command to check the file system rules in /etc/audit/rules.d/audit.rules: 
-
-# grep -i /usr/bin/crontab /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/usr/bin/crontab -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-cron
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030630">
-    <title>SRG-OS-000471-GPOS-00215</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030630_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030630</version>
-      <title>All uses of the pam_timestamp_check command must be audited.</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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030630_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the pam_timestamp_check command occur. 
-
-Add or update the following rule in /etc/audit/rules.d/audit.rules: 
-
--a always,exit -F path=/sbin/pam_timestamp_check -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-pam
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030630_fix" />
-      <check system="C-RHEL-07-030630_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the pam_timestamp_check command occur. 
-
-Check the auditing rules in /etc/audit/rules.d/audit.rules with the following command:
-
-# grep -i /sbin/pam_timestamp_check /etc/audit/rules.d/audit.rules
-
--a always,exit -F path=/sbin/pam_timestamp_check -F perm=x -F auid&gt;=1000 -F auid!=4294967295  -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k privileged-pam  
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030670">
-    <title>SRG-OS-000471-GPOS-00216</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030670_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030670</version>
-      <title>All uses of the init_module command must be audited.</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).
-
-Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030670_fix">Configure the operating system generates audit records when successful/unsuccessful attempts to use the init_module command occur. 
-
-Add or update the following rules to /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): 
-
--a always,exit -F arch=b32 -S init_module -F key=module-change
-
--a always,exit -F arch=b64 -S init_module -F key=module-change
-
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030670_fix" />
-      <check system="C-RHEL-07-030670_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the init_module command occur. 
-
-Check the auditing rules in /etc/audit/rules.d/audit.rules with the following command:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present.
-
-# grep -i init_module /etc/audit/etc/audit/rules.d/audit.rules
-
-If the command does not return the following output (appropriate to the architecture), this is a finding. 
-
--a always,exit -F arch=b32 -S init_module -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change
-
--a always,exit -F arch=b64 -S init_module  -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030671">
-    <title>SRG-OS-000471-GPOS-00216</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030671_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030671</version>
-      <title>All uses of the delete_module command must be audited.</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).
-
-Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030671_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the delete_module command occur. 
-
-Add or update the following rules to /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): 
-
--a always,exit -F arch=b32 -S delete_module -F key=module-change
-
--a always,exit -F arch=b64 -S delete_module -F key=module-change
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030671_fix" />
-      <check system="C-RHEL-07-030671_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the delete_module command occur. 
-
-Check the auditing rules in /etc/audit/rules.d/audit.rules with the following command:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present.
-
-# grep -i delete_module /etc/audit/etc/audit/rules.d/audit.rules
-
-If the command does not return the following output (appropriate to the architecture), this is a finding. 
-
--a always,exit -F arch=b32  -S delete_module -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change
-
--a always,exit -F arch=b64  -S delete_module -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030672">
-    <title>SRG-OS-000471-GPOS-00216</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030672_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030672</version>
-      <title>All uses of the insmod command must be audited.</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).
-
-Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030672_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the insmod command occur. 
-
-Add or update the following rule to /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): 
-
--w /sbin/insmod -p x -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030672_fix" />
-      <check system="C-RHEL-07-030672_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the insmod command occur. 
-
-Check the auditing rules in /etc/audit/rules.d/audit.rules with the following command:
-
-# grep -i insmod /etc/audit/etc/audit/rules.d/audit.rules
-
-If the command does not return the following output (appropriate to the architecture), this is a finding. 
-
--w /sbin/insmod -p x -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030673">
-    <title>SRG-OS-000471-GPOS-00216</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030673_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030673</version>
-      <title>All uses of the rmmod command must be audited.</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).
-
-Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030673_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the rmmod command occur. 
-
-Add or update the following rule to /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): 
-
--w /sbin/rmmod-p x -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030673_fix" />
-      <check system="C-RHEL-07-030673_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the rmmod command occur. 
-
-Check the auditing rules in /etc/audit/rules.d/audit.rules with the following command:
-
-# grep -i rmmod /etc/audit/etc/audit/rules.d/audit.rules
-
-If the command does not return the following output (appropriate to the architecture), this is a finding. 
-
--w /sbin/rmmod -p x -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030674">
-    <title>SRG-OS-000471-GPOS-00216</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030674_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030674</version>
-      <title>All uses of the modprobe command must be audited.</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).
-
-Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <fixtext fixref="F-RHEL-07-030674_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the modprobe command occur. 
-
-Add or update the following rule to /etc/audit/rules.d/audit.rules (removing those that do not match the CPU architecture): 
-
--w /sbin/modprobe -p x -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030674_fix" />
-      <check system="C-RHEL-07-030674_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the modprobe command occur. 
-
-Check the auditing rules in /etc/audit/rules.d/audit.rules with the following command:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present.
-
-# grep -i modprobe /etc/audit/etc/audit/rules.d/audit.rules
-
-If the command does not return the following output (appropriate to the architecture), this is a finding. 
-
--w /sbin/modprobe -p x -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -F key=module-change
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030710">
-    <title>SRG-OS-000004-GPOS-00004</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030710_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030710</version>
-      <title>The operating system must generate audit records for all account creations, modifications, disabling, and termination events.</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).
-
-Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000241-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000018</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001403</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002130</ident>
-      <fixtext fixref="F-RHEL-07-030710_fix">Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events.
-
-Add or update the following file system rules to /etc/audit/rules.d/audit.rules:
-
--w /etc/group -p wa -k identity
--w /etc/passwd -p wa -k identity
--w /etc/gshadow -p wa -k identity
--w /etc/shadow -p wa -k identity
--w /etc/security/opasswd -p wa -k identity
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030710_fix" />
-      <check system="C-RHEL-07-030710_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system automatically audits account creation by performing the following series of commands to check the file system rules in /etc/audit/rules.d/audit.rules:
-
-# grep /etc/group /etc/audit/rules.d/audit.rules
-
-If the command does not return the following output, this is a finding. 
-
--w /etc/group -p wa -k audit_rules_usergroup_modification
-
-# grep /etc/passwd /etc/audit/rules.d/audit.rules
-
-If the command does not return the following output, this is a finding. 
-
--w /etc/passwd -p wa -k audit_rules_usergroup_modification
-
-# grep /etc/gshadow /etc/audit/rules.d/audit.rules
-
-If the command does not return the following output, this is a finding. 
-
--w /etc/gshadow -p wa -k audit_rules_usergroup_modification
-
-# grep /etc/shadow /etc/audit/rules.d/audit.rules
-
-If the command does not return the following output, this is a finding. 
-
--w /etc/shadow -p wa -k audit_rules_usergroup_modification
-
-# grep /etc/security/opasswd /etc/audit/rules.d/audit.rules
-
-If the command does not return the following output, this is a finding. 
-
--w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030750">
-    <title>SRG-OS-000466-GPOS-00210</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030750_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030750</version>
-      <title>All uses of the rename command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
-
-Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030750_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the rename command occur.
-
-Add the following rules to “/etc/audit/rules.d/audit.rules” (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S rename -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
--a always,exit -F arch=b64 -S rename -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030750_fix" />
-      <check system="C-RHEL-07-030750_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the rename command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i rename /etc/audit/rules.d/audit.rules
--a always,exit -F arch=b32 -S rename -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
--a always,exit -F arch=b64 -S rename -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030751">
-    <title>SRG-OS-000466-GPOS-00210</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030751_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030751</version>
-      <title>All uses of the renameat command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
-
-Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030751_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the renameat  command occur.
-
-Add the following rules to “/etc/audit/rules.d/audit.rules” (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S renameat  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
--a always,exit -F arch=b64 -S renameat  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030751_fix" />
-      <check system="C-RHEL-07-030751_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the renameat command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i renameat  /etc/audit/rules.d/audit.rules
--a always,exit -F arch=b32 -S renameat  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
--a always,exit -F arch=b64 -S renameat  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030752">
-    <title>SRG-OS-000466-GPOS-00210</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030752_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030752</version>
-      <title>All uses of the rmdir command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
-
-Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030752_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the rmdir command occur.
-
-Add the following rules to “/etc/audit/rules.d/audit.rules” (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S rmdir  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
--a always,exit -F arch=b64 -S rmdir  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030752_fix" />
-      <check system="C-RHEL-07-030752_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the rmdir command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i rmdir /etc/audit/rules.d/audit.rules
--a always,exit -F arch=b32 -S rmdir  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
--a always,exit -F arch=b64 -S rmdir  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030753">
-    <title>SRG-OS-000466-GPOS-00210</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030753_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030753</version>
-      <title>All uses of the unlink command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
-
-Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030753_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the unlink command occur.
-
-Add the following rules to “/etc/audit/rules.d/audit.rules” (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S unlink -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
--a always,exit -F arch=b64 -S unlink  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030753_fix" />
-      <check system="C-RHEL-07-030753_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the unlink command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i unlink/etc/audit/rules.d/audit.rules
--a always,exit -F arch=b32 -S unlink -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
--a always,exit -F arch=b64 -S unlink  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030754">
-    <title>SRG-OS-000466-GPOS-00210</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030754_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030754</version>
-      <title>All uses of the unlinkat command must be audited.</title>
-      <description>&lt;VulnDiscussion&gt;If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
-
-Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
-      <fixtext fixref="F-RHEL-07-030754_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the unlinkat command occur.
-
-Add the following rules to “/etc/audit/rules.d/audit.rules” (removing those that do not match the CPU architecture):
-
--a always,exit -F arch=b32 -S unlinkat -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
--a always,exit -F arch=b64 -S unlinkat  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
-
-The audit daemon must be restarted for the changes to take effect.</fixtext>
-      <fix id="F-RHEL-07-030754_fix" />
-      <check system="C-RHEL-07-030754_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the unlinkat command occur.
-
-Check the file system rules in /etc/audit/rules.d/audit.rules with the following commands:
-
-Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
-
-# grep -i unlinkat/etc/audit/rules.d/audit.rules
--a always,exit -F arch=b32 -S unlinkat -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
--a always,exit -F arch=b64 -S unlinkat -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -F subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 -k delete
-
-If the command does not return any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030770">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030770_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030770</version>
-      <title>The system must send rsyslog output to a log aggregation server.</title>
-      <description>&lt;VulnDiscussion&gt;Sending rsyslog output to another system ensures that the logs cannot be removed or modified in the event that the system is compromised or has a hardware failure.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-030770_fix">Modify the “/etc/rsyslog.conf” file to contain a configuration line to send all “rsyslog” output to a log aggregation system:
-
-*.* @@&lt;log aggregation system name&gt;</fixtext>
-      <fix id="F-RHEL-07-030770_fix" />
-      <check system="C-RHEL-07-030770_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify “rsyslog” is configured to send all messages to a log aggregation server.
-
-Check the configuration of “rsyslog” with the following command:
-
-# grep @ /etc/rsyslog.conf
-*.* @@logagg.site.mil
-
-If there are no lines in the “/etc/rsyslog.conf” file that contain the “@” or “@@” symbol(s), and the lines with the correct symbol(s) to send output to another system do not cover all “rsyslog” output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030780">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030780_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030780</version>
-      <title>The rsyslog daemon must not accept log messages from other servers unless the server is being used for log aggregation.</title>
-      <description>&lt;VulnDiscussion&gt;Unintentionally running a rsyslog server accepting remote messages puts the system at increased risk. Malicious rsyslog messages sent to the server could exploit vulnerabilities in the server software itself, could introduce misleading information in to the system's logs, or could fill the system's storage leading to a Denial of Service.
-If the system is intended to be a log aggregation server its use must be documented with the ISSO.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
-      <fixtext fixref="F-RHEL-07-030780_fix">Modify the “/etc/rsyslog.conf” file to remove the “ModLoad imtcp” configuration line, or document the system as being used for log aggregation.</fixtext>
-      <fix id="F-RHEL-07-030780_fix" />
-      <check system="C-RHEL-07-030780_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that the system is not accepting "rsyslog" messages from other systems unless it is documented as a log aggregation server.
-
-Check the configuration of rsyslog with the following command:
-
-# grep imtcp /etc/rsyslog.conf
-ModLoad imtcp
-
-If the "imtcp" module is being loaded in the "/etc/rsyslog.conf" file ask to see the documentation for the system being used for log aggregation.
-
-If the documentation does not exist, or does not specify the server as a log aggregation system, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030810">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030810_rule" severity="high" weight="10.0">
-      <version>RHEL-07-030810</version>
-      <title>The system must use a DoD-approved virus scan program.</title>
-      <description>&lt;VulnDiscussion&gt;Virus scanning software can be used to protect a system from penetration from computer viruses and to limit their spread through intermediate systems.  
-
-The virus scanning software should be configured to perform scans dynamically on accessed files. If this capability is not available, the system must be configured to scan, at a minimum, all altered files on the system on a daily basis.
-
-If the system processes inbound SMTP mail, the virus scanner must be configured to scan all received mail.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001668</ident>
-      <fixtext fixref="F-RHEL-07-030810_fix">Install an approved DoD antivirus solution on the system.</fixtext>
-      <fix id="F-RHEL-07-030810_fix" />
-      <check system="C-RHEL-07-030810_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system is using a DoD-approved virus scan program.
-
-Check for the presence of “McAfee VirusScan Enterprise for Linux” with the following command:
-
-# systemctl status nails
-nails - service for McAfee VirusScan Enterprise for Linux 
-&gt;  Loaded: loaded /opt/NAI/package/McAfeeVSEForLinux/McAfeeVSEForLinux-2.0.2.&lt;build_number&gt;; enabled)
-&gt;  Active: active (running) since Mon 2015-09-27 04:11:22 UTC;21 min ago
-
-If the “nails” service is not active, check for the presence of “clamav” on the system with the following command:
-
-# systemctl status clamav-daemon.socket
- systemctl status clamav-daemon.socket
-  clamav-daemon.socket - Socket for Clam AntiVirus userspace daemon
-     Loaded: loaded (/lib/systemd/system/clamav-daemon.socket; enabled)
-     Active: active (running) since Mon 2015-01-12 09:32:59 UTC; 7min ago
-
-If neither of these applications are loaded and active, ask the System Administrator (SA) if there is an antivirus package installed and active on the system. If no antivirus scan program is active on the system, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-030820">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-030820_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-030820</version>
-      <title>The system must update the DoD-approved virus scan program every seven days or more frequently.</title>
-      <description>&lt;VulnDiscussion&gt;Virus scanning software can be used to protect a system from penetration from computer viruses and to limit their spread through intermediate systems.  
-
-The virus scanning software should be configured to check for software and virus definition updates with a frequency no longer than seven days. If a manual process is required to update the virus scan software or definitions, it must be documented with the Information System Security Manager (ISSM).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001668</ident>
-      <fixtext fixref="F-RHEL-07-030820_fix">Update the approved DoD virus scan software and virus definition files.</fixtext>
-      <fix id="F-RHEL-07-030820_fix" />
-      <check system="C-RHEL-07-030820_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system is using a DoD-approved virus scan program and the virus definition file is less than seven days old.
-
-Check for the presence of “McAfee VirusScan Enterprise for Linux” with the following command:
-
-# systemctl status nails
-nails - service for McAfee VirusScan Enterprise for Linux 
-&gt;  Loaded: loaded /opt/NAI/package/McAfeeVSEForLinux/McAfeeVSEForLinux-2.0.2.&lt;build_number&gt;; enabled)
-&gt;  Active: active (running) since Mon 2015-09-27 04:11:22 UTC;21 min ago
-
-If the “nails” service is not active, check for the presence of “clamav” on the system with the following command:
-
-# systemctl status clamav-daemon.socket
-systemctl status clamav-daemon.socket
-  clamav-daemon.socket - Socket for Clam AntiVirus userspace daemon
-     Loaded: loaded (/lib/systemd/system/clamav-daemon.socket; enabled)
-     Active: active (running) since Mon 2015-01-12 09:32:59 UTC; 7min ago
-
-If “McAfee VirusScan Enterprise for Linux” is active on the system, check the dates of the virus definition files with the following command:
-
-# ls -al /opt/NAI/LinuxShield/engine/dat/*.dat
-&lt;need output&gt;
-
-If the virus definition files have dates older than seven days from the current date, this is a finding.
-
-If “clamav” is active on the system, check the dates of the virus database with the following commands:
-
-# grep -I databasedirectory /etc/clamav.conf
-DatabaseDirectory /var/lib/clamav
-
-# ls -al /var/lib/clamav/*.cvd
--rwxr-xr-x  1 root root      149156 Mar  5  2011 daily.cvd
-
-If the database file has a date older than seven days from the current date, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040010">
-    <title>SRG-OS-000027-GPOS-00008</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040010_rule" severity="low" weight="10.0">
-      <version>RHEL-07-040010</version>
-      <title>The operating system must limit the number of concurrent sessions to 10 for all accounts and/or account types.</title>
-      <description>&lt;VulnDiscussion&gt;Operating system management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the number of allowed users and sessions per user is helpful in reducing the risks related to DoS attacks.
-
-This requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions should be defined based on mission needs and the operational environment for each system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000054</ident>
-      <fixtext fixref="F-RHEL-07-040010_fix">Configure the operating system to limit the number of concurrent sessions to 10 for all accounts and/or account types.
-
-Add the following line to the top of the /etc/security/limits.conf:
-
-* hard maxlogins 10</fixtext>
-      <fix id="F-RHEL-07-040010_fix" />
-      <check system="C-RHEL-07-040010_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system limits the number of concurrent sessions to ten for all accounts and/or account types by issuing the following command:
-
-# grep "maxlogins" /etc/security/limits.conf
-* hard maxlogins 10
-
-This can be set as a global domain (with the * wildcard) but may be set differently for multiple domains.
-
-If the maxlogins item is missing or the value is not set to 10 or less for all domains that have the maxlogins item assigned, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040020">
-    <title>SRG-OS-000032-GPOS-00013</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040020_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040020</version>
-      <title>The system must log informational authentication data.</title>
-      <description>&lt;VulnDiscussion&gt;Access services, such as those providing remote access to network devices and information systems, that lack automated monitoring capabilities increase risk and make remote user access management difficult at best.
-
-Automated monitoring of access sessions allows organizations to detect cyber attacks 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000067</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
-      <fixtext fixref="F-RHEL-07-040020_fix">Configure the operating system to log informational authentication data.
-
-Add the following rules to the /etc/rsyslog.conf file:
-
-auth.*,authpriv.* /var/log/auth.log
-daemon.notice /var/log/messages</fixtext>
-      <fix id="F-RHEL-07-040020_fix" />
-      <check system="C-RHEL-07-040020_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system logs informational authentication data.
-
-Check to see if rsyslog is logging authentication information with the following commands:
-
-# grep auth* /etc/rsyslog.conf
-auth,authpriv.debug /var/log/auth.log
-
-# grep daemon.* /etc/rsyslog.conf
-daemon.notice /var/log/messages
-
-If the auth, authpriv, and daemon facilities are not being logged, or they are being logged at a priority of notice or higher, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040030">
-    <title>SRG-OS-000066-GPOS-00034</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040030_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040030</version>
-      <title>The operating system, for PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.</title>
-      <description>&lt;VulnDiscussion&gt;A certificate’s certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate.  
-
-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.
-
-Certification path validation includes checks such as certificate issuer trust, time validity, and revocation status for each certificate in the certification path. Revocation status information for CA and subject certificates in a certification path is commonly provided via certificate revocation lists (CRLs) or online certificate status protocol (OCSP) responses. 
-
-Operating systems that do not validate certificates by performing RFC 5280-compliant certification path validation to a trust anchor are in danger of accepting certificates that are invalid and or counterfeit. This could allow unauthorized access to a 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000185</ident>
-      <fixtext fixref="F-RHEL-07-040030_fix">Configure the operating system, for PKI-based authentication, to validate certificates by performing RFC 5280-compliant certification path validation.
-
-Set all cert_policy lines to use Online Certificate Status Protocol (OCSP) in /etc/pam_pkcs11/pam_pkcs11.conf:
-
-cert_policy = ca, ocsp_on, signature;
-
-If the system cannot use OCSP, configure the system to use certificate revocation lists in /etc/pam_pkcs11/ pam_pkcs11.conf:
-
-crl_dir = /etc/pam_pkcs11/crls;
-
-and place a certificate revocation file in the configured directory.</fixtext>
-      <fix id="F-RHEL-07-040030_fix" />
-      <check system="C-RHEL-07-040030_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system, for PKI–based authentication, validates certificates by performing RFC 5280–compliant certification path validation.
-
-Check to see if Online Certificate Status Protocol (OCSP) is enabled on the system with the following command:
-
-# grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf
-cert_policy =ca, ocsp_on, signature;
-cert_policy =ca, ocsp_on, signature;
-cert_policy =ca, ocsp_on, signature;
-
-There must be at least three lines returned. If oscp_on is present in all cert_policy lines this is not a finding.
-
-If oscp_on is not present in all lines check for the presence of certificate revocation lists:
-
-# grep crl_dir = /etc/pam_pkcs11/crls
-crl_dir = /etc/pam_pkcs11/crls;
-
-Check the returned directory for the presence of a crl file.
-
-If the file exists this in the configured directory is not a finding.
-
-If the system is not configured to use OCSP or crls, or the crls file is missing, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040040">
-    <title>SRG-OS-000067-GPOS-00035</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040040_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040040</version>
-      <title>The operating system, for PKI-based authentication, must enforce authorized access to all PKI private keys stored or used by the operating system.</title>
-      <description>&lt;VulnDiscussion&gt;If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure.
-
-The cornerstone of the PKI is the private key used to encrypt or digitally sign information.
-
-If private keys are stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key(s) to digitally sign data and thus impersonate the associated subjects (systems or users).
-
-Both the holders of a digital certificate and the issuing authority must take careful measures to protect the corresponding private keys. Private keys should always be generated and protected in appropriate FIPS 140-2 validated cryptographic modules.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000186</ident>
-      <fixtext fixref="F-RHEL-07-040040_fix">Configure the operating system, for PKI-based authentication, to enforce authorized access to all PKI private keys stored or used by the operating system.
-
-To use cackey edit /etc/pam_pkcs11/pam_pkcs11.conf:
-
-Change the use_pkcs11_module option to cackey.
-use_pkcs11_module = cackey;
-
-Then directly after the aforementioned line, copy the following lines:
-
-# Cackey Support
-  pkcs11_module cackey {
-    module = /usr/lib64/libcackey.so;
-    description = "Cackey";
-    slot_num = 0;
-    support_threads = false;
-    ca_dir = /etc/pam_pkcs11/cacerts;
-    crl_dir = /etc/pam_pkcs11/crls;
-    cert_policy = signature;
-  }
-To use coolkey edit /etc/pam_pkcs11/pam_pkcs11.conf:
-
-Change the use_pkcs11_module option to coolkey.
-use_pkcs11_module = coolkey;
-
-Then directly after the aforementioned line, copy the following lines:
-
-# Cackey Support
-  pkcs11_module coolkey {
-    module = libcoolkeypk11.so;
-
-    description = "Coolkey";
-    slot_num = 0;
-    support_threads = false;
-    ca_dir = “/etc/pam_pkcs11/cacerts”;
-    crl_dir = “/etc/pam_pkcs11/crls”;
-    cert_policy = signature;
-  }
-
-Find and change the line:
-
-use_mappers = digest, cn, pwent, uid, mail, subject, null;
-to
-use_mappers = subject;</fixtext>
-      <fix id="F-RHEL-07-040040_fix" />
-      <check system="C-RHEL-07-040040_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system, for PKI–based authentication, enforces authorized access to all PKI private keys stored/utilized by the operating system.
-
-Check the module being used by the system smartcard architecture with the following command:
-
-# grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf
-use_pkcs11_module = cackey; 
-
-If the module returned is not cackey or coolkey, or the line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040050">
-    <title>SRG-OS-000068-GPOS-00036</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040050_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040050</version>
-      <title>The operating system 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000187</ident>
-      <fixtext fixref="F-RHEL-07-040050_fix">Configure the operating system to map the authenticated identity to the user or group account for PKI-based authentication by creating the common name map file with the following command:
-
-# touch /etc/pam_pkcs11/subject_mapping</fixtext>
-      <fix id="F-RHEL-07-040050_fix" />
-      <check system="C-RHEL-07-040050_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system maps the authenticated identity to the user or group account for PKI–based authentication by verifying the common name map file exists with the following command:
-
-# ls –al /etc/pam_pkcs11/cn_map
-–rw–r––––– 1 root root 1294 Apr 22 17:22 /etc/pam_pkcs11/subject_mapping
-
-If the file does not exist, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040060">
-    <title>SRG-OS-000068-GPOS-00036</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040060_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040060</version>
-      <title>The cn_map file must have mode 0644 or less permissive.</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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000187</ident>
-      <fixtext fixref="F-RHEL-07-040060_fix">Configure the operating system to protect the file that maps the authenticated identity to the user or group account for PKI-based authentication by setting the mode on the cn_map file to “0644” with the following command:
-
-# chmod 0644 /etc/pam_pkcs11/cn_map</fixtext>
-      <fix id="F-RHEL-07-040060_fix" />
-      <check system="C-RHEL-07-040060_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system protects the file that maps the authenticated identity to the user or group account for PKI–based authentication.
-
-Check the mode on the cn_map file with the following command:
-
-# ls –al /etc/pam_pkcs11/cn_map
-–rw––––––– 1 root root 1294 Apr 22 17:22 /etc/pam_pkcs11/cn_map
-
-If the cn_map file has a mode more permissive than “0644”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040070">
-    <title>SRG-OS-000068-GPOS-00036</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040070_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040070</version>
-      <title>The cn_map file must be owned by root.</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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000187</ident>
-      <fixtext fixref="F-RHEL-07-040070_fix">Configure the operating system to protect the file that maps the authenticated identity to the user or group account for PKI-based authentication by setting the owner on the cn_map file to root with the following command:
-
-# chown root /etc/pam_pkcs11/cn_map</fixtext>
-      <fix id="F-RHEL-07-040070_fix" />
-      <check system="C-RHEL-07-040070_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system protects the file that maps the authenticated identity to the user or group account for PKI–based authentication.
-
-Check the owner on the cn_map file with the following command:
-
-# ls –al /etc/pam_pkcs11/cn_map
-–rw––––––– 1 root root 1294 Apr 22 17:22 /etc/pam_pkcs11/cn_map
-
-If the cn_map file has an owner other than root, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040080">
-    <title>SRG-OS-000068-GPOS-00036</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040080_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040080</version>
-      <title>The cn_map file must be group owned by root.</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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000187</ident>
-      <fixtext fixref="F-RHEL-07-040080_fix">Configure the operating system to protect the file that maps the authenticated identity to the user or group account for PKI-based authentication by setting the group owner on the cn_map file to root with the following command:
-
-# chgrp root /etc/pam_pkcs11/cn_map</fixtext>
-      <fix id="F-RHEL-07-040080_fix" />
-      <check system="C-RHEL-07-040080_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system protects the file that maps the authenticated identity to the user or group account for PKI–based authentication.
-
-Check the group owner on the cn_map file with the following command:
-
-# ls –al /etc/pam_pkcs11/cn_map
-–rw––––––– 1 root root 1294 Apr 22 17:22 /etc/pam_pkcs11/cn_map
-
-If the cn_map file has a group owner other than root, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040100">
-    <title>SRG-OS-000096-GPOS-00050</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040100_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040100</version>
-      <title>The host must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management Component Local Service Assessment (PPSM CLSA) and vulnerability assessments.</title>
-      <description>&lt;VulnDiscussion&gt;In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.
-
-Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.
-
-To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.
-
-Satisfies: SRG-OS-000096-GPOS-00050, SRG-OS-000297-GPOS-00115&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000382</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002314</ident>
-      <fixtext fixref="F-RHEL-07-040100_fix">Update the host's firewall settings and/or running services to comply with the PPSM CLSA for the site or program and the PPSM CAL.</fixtext>
-      <fix id="F-RHEL-07-040100_fix" />
-      <check system="C-RHEL-07-040100_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Inspect the firewall configuration and running services to verify that it is configured to prohibit or restrict the use of functions, ports, protocols, and/or services that are unnecessary or prohibited.
-
-Check which services are currently active with the following command:
-
-# firewall-cmd --list-all
-public (default, active)
-  interfaces: enp0s3
-  sources: 
-  services: dhcpv6-client dns http https ldaps rpc-bind ssh
-  ports: 
-  masquerade: no
-  forward-ports: 
-  icmp-blocks: 
-  rich rules: 
-
-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 additional ports, protocols, or services that are not in the PPSM CLSA, or there are ports, protocols, or services that are prohibited by the PPSM Category Assurance List (CAL), this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040110">
-    <title>SRG-OS-000033-GPOS-00014</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040110_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040110</version>
-      <title>A FIPS 140-2 approved cryptographic algorithm must be used for SSH communications.</title>
-      <description>&lt;VulnDiscussion&gt;Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.
-
-Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
-
-FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system.
-
-Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000120-GPOS-00061, SRG-OS-000125-GPOS-00065, SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000068</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000803</ident>
-      <fixtext fixref="F-RHEL-07-040110_fix">Configure SSH to use FIPS 140-2 approved cryptographic algorithms.
-
-Add the following line (or modify the line to have the required value) to the /etc/ssh/sshd_config file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor).
-
-Ciphers aes128-ctr aes192-ctr, aes256-ctr</fixtext>
-      <fix id="F-RHEL-07-040110_fix" />
-      <check system="C-RHEL-07-040110_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system uses mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.
-
-Note: If RHEL-07-021280 is a finding, this is automatically a finding as the system cannot implement FIPS 140-2 approved cryptographic algorithms and hashes.
-
-The location of the sshd_config file may vary on the system and can be found using the following command:
-
-# find / -name ‘sshd*_config’
-
-If there is more than one ssh server daemon configuration file on the system, determine which daemons are active on the system with the following command:
-
-# ps -ef | grep sshd
-
-The command will return the full path of the ssh daemon. This will indicate which sshd_config file will be checked with the following command:
-
-# grep -i ciphers /etc/ssh/sshd_config
-Ciphers aes128-ctr aes192-ctr, aes256-ctr
-
-If any ciphers other than “aes128-ctr”, “aes192-ctr”, or “aes256-ctr” are listed, the “Ciphers” keyword is missing, or the retuned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040160">
-    <title>SRG-OS-000163-GPOS-00072</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040160_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040160</version>
-      <title>All network connections associated with a communication session must be terminated at the end of the session or after 10 minutes of inactivity from the user at a command prompt, except to fulfill documented and validated mission requirements.</title>
-      <description>&lt;VulnDiscussion&gt;Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element. 
-
-Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001133</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002361</ident>
-      <fixtext fixref="F-RHEL-07-040160_fix">Configure the operating system to terminate all network connections associated with a communications session at the end of the session or after a period of inactivity.
-
-Add the following line to /etc/profile (or modify the line to have the required value):
-
-TMOUT=600</fixtext>
-      <fix id="F-RHEL-07-040160_fix" />
-      <check system="C-RHEL-07-040160_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system terminates all network connections associated with a communications session at the end of the session or based on inactivity.
-
-Check the value of the system inactivity timeout with the following command:
-
-# grep -i tmout /etc/profile 
-TMOUT=600
-
-If “TMOUT” is not set to 600 or less in /etc/profile, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040170">
-    <title>SRG-OS-000023-GPOS-00006</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040170_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040170</version>
-      <title>The Standard Mandatory DoD Notice and Consent Banner must be displayed immediately prior to, or as part of, remote access logon prompts.</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."
-
-Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007 , 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000048</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000050</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001384</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001385</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001386</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001387</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001388</ident>
-      <fixtext fixref="F-RHEL-07-040170_fix">Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via the ssh.
-
-Edit the /etc/ssh/sshd_config file to uncomment the banner keyword and configure it to point to a file that will contain the logon banner (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor). An example configuration line is:
-
-banner=/etc/issue
-
-Either create the file containing the banner or replace the text in the file with the Standard Mandatory DoD Notice and Consent Banner. The DoD required text is:
-
-"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."</fixtext>
-      <fix id="F-RHEL-07-040170_fix" />
-      <check system="C-RHEL-07-040170_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify any publicly accessible connection to the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
-
-Check for the location of the banner file being used with the following command:
-
-# grep -i banner /etc/ssh/sshd_config
-
-banner=/etc/issue
-
-This command will return the banner keyword and the name of the file that contains the ssh banner (in this case /etc/issue).
-
-If the line is commented out, this is a finding.
-
-View the file specified by the banner keyword to check that it matches the text of 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.”
-
-If the system does not display a graphical logon banner or the banner does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding.
-
-If the text in the file does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040180">
-    <title>SRG-OS-000250-GPOS-00093</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040180_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040180</version>
-      <title>The operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) authentication communications.</title>
-      <description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
-
-Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001453</ident>
-      <fixtext fixref="F-RHEL-07-040180_fix">Configure the operating system to implement cryptography to protect the integrity of LDAP authentication sessions.
-
-Set the USELDAPAUTH=yes in /etc/sysconfig/authconfig.
-
-Set ssl start_tls in /etc/pam_ldap.conf.</fixtext>
-      <fix id="F-RHEL-07-040180_fix" />
-      <check system="C-RHEL-07-040180_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system implements cryptography to protect the integrity of remote LDAP authentication sessions.
-
-To determine if LDAP is being used for authentication, use the following command:
-
-# grep -i useldapauth /etc/sysconfig/authconfig
-USELDAPAUTH=yes
-
-If USELDAPAUTH=yes, then LDAP is being used. To see if LDAP is configured to use TLS, use the following command:
-
-# grep -i ssl /etc/pam_ldap.conf
-ssl start_tls
-
-If the “ssl” option is not “start_tls”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040181">
-    <title>SRG-OS-000250-GPOS-00093</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040181_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040181</version>
-      <title>The operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications.</title>
-      <description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
-
-Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001453</ident>
-      <fixtext fixref="F-RHEL-07-040181_fix">Configure the operating system to implement cryptography to protect the integrity of LDAP remote access sessions.
-
-Set the tls_cacertdir option in /etc/pam_ldap.conf to point to the directory that will contain the X.509 certificates for peer authentication.
-
-Set the tls_cacertfile option in /etc/pam_ldap.conf to point to the path for the X.509 certificates used for peer authentication.</fixtext>
-      <fix id="F-RHEL-07-040181_fix" />
-      <check system="C-RHEL-07-040181_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system implements cryptography to protect the integrity of remote LDAP access sessions.
-
-To determine if LDAP is being used for authentication, use the following command:
-
-# grep -i useldapauth /etc/sysconfig/authconfig
-USELDAPAUTH=yes
-
-If USELDAPAUTH=yes, then LDAP is being used. 
-
-Check for the directory containing X.509 certificates for peer authentication with the following command:
-
-# grep -i cacertdir /etc/pam_ldap.conf
-tls_cacertdir /etc/openldap/certs
-
-Verify the directory set with the “tls_cacertdir” option exists.
-
-If the directory does not exist or the option is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040182">
-    <title>SRG-OS-000250-GPOS-00093</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040182_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040182</version>
-      <title>The operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications.</title>
-      <description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
-
-Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001453</ident>
-      <fixtext fixref="F-RHEL-07-040182_fix">Configure the operating system to implement cryptography to protect the integrity of LDAP remote access sessions.
-
-Set the tls_cacertfile option in /etc/pam_ldap.conf to point to the path for the X.509 certificates used for peer authentication.</fixtext>
-      <fix id="F-RHEL-07-040182_fix" />
-      <check system="C-RHEL-07-040182_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system implements cryptography to protect the integrity of remote ldap access sessions.
-
-To determine if LDAP is being used for authentication, use the following command:
-
-# grep -i useldapauth /etc/sysconfig/authconfig
-USELDAPAUTH=yes
-
-If USELDAPAUTH=yes, then LDAP is being used.
-
-Check that the path to the X.509 certificate for peer authentication with the following command:
-
-# grep -i cacertfile /etc/pam_ldap.conf
-tls_cacertfile /etc/openldap/ldap-cacert.pem
-
-Verify the “tls_cacertfile” option points to a file that contains the trusted CA certificate.
-
-If this file does not exist, or the option is commented out or missing, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040190">
-    <title>SRG-OS-000163-GPOS-00072</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040190_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040190</version>
-      <title>All network connections associated with SSH traffic must terminate at the end of the session or after 10 minutes of inactivity, except to fulfill documented and validated mission requirements.</title>
-      <description>&lt;VulnDiscussion&gt;Terminating an idle SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle SSH session will also free up resources committed by the managed network element.
-
-Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.
-
-Satisfies: SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001133</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002361</ident>
-      <fixtext fixref="F-RHEL-07-040190_fix">Configure the operating system to automatically terminate a user session after inactivity time-outs have expired or at shutdown.
-
-Add the following line (or modify the line to have the required value) to the /etc/ssh/sshd_config file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
-
-ClientAliveInterval 600</fixtext>
-      <fix id="F-RHEL-07-040190_fix" />
-      <check system="C-RHEL-07-040190_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system automatically terminates a user session after inactivity time-outs have expired.
-
-Check for the value of the ClientAlive keyword with the following command:
-
-# grep -i clientalive /etc/ssh/sshd_config
-
-ClientAliveInterval 600
-
-If “ClientAliveInterval” is not set to “600” in /etc/ ssh/sshd_config, and a lower value is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040191">
-    <title>SRG-OS-000163-GPOS-00072</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040191_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040191</version>
-      <title>All network connections associated with SSH traffic must terminate after a period of inactivity.</title>
-      <description>&lt;VulnDiscussion&gt;Terminating an idle SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle SSH session will also free up resources committed by the managed network element.
-
-Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.
-
-Satisfies: SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001133</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002361</ident>
-      <fixtext fixref="F-RHEL-07-040191_fix">Configure the operating system to automatically terminate a user session after inactivity time-outs have expired or at shutdown.
-
-Add the following line (or modify the line to have the required value) to the /etc/ssh/sshd_config file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
-
-ClientAliveCountMax 0</fixtext>
-      <fix id="F-RHEL-07-040191_fix" />
-      <check system="C-RHEL-07-040191_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system automatically terminates a user session after inactivity time-outs have expired.
-
-Check for the value of the ClientAliveCountMax keyword with the following command:
-
-# grep -i clientalivecount /etc/ssh/sshd_config
-ClientAliveCountMax 0
-
-If “ClientAliveCountMax” is not set to “0” in /etc/ ssh/sshd_config, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040210">
-    <title>SRG-OS-000355-GPOS-00143</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040210_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040210</version>
-      <title>The operating system must, for networked systems, synchronize clocks with a server that is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, 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).
-
-Satisfies: SRG-OS-000355-GPOS-00143, SRG-OS-000355-GPOS-00144&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001891</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002046</ident>
-      <fixtext fixref="F-RHEL-07-040210_fix">Edit the "/etc/ntp.conf" file and add or update an entry to define "maxpoll" to "10" as follows:
-
-maxpoll 10
-
-If NTP was running and "maxpoll" was updated, the ntp service must be restarted:
-
-# systemctl restart ntpd
-
-If NTP was not running, it must be started:
-
-# systemctl start ntpd</fixtext>
-      <fix id="F-RHEL-07-040210_fix" />
-      <check system="C-RHEL-07-040210_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Check to see if ntp is running in continuous mode.
-
-# ps -ef | grep ntp
-
-If NTP is not running, this is a finding.
-
-If the process is found, then check the ntp.conf file for the “maxpoll” option setting:
-
-# grep maxpoll /etc/ntp.conf
-maxpoll 10
-
-If the file does not exist, this is a finding.
-
-If the option is set to “17” or is not set, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040230">
-    <title>SRG-OS-000384-GPOS-00167</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040230_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040230</version>
-      <title>The operating system, if using PKI-based authentication, must implement a local cache of revocation data to certificate validation 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001991</ident>
-      <fixtext fixref="F-RHEL-07-040230_fix">Configure the operating system, for PKI-based authentication, to implement a local cache of revocation data to support certificate validation in case of the inability to access revocation information via the network.
-
-Add the following lines to /var/lib/pki-kra/conf/server.xml (or modify the line to have the required value):
-
-auths.revocationChecking.bufferSize=50
-auths.revocationChecking.enabled=true
-
-Add the following lines to /var/lib/pki-kra/conf/server.xml (or modify the line to have the required value):
-
-enableOCSP="true"
-ocspCacheSize="50"</fixtext>
-      <fix id="F-RHEL-07-040230_fix" />
-      <check system="C-RHEL-07-040230_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system, for PKI-based authentication, implements a local cache of revocation data to support certificate validation in case of the inability to access revocation information via the network.
-
-Check to see if the certificate authority certificate revocation data cache is enabled on the system with the following command:
-
-# grep -i  revocationchecking /var/lib/pki-ca/conf/CS.cfg
-auths.revocationChecking.bufferSize=50
-auths.revocationChecking.ca=ca
-auths.revocationChecking.enabled=true
-auths.revocationChecking.unknownStateInterval=0
-auths.revocationChecking.validityInterval=120
-
-If auths.revocationChecking.enabled is not set to "true", this is a finding.
-
-If auths.revocationChecking.bufferSize is not set to a value of “50” or less, this is a finding.
-
-Check to see if the Online Certificate Status Protocol (OCSP) certificate revocation data cache is enabled on the system with the following command: 
-
-# grep -i ocsp /var/lib/pki-kra/conf/server.xml
-enableOCSP="true"
-ocspResponderURL="http://server.pki.mil:9180/ca/ocsp"
-      ocspResponderCertNickname="ocspSigningCert cert-pki-ca 102409a"
-        ocspCacheSize="50"
-        ocspMinCacheEntryDuration="60"
-        ocspMaxCacheEntryDuration="120"
-        ocspTimeout="10"
-
-If “enableOCSP” is not set to "true", this is a finding.
-
-If “ocspCacheSize” is not set to a value of “50” or less, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040250">
-    <title>SRG-OS-000420-GPOS-00186</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040250_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040250</version>
-      <title>The operating system must protect against or limit the effects of Denial of Service (DoS) attacks by validating the operating system is implementing rate-limiting measures on impacted network interfaces.</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.
-
-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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002385</ident>
-      <fixtext fixref="F-RHEL-07-040250_fix">Create a direct firewall rule to protect against DoS attacks with the following command:
-
-# firewall-cmd --direct --add-rule ipv4 filter IN_public_allow 0 -m tcp -p tcp -m limit --limit 25/minute --limit-burst 100  -j ACCEPT</fixtext>
-      <fix id="F-RHEL-07-040250_fix" />
-      <check system="C-RHEL-07-040250_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system protects against or limits the effects of DoS attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces.
-
-Check the firewall configuration with the following command:
-
-# firewall-cmd --direct --get-rule ipv4 filter IN_public_allow
-rule ipv4 filter IN_public_allow 0 -m tcp -p tcp -m limit --limit 25/minute --limit-burst 100  -j ACCEPT
-
-If a rule with both the limit and limit-burst arguments parameters does not exist, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040260">
-    <title>SRG-OS-000423-GPOS-00187</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040260_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040260</version>
-      <title>All networked systems 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, logical means (cryptography) do not have to be employed, and vice versa.
-
-Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000423-GPOS-00188, SRG-OS-000423-GPOS-00189, SRG-OS-000423-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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002418</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002421</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002420</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002422</ident>
-      <fixtext fixref="F-RHEL-07-040260_fix">Install SSH packages onto the host with the following commands:
-
-# yum install openssh-clients.x86_64
-# yum install openssh-server.x86_64
-
-Note: 32-bit versions will require different packages.</fixtext>
-      <fix id="F-RHEL-07-040260_fix" />
-      <check system="C-RHEL-07-040260_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Check to see if sshd is installed with the following command:
-
-# yum list installed | grep ssh
-libssh2.x86_64                           1.4.3-8.el7               @anaconda/7.1
-openssh.x86_64                           6.6.1p1-11.el7            @anaconda/7.1
-openssh-clients.x86_64                   6.6.1p1-11.el7            @anaconda/7.1
-openssh-server.x86_64                    6.6.1p1-11.el7            @anaconda/7.1
-
-If the “SSH server” package is not installed, this is a finding.
-
-If the “SSH client” package is not installed, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040261">
-    <title>SRG-OS-000423-GPOS-00187</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040261_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040261</version>
-      <title>All networked systems must use SSH for confidentiality and integrity of transmitted and received information as well as information during preparation for transmission.</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-000423-GPOS-00188, SRG-OS-000423-GPOS-00189, SRG-OS-000423-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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-002418</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002421</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002420</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-002422</ident>
-      <fixtext fixref="F-RHEL-07-040261_fix">Configure the SSH service to automatically start after reboot with the following command:
-
-# systemctl enable sshd ln -s '/usr/lib/systemd/system/sshd.service' '/etc/systemd/system/multi-user.target.wants/sshd.service'</fixtext>
-      <fix id="F-RHEL-07-040261_fix" />
-      <check system="C-RHEL-07-040261_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify SSH is loaded and active with the following command:
-
-# systemctl status sshd
- sshd.service - OpenSSH server daemon
-   Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
-   Active: active (running) since Tue 2015-11-17 15:17:22 EST; 4 weeks 0 days ago
- Main PID: 1348 (sshd)
-   CGroup: /system.slice/sshd.service
-           ??1348 /usr/sbin/sshd -D
-
-If “sshd” does not show a status of “active” and “running”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040290">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040290_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040290</version>
-      <title>The operating system must enable an application firewall, if available.</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.
-
-Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000480-GPOS-00231, SRG-OS-000480-GPOS-00232&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040290_fix">Ensure the operating system's application firewall is enabled.
-
-Install the “firewalld” package if it is not on the system with the following command:
-
-# yum install firewalld
-
-Start the firewall via systemctl with the following command:
-
-# systemctl start firewalld</fixtext>
-      <fix id="F-RHEL-07-040290_fix" />
-      <check system="C-RHEL-07-040290_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the operating system enabled an application firewall.
-
-Check to see if "firewalld" is installed with the following command:
-
-# yum list installed | grep firewalld
-firewalld-0.3.9-11.el7.noarch.rpm
-
-If the “firewalld” package is not installed, ask the system administrator if another firewall application (such as iptables) is installed. If an application firewall is not installed, this is a finding. 
-
-Check to see if the firewall is loaded and active with the following command:
-
-# systemctl status firewalld - must show that the firewall if loaded and active
-firewalld.service - firewalld - dynamic firewall daemon
-
-   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
-   Active: active (running) since Tue 2014-06-17 11:14:49 CEST; 5 days ago
-
-If “firewalld” does not show a status of “loaded and active”, this is a finding. 
-
-Check the state of the firewall:
-
-# firewall-cmd --state 
-running
-
-If “firewalld” does not show a state of “running”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040300">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040300_rule" severity="low" weight="10.0">
-      <version>RHEL-07-040300</version>
-      <title>The system must display the date and time of the last successful account logon upon logon.</title>
-      <description>&lt;VulnDiscussion&gt;Providing users with feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040300_fix">Configure the operating system to provide users with feedback on when account accesses last occurred by setting the required configuration options in “/etc/pam.d/postlogin”. 
-
-Add the following line to the top of “/etc/pam.d/postlogin”:
-
-session     required      pam_lastlog.so showfailed</fixtext>
-      <fix id="F-RHEL-07-040300_fix" />
-      <check system="C-RHEL-07-040300_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that users are provided with feedback on when account accesses last occurred.
-
-Check that “pam_lastlog” is used and not silent with the following command:
-
-# grep pam_lastlog /etc/pam.d/postlogin
-
-session     required      pam_lastlog.so showfailed silent
-
-If “pam_lastlog” is missing from “/etc/pam.d/postlogin” file, or the silent option is present on the line check for the “PrintLastLog” keyword in the sshd daemon configuration file, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040301">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040301_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040301</version>
-      <title>The system must display the date and time of the last successful account logon upon an SSH logon.</title>
-      <description>&lt;VulnDiscussion&gt;Providing users with feedback on when account accesses via SSH last occurred facilitates user recognition and reporting of unauthorized account use.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040301_fix">Configure SSH to provide users with feedback on when account accesses last occurred by setting the required configuration options in “/etc/pam.d/sshd” or in the “sshd_config” file used by the system (/etc/ssh/sshd_config will be used in the example) (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor).
-
-Add the following line to the top of “/etc/pam.d/sshd”:
-
-session     required      pam_lastlog.so showfailed
-
-Or modify the PrintLastLog line in “/etc/ssh/sshd_config” to match the following:
-
-PrintLastLog yes</fixtext>
-      <fix id="F-RHEL-07-040301_fix" />
-      <check system="C-RHEL-07-040301_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify SSH provides users with feedback on when account accesses last occurred.
-
-Check that “PrintLastLog” keyword in the sshd daemon configuration file is used and set to “yes” with the following command:
-
-# grep -i printlastlog /etc/ssh/sshd_config
-PrintLastLog yes
-
-If the “PrintLastLog” keyword is set to “no”, is missing, or is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040310">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040310_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040310</version>
-      <title>The system must not permit direct logons to the root account using remote access via SSH.</title>
-      <description>&lt;VulnDiscussion&gt;Even though the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging on directly as root. In addition, logging on with a user-specific account provides individual accountability of actions performed on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040310_fix">Configure SSH to stop users from logging on remotely as the root user.
-
-Edit the appropriate  /etc/ssh/sshd_config file to uncomment or add the line for the PermitRootLogin keyword and set its value to “no” (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
-
-PermitRootLogin no</fixtext>
-      <fix id="F-RHEL-07-040310_fix" />
-      <check system="C-RHEL-07-040310_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify remote access using SSH prevents users from logging on directly as root.
-
-Check that SSH prevents users from logging on directly as root with the following command:
-
-# grep -i permitrootlogin /etc/ssh/sshd_config
-PermitRootLogin no
-
-If the “PermitRootLogin” keyword is set to “yes”, is missing, or is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040320">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040320_rule" severity="low" weight="10.0">
-      <version>RHEL-07-040320</version>
-      <title>For systems using DNS resolution, at least two name servers must be configured.</title>
-      <description>&lt;VulnDiscussion&gt;To provide availability for name resolution services, multiple redundant name servers are mandated. A failure in name resolution could lead to the failure of security functions requiring name resolution, which may include time synchronization, centralized authentication, and remote system logging.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040320_fix">Configure the operating system to use two or more name servers for DNS resolution.
-
-Edit the “/etc/resolv.conf” file to uncomment or add the two or more nameserver option lines with the IP address of local authoritative name servers. If local host resolution is being performed, the “/etc/resolv.conf” file must be empty. An empty “/etc/resolv.conf” file can be created as follows:
-
-# echo -n &gt; /etc/resolv.conf
-And then make the file immutable with the following command:
-# chattr +i /etc/resolv.conf</fixtext>
-      <fix id="F-RHEL-07-040320_fix" />
-      <check system="C-RHEL-07-040320_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Determine whether the system is using local or DNS name resolution with the following command:
-
-# grep hosts /etc/nsswitch.conf
-hosts:   files dns
-
-If the dns entry is missing from the host’s line in the “/etc/nsswitch.conf” file, the “/etc/resolv.conf” file must be empty.
-
-Verify the “/etc/resolv.conf” file is empty with the following command:
-
-# l s -al /etc/resolv.conf
--rw-r--r--  1 root root        0 Aug 19 08:31 resolv.conf
-
-If local host authentication is being used and the “/etc/resolv.conf” file is not empty, this is a finding.
-
-If the dns entry is found on the host’s line of the “/etc/nsswitch.conf” file, verify the operating system is configured to use two or more name servers for DNS resolution.
-
-Determine the name servers used by the system with the following command:
-
-# grep nameserver /etc/resolv.conf
-nameserver 192.168.1.2
-nameserver 192.168.1.3
-
-If less than two lines are returned that are not commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040330">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040330_rule" severity="high" weight="10.0">
-      <version>RHEL-07-040330</version>
-      <title>There must be no .shosts files on the system.</title>
-      <description>&lt;VulnDiscussion&gt;The .shosts files are used to configure host-based authentication for individual users or the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040330_fix">Remove any found .shosts files from the system.
-
-# rm /[path]/[to]/[file]/.shosts</fixtext>
-      <fix id="F-RHEL-07-040330_fix" />
-      <check system="C-RHEL-07-040330_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify there are no .shosts files on the system.
-
-Check the system for the existence of these files with the following command:
-
-# find / -name '*.shosts’
-
-If any .shosts files are found on the system, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040331">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040331_rule" severity="high" weight="10.0">
-      <version>RHEL-07-040331</version>
-      <title>There must be no shosts.equiv files on the system.</title>
-      <description>&lt;VulnDiscussion&gt;The shosts.equiv files are used to configure host-based authentication for the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040331_fix">Remove any found shosts.equiv files from the system.
-
-# rm /[path]/[to]/[file]/shosts.equiv</fixtext>
-      <fix id="F-RHEL-07-040331_fix" />
-      <check system="C-RHEL-07-040331_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify there are no shosts.equiv files on the system.
-
-Check the system for the existence of these files with the following command:
-
-# find / -name shosts.equiv
-
-If any shosts.equiv files are found on the system, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040334">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040334_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040334</version>
-      <title>The SSH daemon must not allow authentication using rhosts authentication.</title>
-      <description>&lt;VulnDiscussion&gt;Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040334_fix">Configure the SSH daemon to not allow authentication using known hosts authentication.
-
-Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to “yes”:
-
-IgnoreRhosts yes</fixtext>
-      <fix id="F-RHEL-07-040334_fix" />
-      <check system="C-RHEL-07-040334_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the SSH daemon does not allow authentication using known hosts authentication.
-
-To determine how the SSH daemon's "IgnoreRhosts" option is set, run the following command:
-
-# grep -i IgnoreRhosts /etc/ssh/sshd_config
-
-IgnoreRhosts yes
-
-If the value is returned as “no”, the returned line is commented out, or no output is returned, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040332">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040332_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040332</version>
-      <title>The SSH daemon must not allow authentication using known hosts authentication.</title>
-      <description>&lt;VulnDiscussion&gt;Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040332_fix">Configure the SSH daemon to not allow authentication using known hosts authentication.
-
-Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to yes:
-
-IgnoreUserKnownHosts yes</fixtext>
-      <fix id="F-RHEL-07-040332_fix" />
-      <check system="C-RHEL-07-040332_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the SSH daemon does not allow authentication using known hosts authentication.
-
-To determine how the SSH daemon's "IgnoreUserKnownHosts" option is set, run the following command:
-
-# grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config
-
-IgnoreUserKnownHosts yes
-
-If the value is returned as “no”, the returned line is commented out, or no output is returned, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040333">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040333_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040333</version>
-      <title>The SSH daemon must not allow authentication using RSA rhosts authentication.</title>
-      <description>&lt;VulnDiscussion&gt;Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040333_fix">Configure the SSH daemon to not allow authentication using RSA rhosts authentication.
-
-Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to yes:
-
-RhostsRSAAuthentication yes</fixtext>
-      <fix id="F-RHEL-07-040333_fix" />
-      <check system="C-RHEL-07-040333_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the SSH daemon does not allow authentication using RSA rhosts authentication.
-
-To determine how the SSH daemon's "RhostsRSAAuthentication" option is set, run the following command:
-
-# grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config
-
-RhostsRSAAuthentication yes
-
-If the value is returned as “no”, the returned line is commented out, or no output is returned, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040350">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040350_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040350</version>
-      <title>The system must not forward Internet Protocol version 4 (IPv4) source-routed packets.</title>
-      <description>&lt;VulnDiscussion&gt;Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040350_fix">Set the system to the required kernel parameter by adding the following line to /etc/sysctl.conf (or modify the line to have the required value):
-
-net.ipv4.conf.all.accept_source_route = 0</fixtext>
-      <fix id="F-RHEL-07-040350_fix" />
-      <check system="C-RHEL-07-040350_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system does not accept IPv4 source-routed packets.
-
-Check the value of the accept source route variable with the following command:
-
-# /sbin/sysctl -a | grep  net.ipv4.conf.all.accept_source_route
-net.ipv4.conf.all.accept_source_route=0
-
-If the returned line does not have a value of “0”, a line is not returned, or the returned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040351">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040351_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040351</version>
-      <title>The system must not forward Internet Protocol version 4 (IPv4) source-routed packets by default.</title>
-      <description>&lt;VulnDiscussion&gt;Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;NEW&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040351_fix">Set the system to the required kernel parameter by adding the following line to /etc/sysctl.conf (or modify the line to have the required value):
-
-net.ipv4.conf.default.accept_source_route = 0</fixtext>
-      <fix id="F-RHEL-07-040351_fix" />
-      <check system="C-RHEL-07-040351_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system does not accept IPv4 source-routed packets by default.
-
-Check the value of the accept source route variable with the following command:
-
-# /sbin/sysctl -a | grep  net.ipv4.conf.default.accept_source_route
-net.ipv4.conf.default.accept_source_route=0
-
-If the returned line does not have a value of “0”, a line is not returned, or the returned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040380">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040380_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040380</version>
-      <title>The system must not respond to Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) echoes sent to a broadcast address.</title>
-      <description>&lt;VulnDiscussion&gt;Responding to broadcast (ICMP) echoes facilitates network mapping and provides a vector for amplification 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040380_fix">Set the system to the required kernel parameter with the following command:
-
-# /sbin/sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1</fixtext>
-      <fix id="F-RHEL-07-040380_fix" />
-      <check system="C-RHEL-07-040380_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system does not respond to IPv4 ICMP echoes sent to a broadcast address.
-
-Check the value of the icmp_echo_ignore_broadcasts variable with the following command:
-
-# /sbin/sysctl -a | grep  net.ipv4.icmp_echo_ignore_broadcasts
-net.ipv4.icmp_echo_ignore_broadcasts=1
-
-If the returned line does not have a value of “1”, a line is not returned, or the retuned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040410">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040410_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040410</version>
-      <title>The system must ignore to Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages.</title>
-      <description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040410_fix">Set the system to the required kernel parameter by adding the following line to /etc/sysctl.conf (or modify the line to have the required value):
-
-net.ipv4.conf.all.accept_redirects = 0
-net.ipv4.conf.default.accept_redirects = 0</fixtext>
-      <fix id="F-RHEL-07-040410_fix" />
-      <check system="C-RHEL-07-040410_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system ignores IPv4 ICMP redirect messages.
-
-Check the value of the “accept_redirects” variables with the following command:
-
-# /sbin/sysctl -a | grep  'net.ipv4.conf.*.accept_redirects'
-net.ipv4.conf.default.accept_redirects=0
-net.ipv4.conf.all.accept_redirects=0
-
-If both of the returned line do not have a value of “0”, a line is not returned, or the retuned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040420">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040420_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040420</version>
-      <title>The system must not allow interfaces to perform Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects by default.</title>
-      <description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040420_fix">Configure the system to not allow interfaces to perform IPv4 ICMP redirects by default. 
-
-Set the system to the required kernel parameter by adding the following line to /etc/sysctl.conf (or modify the line to have the required value):
-
-net.ipv4.conf.default.send_redirects=0</fixtext>
-      <fix id="F-RHEL-07-040420_fix" />
-      <check system="C-RHEL-07-040420_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system does not allow interfaces to perform IPv4 ICMP redirects by default.
-
-Check the value of the "default send_redirects" variables with the following command:
-
-# /sbin/sysctl -a | grep  'net.ipv4.conf.default.send_redirects'
-net.ipv4.conf.default.send_redirects=0
-
-If the returned line does not have a value of “0”, a line is not returned, or the retuned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040421">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040421_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040421</version>
-      <title>The system must not send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects.</title>
-      <description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040421_fix">Configure the system to not allow interfaces to perform IPv4 ICMP redirects. 
-
-Set the system to the required kernel parameter by adding the following line to /etc/sysctl.conf (or modify the line to have the required value):
-
-net.ipv4.conf.all.send_redirects=0</fixtext>
-      <fix id="F-RHEL-07-040421_fix" />
-      <check system="C-RHEL-07-040421_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system does not send IPv4 ICMP redirect messages.
-
-Check the value of the "all send_redirects" variables with the following command:
-
-# /sbin/sysctl -a | grep  net.ipv4.conf.all.send_redirects
-
-net.ipv4.conf.all.send_redirects=0
-
-If the returned line does not have a value of “0”, a line is not returned, or the retuned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040470">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040470_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040470</version>
-      <title>Network interfaces must not be in promiscuous mode.</title>
-      <description>&lt;VulnDiscussion&gt;Network interfaces in promiscuous mode allow for the capture of all network traffic visible to the system. If unauthorized individuals can access these applications, it may allow then to collect information such as logon IDs, passwords, and key exchanges between systems.
-
-If the system is being used to perform a network troubleshooting function, the use of these tools must be documented with the Information System Security Manager (ISSM) and restricted to only authorized personnel.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040470_fix">Configure network interfaces to turn off promiscuous mode unless approved by the ISSM and documented.
-
-Set the promiscuous mode of an interface to off with the following command:
-
-#ip link set dev &lt;devicename&gt; multicast off promisc off</fixtext>
-      <fix id="F-RHEL-07-040470_fix" />
-      <check system="C-RHEL-07-040470_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify network interfaces are not in promiscuous mode unless approved by the Information System Security Manager (ISSM) and documented.
-
-Check for the status with the following command:
-
-# ip link | grep -i promisc
-
-If network interfaces are found on the system in promiscuous mode and their use has not been approved by the ISSM and documented, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040480">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040480_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040480</version>
-      <title>The system must be configured to prevent unrestricted mail relaying.</title>
-      <description>&lt;VulnDiscussion&gt;If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending spam or other unauthorized activity.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040480_fix">If “postfix” is installed, modify the “/etc/postfix/main.cf” file to restrict client connections to the local network with the following configuration line:
-
-smtpd_client_restrictions = permit_mynetworks, reject</fixtext>
-      <fix id="F-RHEL-07-040480_fix" />
-      <check system="C-RHEL-07-040480_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system is configured to prevent unrestricted mail relaying.
-
-Determine if "postfix" or "sendmail" are installed with the following commands:
-
-# yum list installed | grep postfix
-postfix-2.6.6-6.el7.x86_64.rpm 
-# yum list installed | grep sendmail
-
-If neither are installed, this is Not Applicable.
-
-If postfix is installed, determine if it is configured to reject connections from unknown or untrusted networks with the following command:
-
-# grep smtpd_client_restrictions /etc/postfix/main.cf
-smtpd_client_restrictions = permit_mynetworks, reject
-
-If the “smtpd_client_restrictions” parameter contains any entries other than "permit_mynetworks" and "reject", this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040490">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040490_rule" severity="high" weight="10.0">
-      <version>RHEL-07-040490</version>
-      <title>A File Transfer Protocol (FTP) server package must not be installed unless needed.</title>
-      <description>&lt;VulnDiscussion&gt;The FTP service provides an unencrypted remote access that does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to log on using this service, the privileged user password could be compromised. SSH or other encrypted file transfer methods must be used in place of this service.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040490_fix">Document the "lftpd" package with the ISSO as an operational requirement or remove it from the system with the following command:
-
-# yum remove lftpd</fixtext>
-      <fix id="F-RHEL-07-040490_fix" />
-      <check system="C-RHEL-07-040490_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify a lightweight FTP server has not been installed on the system.
-
-Check to see if a lightweight FTP server has been installed with the following commands:
-
-# yum list installed | grep lftpd
- lftp-4.4.8-7.el7.x86_64.rpm
-
-An alternate method of determining if a lightweight FTP server is active on the server is to use the following command:
-
-# netstat -a | grep 21
-
-If “lftpd” is installed, or if an application is listening on port 21, and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040500">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040500_rule" severity="high" weight="10.0">
-      <version>RHEL-07-040500</version>
-      <title>The Trivial File Transfer Protocol (TFTP) server package must not be installed if not required for operational support.</title>
-      <description>&lt;VulnDiscussion&gt;If TFTP is required for operational support (such as the transmission of router configurations) its use must be documented with the Information System Security Manager (ISSM), restricted to only authorized personnel, and have access control rules established.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
-      <fixtext fixref="F-RHEL-07-040500_fix">Remove the TFTP package from the system with the following command:
-
-# yum remove tftp</fixtext>
-      <fix id="F-RHEL-07-040500_fix" />
-      <check system="C-RHEL-07-040500_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify a TFTP server has not been installed on the system.
-
-Check to see if a TFTP server has been installed with the following command:
-
-# yum list installed | grep tftp-server
-tftp-server-0.49-9.el7.x86_64.rpm
-
-An alternate method of determining if a TFTP server is active on the server is to use the following commands:
-
-# netstat -a | grep 69
-# netstat -a | grep 8099
-
-If TFTP is installed and the requirement for TFTP is not documented with the ISSM, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040520">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040520_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040520</version>
-      <title>If the Trivial File Transfer Protocol (TFTP) server is required, the TFTP daemon must be configured to operate in secure mode.</title>
-      <description>&lt;VulnDiscussion&gt;Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040520_fix">Configure the TFTP daemon to operate in secure mode by adding the following line to /etc/xinetd.d/tftp (or modify the line to have the required value):
-
-server_args = -s /var/lib/tftpboot</fixtext>
-      <fix id="F-RHEL-07-040520_fix" />
-      <check system="C-RHEL-07-040520_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the TFTP daemon is configured to operate in secure mode.
-
-Check to see if a TFTP server has been installed with the following commands:
-
-# yum list installed | grep tftp
-tftp-0.49-9.el7.x86_64.rpm
-
-If a TFTP server is not installed, this is Not Applicable.
-
-If a TFTP server is installed, check for the server arguments with the following command: 
-
-# grep server_arge /etc/xinetd.d/tftp
-server_args = -s /var/lib/tftpboot
-
-If the “server_args” line does not have a -s option and the directory /var/lib/tftpboot, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040540">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040540_rule" severity="high" weight="10.0">
-      <version>RHEL-07-040540</version>
-      <title>Remote X connections for interactive users must be encrypted.</title>
-      <description>&lt;VulnDiscussion&gt;Open X displays allow an attacker to capture keystrokes and execute commands remotely.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040540_fix">Configure SSH to encrypt connections for interactive users.
-
-Edit the /etc/ssh/sshd_config file to uncomment or add the line for the X11Forwarding keyword and set its value to “yes” (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
-
-X11Fowarding yes</fixtext>
-      <fix id="F-RHEL-07-040540_fix" />
-      <check system="C-RHEL-07-040540_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify remote X connections for interactive users are encrypted.
-
-Check that remote X connections are encrypted with the following command:
-
-# grep -i x11forwarding /etc/ssh/sshd_config
-X11Fowarding yes
-
-If the X11Forwarding keyword is set to "no", is missing, or is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040560">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040560_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040560</version>
-      <title>An X Windows display manager must not be installed unless approved.</title>
-      <description>&lt;VulnDiscussion&gt;Internet services that are not required for system or application processes must not be active to decrease the attack surface of the system. X Windows has a long history of security vulnerabilities and will not be used unless approved and documented.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040560_fix">Document the requirement for an X Windows server with the ISSM or remove the related packages with the following commands:
-
-#yum groupremove "X Window System"
-
-#yum remove xorg-x11-server-common</fixtext>
-      <fix id="F-RHEL-07-040560_fix" />
-      <check system="C-RHEL-07-040560_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that if the system has X Windows installed, it is authorized.
-
-Check for the X11 package with the following command:
-
-#yum groupinstall "X Window System"
-
-Ask the System Administrator (SA) if use of the X Windows system is an operational requirement.
-
-If the use of X Windows on the system is not documented with the Information System Security Manager (ISSM), this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040580">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040580_rule" severity="high" weight="10.0">
-      <version>RHEL-07-040580</version>
-      <title>SNMP community strings must be changed from the default.</title>
-      <description>&lt;VulnDiscussion&gt;Whether active or not, default Simple Network Management Protocol (SNMP) community strings must be changed to maintain security. If the service is running with the default authenticators, anyone can gather data about the system and the network and use the information to potentially compromise the integrity of the system or network(s). It is highly recommended that SNMP version 3 user authentication and message encryption be used in place of the version 2 community strings.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040580_fix">If the “/etc/snmp/snmpd.conf” file exists, modify any lines that contain a community string of public or private to another string.</fixtext>
-      <fix id="F-RHEL-07-040580_fix" />
-      <check system="C-RHEL-07-040580_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that a system using SNMP is not using default community strings.
-
-Check to see if the “/etc/snmp/snmpd.conf” file exists with the following command:
-
-# ls -al /etc/snmp/snmpd.conf
- -rw-------   1 root root      52640 Mar 12 11:08 snmpd.conf
-
-If the file does not exist, this is Not Applicable.
-
-If the file does exist, check for the default community strings with the following commands:
-
-# grep public /etc/snmp/snmpd.conf
-# grep private /etc/snmp/snmpd.conf
-
-If either of these command returns any output, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040590">
-    <title>SRG-OS-000074-GPOS-00042</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040590_rule" severity="high" weight="10.0">
-      <version>RHEL-07-040590</version>
-      <title>The SSH daemon must be configured to only use the SSHv2 protocol.</title>
-      <description>&lt;VulnDiscussion&gt;SSHv1 is an insecure implementation of the SSH protocol and has many well-known vulnerability exploits. Exploits of the SSH daemon could provide immediate root access to the system.
-
-Satisfies: SRG-OS-000074-GPOS-00042, SRG-OS-000480-GPOS-00227&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000197</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040590_fix">Remove all Protocol lines that reference version 1 in /etc/ssh/sshd_config (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor). The "Protocol" line must be as follows:
-
-Protocol 2</fixtext>
-      <fix id="F-RHEL-07-040590_fix" />
-      <check system="C-RHEL-07-040590_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the SSH daemon is configured to only use the SSHv2 protocol.
-
-Check that the SSH daemon is configured to only use the SSHv2 protocol with the following command:
-
-# grep -i protocol /etc/ssh/sshd_config
-Protocol 2
-#Protocol 1,2
-
-If any protocol line other than "Protocol 2" is uncommented, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040620">
-    <title>SRG-OS-000250-GPOS-00093</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040620_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040620</version>
-      <title>The SSH daemon must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms.</title>
-      <description>&lt;VulnDiscussion&gt;DoD information systems are required to use FIPS 140-2 approved cryptographic hash functions. The only SSHv2 hash algorithm meeting this requirement is SHA.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-001453</ident>
-      <fixtext fixref="F-RHEL-07-040620_fix">Edit the /etc/ssh/sshd_config file to uncomment or add the line for the MACs keyword and set its value to “hmac-sha2-256” and/or “hmac-sha2-512 “(this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
-
-MACs hmac-sha2-256,hmac-sha2-512</fixtext>
-      <fix id="F-RHEL-07-040620_fix" />
-      <check system="C-RHEL-07-040620_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the SSH daemon is configured to only use MACs employing FIPS 140-2 approved ciphers.
-
-Note: If RHEL-07-021280 is a finding, this is automatically a finding as the system cannot implement FIPS 140-2 approved cryptographic algorithms and hashes.
-
-Check that the SSH daemon is configured to only use MACs employing FIPS 140-2 approved ciphers with the following command:
-
-# grep -i macs /etc/ssh/sshd_config
-MACs hmac-sha2-256,hmac-sha2-512
-
-If any ciphers other than “hmac-sha2-256” or “hmac-sha2-512” are listed or the retuned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040640">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040640_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040640</version>
-      <title>The SSH public host key files must have mode 0644 or less permissive.</title>
-      <description>&lt;VulnDiscussion&gt;If a public host key file is modified by an unauthorized user, the SSH service may 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;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040640_fix">Note: SSH public key files may be found in other directories on the system depending on the installation. 
-
-The following command will find all SSH public key files on the system:
-
-# find / -name ‘*key.pub’
-
-Change the mode of public host key files under “/etc/ssh” to “0644” with the following command:
-
-# chmod 0644 /etc/ssh/*.key.pub</fixtext>
-      <fix id="F-RHEL-07-040640_fix" />
-      <check system="C-RHEL-07-040640_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the SSH public host key files have mode “0644” or less permissive.
-
-Note: SSH public key files may be found in other directories on the system depending on the installation.
-
-The following command will find all SSH public key files on the system:
-
-# find / -name '*.pub'
-
-Check the mode of the public host key files under /etc/ssh file with the following command:
-
-# ls -lL /etc/ssh/*.pub
--rw-r--r--  1 root  wheel  618 Nov 28 06:43 ssh_host_dsa_key.pub
--rw-r--r--  1 root  wheel  347 Nov 28 06:43 ssh_host_key.pub
--rw-r--r--  1 root  wheel  238 Nov 28 06:43 ssh_host_rsa_key.pub
-
-If any file has a mode more permissive than “0644”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040650">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040650_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040650</version>
-      <title>The SSH private host key files must have mode 0600 or less permissive.</title>
-      <description>&lt;VulnDiscussion&gt;If an unauthorized user obtains the private SSH host key file, the host could be impersonated.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040650_fix">Configure the mode of SSH private host key files under “/etc/ssh” to “0600” with the following command:
-
-# chmod 0600 /etc/ssh/ssh_host*key</fixtext>
-      <fix id="F-RHEL-07-040650_fix" />
-      <check system="C-RHEL-07-040650_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the SSH private host key files have mode “0600” or less permissive.
-
-The following command will find all SSH private key files on the system:
-
-# find / -name '*ssh_host*key'
-
-Check the mode of the private host key files under /etc/ssh file with the following command:
-
-# ls -lL /etc/ssh/*key
--rw-------  1 root  wheel  668 Nov 28 06:43 ssh_host_dsa_key
--rw-------  1 root  wheel  582 Nov 28 06:43 ssh_host_key
--rw-------  1 root  wheel  887 Nov 28 06:43 ssh_host_rsa_key
-
-If any file has a mode more permissive than “0600”, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040660">
-    <title>SRG-OS-000364-GPOS-00151</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040660_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040660</version>
-      <title>The SSH daemon must not permit Generic Security Service Application Program Interface (GSSAPI) authentication unless needed.</title>
-      <description>&lt;VulnDiscussion&gt;GSSAPI authentication is used to provide additional authentication mechanisms to applications. Allowing GSSAPI authentication through SSH exposes the system’s GSSAPI to remote hosts, increasing the attack surface of the system. GSSAPI authentication must be disabled unless needed.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
-      <fixtext fixref="F-RHEL-07-040660_fix">Uncomment the “GSSAPIAuthentication” keyword in /etc/ssh/sshd_config (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) and set the value to "no": 
-
-GSSAPIAuthentication no
-
-If GSSAPI authentication is required, it must be documented, to include the location of the configuration file, with the ISSO.</fixtext>
-      <fix id="F-RHEL-07-040660_fix" />
-      <check system="C-RHEL-07-040660_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the SSH daemon does not permit GSSAPI authentication unless approved.
-
-Check that the SSH daemon does not permit GSSAPI authentication with the following command:
-
-# grep -i gssapiauth /etc/ssh/sshd_config
-GSSAPIAuthentication no
-
-If the “GSSAPIAuthentication” keyword is missing, is set to “yes” and is not documented with the Information System Security Officer (ISSO), or the returned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040670">
-    <title>SRG-OS-000364-GPOS-00151</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040670_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040670</version>
-      <title>The SSH daemon must not permit Kerberos authentication unless needed.</title>
-      <description>&lt;VulnDiscussion&gt;Kerberos authentication for SSH is often implemented using Generic Security Service Application Program Interface (GSSAPI). If Kerberos is enabled through SSH, the SSH daemon provides a means of access to the system's Kerberos implementation. Vulnerabilities in the system's Kerberos implementation may then be subject to exploitation. To reduce the attack surface of the system, the Kerberos authentication mechanism within SSH must be disabled for systems not using this capability.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
-      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
-      <fixtext fixref="F-RHEL-07-040670_fix">Uncomment the “KerberosAuthentication” keyword in /etc/ssh/sshd_config (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) and set the value to "no":
-
-KerberosAuthentication no
-
-If Kerberos authentication is required, it must be documented, to include the location of the configuration file, with the ISSO.</fixtext>
-      <fix id="F-RHEL-07-040670_fix" />
-      <check system="C-RHEL-07-040670_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the SSH daemon does not permit Kerberos to authenticate passwords unless approved.
-
-Check that the SSH daemon does not permit Kerberos to authenticate passwords with the following command:
-
-# grep -i kerberosauth /etc/ssh/sshd_config
-KerberosAuthentication no
-
-If the “KerberosAuthentication” keyword is missing, or is set to "yes" and is not documented with the Information System Security Officer (ISSO), or the returned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040680">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040680_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040680</version>
-      <title>The SSH daemon must perform strict mode checking of home directory configuration files.</title>
-      <description>&lt;VulnDiscussion&gt;If other users have access to modify user-specific SSH configuration files, they may be able to log on to the system as another user.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040680_fix">Uncomment the “StrictModes” keyword in /etc/ssh/sshd_config (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) and set the value to "yes":
-
-StrictModes yes</fixtext>
-      <fix id="F-RHEL-07-040680_fix" />
-      <check system="C-RHEL-07-040680_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the SSH daemon performs strict mode checking of home directory configuration files.
-
-The location of the sshd_config file may vary on the system and can be found using the following command:
-
-# find / -name 'sshd*_config' 
-
-If there is more than one ssh server daemon configuration file on the system, determine which daemons are active on the system with the following command:
-
-# ps -ef | grep sshd
-
-The command will return the full path of the ssh daemon. This will indicate which sshd_config file will be checked with the following command:
-
-# grep -i strictmodes /etc/ssh/sshd_config
-StrictModes yes
-
-If “StrictModes” is set to "no", is missing, or the retuned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040690">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040690_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040690</version>
-      <title>The SSH daemon must use privilege separation.</title>
-      <description>&lt;VulnDiscussion&gt;SSH daemon privilege separation causes the SSH process to drop root privileges when not needed, which would decrease the impact of software vulnerabilities in the unprivileged section.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040690_fix">Uncomment the “UsePrivilegeSeparation” keyword in /etc/ssh/sshd_config (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) and set the value to "yes":
-
-UsePrivilegeSeparation yes</fixtext>
-      <fix id="F-RHEL-07-040690_fix" />
-      <check system="C-RHEL-07-040690_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the SSH daemon performs privilege separation.
-
-Check that the SSH daemon performs privilege separation with the following command:
-
-# grep -i usepriv /etc/ssh/sshd_config
-UsePrivilegeSeparation yes
-
-If the “UsePrivilegeSeparation” keyword is set to "no", is missing, or the retuned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040700">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040700_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040700</version>
-      <title>The SSH daemon must not allow compression or must only allow compression after successful authentication.</title>
-      <description>&lt;VulnDiscussion&gt;If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the system from an unauthenticated connection, potentially with root privileges.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040700_fix">Uncomment the “Compression” keyword in /etc/ssh/sshd_config (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) on the system and set the value to "delayed" or "no":
-
-Compression no</fixtext>
-      <fix id="F-RHEL-07-040700_fix" />
-      <check system="C-RHEL-07-040700_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the SSH daemon performs compression after a user successfully authenticates.
-
-Check that the SSH daemon performs compression after a user successfully authenticates with the following command:
-
-# grep -i compression /etc/ssh/sshd_config
-Compression delayed
-
-If the “Compression” keyword is set to “yes”, is missing, or the retuned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040730">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040730_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040730</version>
-      <title>The system must not be performing packet forwarding unless the system is a router.</title>
-      <description>&lt;VulnDiscussion&gt;Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040730_fix">Set the system to the required kernel parameter by adding the following line to /etc/sysctl.conf (or modify the line to have the required value):
-
-net.ipv4.ip_forward = 0</fixtext>
-      <fix id="F-RHEL-07-040730_fix" />
-      <check system="C-RHEL-07-040730_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system is not performing packet forwarding, unless the system is a router.
-
-Check to see if IP forwarding is enabled using the following command:
-
-# /sbin/sysctl -a | grep  net.ipv4.ip_forward
-net.ipv4.ip_forward=0
-
-If IP forwarding value is “1” and the system is hosting any application, database, or web servers, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040740">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040740_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040740</version>
-      <title>The Network File System (NFS) must be configured to use AUTH_GSS.</title>
-      <description>&lt;VulnDiscussion&gt;When an NFS server is configured to use AUTH_SYS, a selected userid and groupid are used to handle requests from the remote user. The userid and groupid could mistakenly or maliciously be set incorrectly. The AUTH_GSS method of authentication uses certificates on the server and client systems to more securely authenticate the remote mount request.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040740_fix">Update the “/etc/fstab” file so the option “sec” is defined for each file system and the “sec” option does not have the “sys” setting. 
-
-Ensure the “sec” option is defined as “krb5:krb5i:krb5p”.</fixtext>
-      <fix id="F-RHEL-07-040740_fix" />
-      <check system="C-RHEL-07-040740_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify “AUTH_GSS’ is being used to authenticate NFS mounts.
-
-To check if the system is importing an NFS file system, look for any entries in the “/etc/fstab” file that have a file system type of “nfs” with the following command:
-
-# cat /etc/fstab | grep nfs
-192.168.21.5:/mnt/export /data1 nfs4 rw,sync ,soft,sec=sys, krb5:krb5i:krb5p
-
-If the system is mounting file systems via NFS and has the sec option without the “krb5:krb5i:krb5p” settings, the sec option has the “sys” setting, or the “sec” option is missing, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040810">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040810_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040810</version>
-      <title>The system must use a local firewall.</title>
-      <description>&lt;VulnDiscussion&gt;A firewall provides the ability to enhance system security posture by restricting services to known good IP addresses and address ranges. This prevents connections from unknown hosts and protocols.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040810_fix">Install “firewalld” on the system if it is not already installed with the following command:
-
-# yum install firewalld firewall-config
-
-Enable firewalld with the following command:
-
-#systemctl enable firewalld</fixtext>
-      <fix id="F-RHEL-07-040810_fix" />
-      <check system="C-RHEL-07-040810_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify that a firewall is in use on the system.
-
-Check to see if “firewalld” is installed with the following command:
-
-# yum list installed | grep firewalld
-
-If “firewalld” is not installed, ask the System Administrator if they are performing another method of access control (such as iptables) for all network services on the system. 
-
-If there is no access control being performed on all network services, this is a finding.
-
-If “firewalld” is installed, determine whether it is active with the following command:
-
-# systemctl status firewalld
-firewalld.service - firewalld - dynamic firewall daemon
-   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
-   Active: active (running) since Sun 2014-04-20 14:06:46 BST; 30s ago
-
-If “firewalld” is not active, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040820">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040820_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040820</version>
-      <title>The system's access control program must be configured to grant or deny system access to specific hosts and services.</title>
-      <description>&lt;VulnDiscussion&gt;If the systems access control program is not configured with appropriate rules for allowing and denying access to system network resources, services may be accessible to unauthorized hosts.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040820_fix">If “firewalld” is installed and active on the system, configure rules for allowing specific services and hosts. 
-
-If “tcpwrappers” is installed. configure the “/etc/hosts.allow” and “/etc/hosts.deny” to allow or deny access to specific hosts.</fixtext>
-      <fix id="F-RHEL-07-040820_fix" />
-      <check system="C-RHEL-07-040820_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>If the “firewalld” package is not installed, ask the System Administrator if another firewall application (such as iptables) is installed. If an application firewall is not installed, this is a finding. 
-
-Verify the system's access control program is configured to grant or deny system access to specific hosts.
-
-Check to see if “firewalld” is active with the following command:
-
-# systemctl status firewalld
-firewalld.service - firewalld - dynamic firewall daemon
-   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
-   Active: active (running) since Sun 2014-04-20 14:06:46 BST; 30s ago
-
-If “firewalld” is active, check to see if it is configured to grant or deny access to specific hosts or services with the following commands:
-
-# firewall-cmd --get-default-zone
-public
-
-# firewall-cmd --list-all --zone=public
-public (default, active)
-  interfaces: eth0
-  sources:
-  services: mdns ssh
-  ports:
-  masquerade: no
-  forward-ports:
-  icmp-blocks:
-  rich rules:
- rule family="ipv4" source address="92.188.21.1/24" accept
- rule family="ipv4" source address="211.17.142.46/32" accept
-
-If “firewalld” is not active, determine whether “tcpwrappers” is being used by checking whether the “hosts.allow” and “hosts.deny” files are empty with the following commands:
-
-# ls -al /etc/hosts.allow
-rw-r----- 1 root root 9 Aug  2 23:13 /etc/hosts.allow
- 
-# ls -al /etc/hosts.deny
--rw-r----- 1 root root  9 Apr  9  2007 /etc/hosts.deny
-
-If “firewalld” and “tcpwrappers” are not installed, configured, and active, ask the System Administrator (SA) if another access control program (such as iptables) is installed and active. Ask the SA to show that the running configuration grants or denies access to specific hosts or services.
-
-If “firewalld” is active and is not configured to grant access to specific hosts and “tcpwrappers” is not configured to grant or deny access to specific hosts, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040830">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040830_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040830</version>
-      <title>The system must not have unauthorized IP tunnels configured.</title>
-      <description>&lt;VulnDiscussion&gt;IP tunneling mechanisms can be used to bypass network filtering. If tunneling is required, it must be documented with the Information System Security Officer (ISSO).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040830_fix">Remove all unapproved tunnels from the system, or document them with the ISSO.</fixtext>
-      <fix id="F-RHEL-07-040830_fix" />
-      <check system="C-RHEL-07-040830_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system does not have unauthorized IP tunnels configured.
-
-Check to see if “libreswan” is installed with the following command:
-
-# yum list installed libreswan
-openswan-2.6.32-27.el6.x86_64
-
-If “libreswan” is installed, check to see if the “IPsec” service is active with the following command:
-
-# systemctl status ipsec
-ipsec.service - Internet Key Exchange (IKE) Protocol Daemon for IPsec
-   Loaded: loaded (/usr/lib/systemd/system/ipsec.service; disabled)
-   Active: inactive (dead)
-
-If the “IPsec” service is active, check to see if any tunnels are configured in “/etc/ipsec.conf” and “/etc/ipsec.d/” with the following commands:
-
-# grep -i conn /etc/ipsec.conf
-conn mytunnel
-
-# grep -i conn /etc/ipsec.d/*.conf
-conn mytunnel
-
-If there are indications that a “conn” parameter is configured for a tunnel, ask the System Administrator (SA) if the tunnel is documented with the ISSO. If “libreswan” is installed, “IPsec” is active, and an undocumented tunnel is active, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-  <Group id="RHEL-07-040860">
-    <title>SRG-OS-000480-GPOS-00227</title>
-    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
-    <Rule id="RHEL-07-040860_rule" severity="medium" weight="10.0">
-      <version>RHEL-07-040860</version>
-      <title>The system must not forward IPv6 source-routed packets.</title>
-      <description>&lt;VulnDiscussion&gt;Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv6 forwarding is enabled and the system is functioning as a router.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SecurityOverrideGuidance&gt;&lt;/SecurityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
-      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
-      <fixtext fixref="F-RHEL-07-040860_fix">Set the system to the required kernel parameter, if IPv6 is enabled, by adding the following line to /etc/sysctl.conf (or modify the line to have the required value):
-
-net.ipv6.conf.all.accept_source_route = 0</fixtext>
-      <fix id="F-RHEL-07-040860_fix" />
-      <check system="C-RHEL-07-040860_chk">
-        <check-content-ref name="M" href="VMS_XCCDF_Benchmark_SRG.xml" />
-        <check-content>Verify the system does not accept IPv6 source-routed packets.
-
-Note: If IPv6 is not enabled, the key will not exist, and this is not a finding.
-
-Check the value of the accept source route variable with the following command:
-
-# /sbin/sysctl -a | grep  net.ipv6.conf.all.accept_source_route
-net.ipv6.conf.all.accept_source_route=0
-
-If the returned lines do not have a value of “0”, a line is not returned, or the retuned line is commented out, this is a finding.</check-content>
-      </check>
-    </Rule>
-  </Group>
-</Benchmark>
-
diff --git a/doc/metadata/U_Red_Hat_Enterprise_Linux_7_STIG_V1R1_Manual-xccdf.xml b/doc/metadata/U_Red_Hat_Enterprise_Linux_7_STIG_V1R1_Manual-xccdf.xml
new file mode 100644
index 00000000..57af75c4
--- /dev/null
+++ b/doc/metadata/U_Red_Hat_Enterprise_Linux_7_STIG_V1R1_Manual-xccdf.xml
@@ -0,0 +1,12082 @@
+<?xml version="1.0" encoding="utf-8"?>
+<?xml-stylesheet type='text/xsl' href='STIG_unclass.xsl'?>
+<Benchmark xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" 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:dc="http://purl.org/dc/elements/1.1/" xmlns="http://checklists.nist.gov/xccdf/1.1" id="RHEL_7_STIG" xml:lang="en" 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">
+  <status date="2017-03-08">accepted</status>
+  <title>Red Hat Enterprise Linux 7 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"/>
+  <reference href="http://iase.disa.mil">
+    <dc:publisher>DISA</dc:publisher>
+    <dc:source>STIG.DOD.MIL</dc:source>
+  </reference>
+  <plain-text id="release-info">Release: 1 Benchmark Date: 27 Feb 2017</plain-text>
+  <version>1</version>
+  <Profile id="MAC-1_Classified">
+    <title>I - Mission Critical Classified</title>
+    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
+    <select idref="V-71849" selected="true"/>
+    <select idref="V-71855" selected="true"/>
+    <select idref="V-71859" selected="true"/>
+    <select idref="V-71861" selected="true"/>
+    <select idref="V-71863" selected="true"/>
+    <select idref="V-71891" selected="true"/>
+    <select idref="V-71893" selected="true"/>
+    <select idref="V-71895" selected="true"/>
+    <select idref="V-71897" selected="true"/>
+    <select idref="V-71899" selected="true"/>
+    <select idref="V-71901" selected="true"/>
+    <select idref="V-71903" selected="true"/>
+    <select idref="V-71905" selected="true"/>
+    <select idref="V-71907" selected="true"/>
+    <select idref="V-71909" selected="true"/>
+    <select idref="V-71911" selected="true"/>
+    <select idref="V-71913" selected="true"/>
+    <select idref="V-71915" selected="true"/>
+    <select idref="V-71917" selected="true"/>
+    <select idref="V-71919" selected="true"/>
+    <select idref="V-71921" selected="true"/>
+    <select idref="V-71923" selected="true"/>
+    <select idref="V-71925" selected="true"/>
+    <select idref="V-71927" selected="true"/>
+    <select idref="V-71929" selected="true"/>
+    <select idref="V-71931" selected="true"/>
+    <select idref="V-71933" selected="true"/>
+    <select idref="V-71935" selected="true"/>
+    <select idref="V-71937" selected="true"/>
+    <select idref="V-71939" selected="true"/>
+    <select idref="V-71941" selected="true"/>
+    <select idref="V-71943" selected="true"/>
+    <select idref="V-71945" selected="true"/>
+    <select idref="V-71947" selected="true"/>
+    <select idref="V-71949" selected="true"/>
+    <select idref="V-71951" selected="true"/>
+    <select idref="V-71953" selected="true"/>
+    <select idref="V-71955" selected="true"/>
+    <select idref="V-71957" selected="true"/>
+    <select idref="V-71959" selected="true"/>
+    <select idref="V-71961" selected="true"/>
+    <select idref="V-71963" selected="true"/>
+    <select idref="V-71965" selected="true"/>
+    <select idref="V-71967" selected="true"/>
+    <select idref="V-71969" selected="true"/>
+    <select idref="V-71971" selected="true"/>
+    <select idref="V-71973" selected="true"/>
+    <select idref="V-71975" selected="true"/>
+    <select idref="V-71977" selected="true"/>
+    <select idref="V-71979" selected="true"/>
+    <select idref="V-71981" selected="true"/>
+    <select idref="V-71983" selected="true"/>
+    <select idref="V-71985" selected="true"/>
+    <select idref="V-71987" selected="true"/>
+    <select idref="V-71989" selected="true"/>
+    <select idref="V-71991" selected="true"/>
+    <select idref="V-71993" selected="true"/>
+    <select idref="V-71995" selected="true"/>
+    <select idref="V-71997" selected="true"/>
+    <select idref="V-71999" selected="true"/>
+    <select idref="V-72001" selected="true"/>
+    <select idref="V-72003" selected="true"/>
+    <select idref="V-72005" selected="true"/>
+    <select idref="V-72007" selected="true"/>
+    <select idref="V-72009" selected="true"/>
+    <select idref="V-72011" selected="true"/>
+    <select idref="V-72013" selected="true"/>
+    <select idref="V-72015" selected="true"/>
+    <select idref="V-72017" selected="true"/>
+    <select idref="V-72019" selected="true"/>
+    <select idref="V-72021" selected="true"/>
+    <select idref="V-72023" selected="true"/>
+    <select idref="V-72025" selected="true"/>
+    <select idref="V-72027" selected="true"/>
+    <select idref="V-72029" selected="true"/>
+    <select idref="V-72031" selected="true"/>
+    <select idref="V-72033" selected="true"/>
+    <select idref="V-72035" selected="true"/>
+    <select idref="V-72037" selected="true"/>
+    <select idref="V-72039" selected="true"/>
+    <select idref="V-72041" selected="true"/>
+    <select idref="V-72043" selected="true"/>
+    <select idref="V-72045" selected="true"/>
+    <select idref="V-72047" selected="true"/>
+    <select idref="V-72049" selected="true"/>
+    <select idref="V-72051" selected="true"/>
+    <select idref="V-72053" selected="true"/>
+    <select idref="V-72055" selected="true"/>
+    <select idref="V-72057" selected="true"/>
+    <select idref="V-72059" selected="true"/>
+    <select idref="V-72061" selected="true"/>
+    <select idref="V-72063" selected="true"/>
+    <select idref="V-72065" selected="true"/>
+    <select idref="V-72067" selected="true"/>
+    <select idref="V-72069" selected="true"/>
+    <select idref="V-72071" selected="true"/>
+    <select idref="V-72073" selected="true"/>
+    <select idref="V-72075" selected="true"/>
+    <select idref="V-72077" selected="true"/>
+    <select idref="V-72079" selected="true"/>
+    <select idref="V-72081" selected="true"/>
+    <select idref="V-72083" selected="true"/>
+    <select idref="V-72085" selected="true"/>
+    <select idref="V-72087" selected="true"/>
+    <select idref="V-72089" selected="true"/>
+    <select idref="V-72091" selected="true"/>
+    <select idref="V-72093" selected="true"/>
+    <select idref="V-72095" selected="true"/>
+    <select idref="V-72097" selected="true"/>
+    <select idref="V-72099" selected="true"/>
+    <select idref="V-72101" selected="true"/>
+    <select idref="V-72103" selected="true"/>
+    <select idref="V-72105" selected="true"/>
+    <select idref="V-72107" selected="true"/>
+    <select idref="V-72109" selected="true"/>
+    <select idref="V-72111" selected="true"/>
+    <select idref="V-72113" selected="true"/>
+    <select idref="V-72115" selected="true"/>
+    <select idref="V-72117" selected="true"/>
+    <select idref="V-72119" selected="true"/>
+    <select idref="V-72121" selected="true"/>
+    <select idref="V-72123" selected="true"/>
+    <select idref="V-72125" selected="true"/>
+    <select idref="V-72127" selected="true"/>
+    <select idref="V-72129" selected="true"/>
+    <select idref="V-72131" selected="true"/>
+    <select idref="V-72133" selected="true"/>
+    <select idref="V-72135" selected="true"/>
+    <select idref="V-72137" selected="true"/>
+    <select idref="V-72139" selected="true"/>
+    <select idref="V-72141" selected="true"/>
+    <select idref="V-72143" selected="true"/>
+    <select idref="V-72145" selected="true"/>
+    <select idref="V-72147" selected="true"/>
+    <select idref="V-72149" selected="true"/>
+    <select idref="V-72151" selected="true"/>
+    <select idref="V-72153" selected="true"/>
+    <select idref="V-72155" selected="true"/>
+    <select idref="V-72157" selected="true"/>
+    <select idref="V-72159" selected="true"/>
+    <select idref="V-72161" selected="true"/>
+    <select idref="V-72163" selected="true"/>
+    <select idref="V-72165" selected="true"/>
+    <select idref="V-72167" selected="true"/>
+    <select idref="V-72169" selected="true"/>
+    <select idref="V-72171" selected="true"/>
+    <select idref="V-72173" selected="true"/>
+    <select idref="V-72175" selected="true"/>
+    <select idref="V-72177" selected="true"/>
+    <select idref="V-72179" selected="true"/>
+    <select idref="V-72181" selected="true"/>
+    <select idref="V-72183" selected="true"/>
+    <select idref="V-72185" selected="true"/>
+    <select idref="V-72187" selected="true"/>
+    <select idref="V-72189" selected="true"/>
+    <select idref="V-72191" selected="true"/>
+    <select idref="V-72193" selected="true"/>
+    <select idref="V-72195" selected="true"/>
+    <select idref="V-72197" selected="true"/>
+    <select idref="V-72199" selected="true"/>
+    <select idref="V-72201" selected="true"/>
+    <select idref="V-72203" selected="true"/>
+    <select idref="V-72205" selected="true"/>
+    <select idref="V-72207" selected="true"/>
+    <select idref="V-72209" selected="true"/>
+    <select idref="V-72211" selected="true"/>
+    <select idref="V-72213" selected="true"/>
+    <select idref="V-72215" selected="true"/>
+    <select idref="V-72217" selected="true"/>
+    <select idref="V-72219" selected="true"/>
+    <select idref="V-72221" selected="true"/>
+    <select idref="V-72223" selected="true"/>
+    <select idref="V-72225" selected="true"/>
+    <select idref="V-72227" selected="true"/>
+    <select idref="V-72229" selected="true"/>
+    <select idref="V-72231" selected="true"/>
+    <select idref="V-72233" selected="true"/>
+    <select idref="V-72235" selected="true"/>
+    <select idref="V-72237" selected="true"/>
+    <select idref="V-72239" selected="true"/>
+    <select idref="V-72241" selected="true"/>
+    <select idref="V-72243" selected="true"/>
+    <select idref="V-72245" selected="true"/>
+    <select idref="V-72247" selected="true"/>
+    <select idref="V-72249" selected="true"/>
+    <select idref="V-72251" selected="true"/>
+    <select idref="V-72253" selected="true"/>
+    <select idref="V-72255" selected="true"/>
+    <select idref="V-72257" selected="true"/>
+    <select idref="V-72259" selected="true"/>
+    <select idref="V-72261" selected="true"/>
+    <select idref="V-72263" selected="true"/>
+    <select idref="V-72265" selected="true"/>
+    <select idref="V-72267" selected="true"/>
+    <select idref="V-72269" selected="true"/>
+    <select idref="V-72271" selected="true"/>
+    <select idref="V-72273" selected="true"/>
+    <select idref="V-72275" selected="true"/>
+    <select idref="V-72277" selected="true"/>
+    <select idref="V-72279" selected="true"/>
+    <select idref="V-72281" selected="true"/>
+    <select idref="V-72283" selected="true"/>
+    <select idref="V-72285" selected="true"/>
+    <select idref="V-72287" selected="true"/>
+    <select idref="V-72289" selected="true"/>
+    <select idref="V-72291" selected="true"/>
+    <select idref="V-72293" selected="true"/>
+    <select idref="V-72295" selected="true"/>
+    <select idref="V-72297" selected="true"/>
+    <select idref="V-72299" selected="true"/>
+    <select idref="V-72301" selected="true"/>
+    <select idref="V-72303" selected="true"/>
+    <select idref="V-72305" selected="true"/>
+    <select idref="V-72307" selected="true"/>
+    <select idref="V-72309" selected="true"/>
+    <select idref="V-72311" selected="true"/>
+    <select idref="V-72313" selected="true"/>
+    <select idref="V-72315" selected="true"/>
+    <select idref="V-72317" selected="true"/>
+    <select idref="V-72319" selected="true"/>
+    <select idref="V-72417" selected="true"/>
+    <select idref="V-72427" selected="true"/>
+    <select idref="V-72433" selected="true"/>
+    <select idref="V-72435" selected="true"/>
+    <select idref="V-73155" selected="true"/>
+    <select idref="V-73157" selected="true"/>
+    <select idref="V-73159" selected="true"/>
+    <select idref="V-73161" selected="true"/>
+    <select idref="V-73163" selected="true"/>
+    <select idref="V-73165" selected="true"/>
+    <select idref="V-73167" selected="true"/>
+    <select idref="V-73171" selected="true"/>
+    <select idref="V-73173" selected="true"/>
+    <select idref="V-73175" selected="true"/>
+    <select idref="V-73177" 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-71849" selected="true"/>
+    <select idref="V-71855" selected="true"/>
+    <select idref="V-71859" selected="true"/>
+    <select idref="V-71861" selected="true"/>
+    <select idref="V-71863" selected="true"/>
+    <select idref="V-71891" selected="true"/>
+    <select idref="V-71893" selected="true"/>
+    <select idref="V-71895" selected="true"/>
+    <select idref="V-71897" selected="true"/>
+    <select idref="V-71899" selected="true"/>
+    <select idref="V-71901" selected="true"/>
+    <select idref="V-71903" selected="true"/>
+    <select idref="V-71905" selected="true"/>
+    <select idref="V-71907" selected="true"/>
+    <select idref="V-71909" selected="true"/>
+    <select idref="V-71911" selected="true"/>
+    <select idref="V-71913" selected="true"/>
+    <select idref="V-71915" selected="true"/>
+    <select idref="V-71917" selected="true"/>
+    <select idref="V-71919" selected="true"/>
+    <select idref="V-71921" selected="true"/>
+    <select idref="V-71923" selected="true"/>
+    <select idref="V-71925" selected="true"/>
+    <select idref="V-71927" selected="true"/>
+    <select idref="V-71929" selected="true"/>
+    <select idref="V-71931" selected="true"/>
+    <select idref="V-71933" selected="true"/>
+    <select idref="V-71935" selected="true"/>
+    <select idref="V-71937" selected="true"/>
+    <select idref="V-71939" selected="true"/>
+    <select idref="V-71941" selected="true"/>
+    <select idref="V-71943" selected="true"/>
+    <select idref="V-71945" selected="true"/>
+    <select idref="V-71947" selected="true"/>
+    <select idref="V-71949" selected="true"/>
+    <select idref="V-71951" selected="true"/>
+    <select idref="V-71953" selected="true"/>
+    <select idref="V-71955" selected="true"/>
+    <select idref="V-71957" selected="true"/>
+    <select idref="V-71959" selected="true"/>
+    <select idref="V-71961" selected="true"/>
+    <select idref="V-71963" selected="true"/>
+    <select idref="V-71965" selected="true"/>
+    <select idref="V-71967" selected="true"/>
+    <select idref="V-71969" selected="true"/>
+    <select idref="V-71971" selected="true"/>
+    <select idref="V-71973" selected="true"/>
+    <select idref="V-71975" selected="true"/>
+    <select idref="V-71977" selected="true"/>
+    <select idref="V-71979" selected="true"/>
+    <select idref="V-71981" selected="true"/>
+    <select idref="V-71983" selected="true"/>
+    <select idref="V-71985" selected="true"/>
+    <select idref="V-71987" selected="true"/>
+    <select idref="V-71989" selected="true"/>
+    <select idref="V-71991" selected="true"/>
+    <select idref="V-71993" selected="true"/>
+    <select idref="V-71995" selected="true"/>
+    <select idref="V-71997" selected="true"/>
+    <select idref="V-71999" selected="true"/>
+    <select idref="V-72001" selected="true"/>
+    <select idref="V-72003" selected="true"/>
+    <select idref="V-72005" selected="true"/>
+    <select idref="V-72007" selected="true"/>
+    <select idref="V-72009" selected="true"/>
+    <select idref="V-72011" selected="true"/>
+    <select idref="V-72013" selected="true"/>
+    <select idref="V-72015" selected="true"/>
+    <select idref="V-72017" selected="true"/>
+    <select idref="V-72019" selected="true"/>
+    <select idref="V-72021" selected="true"/>
+    <select idref="V-72023" selected="true"/>
+    <select idref="V-72025" selected="true"/>
+    <select idref="V-72027" selected="true"/>
+    <select idref="V-72029" selected="true"/>
+    <select idref="V-72031" selected="true"/>
+    <select idref="V-72033" selected="true"/>
+    <select idref="V-72035" selected="true"/>
+    <select idref="V-72037" selected="true"/>
+    <select idref="V-72039" selected="true"/>
+    <select idref="V-72041" selected="true"/>
+    <select idref="V-72043" selected="true"/>
+    <select idref="V-72045" selected="true"/>
+    <select idref="V-72047" selected="true"/>
+    <select idref="V-72049" selected="true"/>
+    <select idref="V-72051" selected="true"/>
+    <select idref="V-72053" selected="true"/>
+    <select idref="V-72055" selected="true"/>
+    <select idref="V-72057" selected="true"/>
+    <select idref="V-72059" selected="true"/>
+    <select idref="V-72061" selected="true"/>
+    <select idref="V-72063" selected="true"/>
+    <select idref="V-72065" selected="true"/>
+    <select idref="V-72067" selected="true"/>
+    <select idref="V-72069" selected="true"/>
+    <select idref="V-72071" selected="true"/>
+    <select idref="V-72073" selected="true"/>
+    <select idref="V-72075" selected="true"/>
+    <select idref="V-72077" selected="true"/>
+    <select idref="V-72079" selected="true"/>
+    <select idref="V-72081" selected="true"/>
+    <select idref="V-72083" selected="true"/>
+    <select idref="V-72085" selected="true"/>
+    <select idref="V-72087" selected="true"/>
+    <select idref="V-72089" selected="true"/>
+    <select idref="V-72091" selected="true"/>
+    <select idref="V-72093" selected="true"/>
+    <select idref="V-72095" selected="true"/>
+    <select idref="V-72097" selected="true"/>
+    <select idref="V-72099" selected="true"/>
+    <select idref="V-72101" selected="true"/>
+    <select idref="V-72103" selected="true"/>
+    <select idref="V-72105" selected="true"/>
+    <select idref="V-72107" selected="true"/>
+    <select idref="V-72109" selected="true"/>
+    <select idref="V-72111" selected="true"/>
+    <select idref="V-72113" selected="true"/>
+    <select idref="V-72115" selected="true"/>
+    <select idref="V-72117" selected="true"/>
+    <select idref="V-72119" selected="true"/>
+    <select idref="V-72121" selected="true"/>
+    <select idref="V-72123" selected="true"/>
+    <select idref="V-72125" selected="true"/>
+    <select idref="V-72127" selected="true"/>
+    <select idref="V-72129" selected="true"/>
+    <select idref="V-72131" selected="true"/>
+    <select idref="V-72133" selected="true"/>
+    <select idref="V-72135" selected="true"/>
+    <select idref="V-72137" selected="true"/>
+    <select idref="V-72139" selected="true"/>
+    <select idref="V-72141" selected="true"/>
+    <select idref="V-72143" selected="true"/>
+    <select idref="V-72145" selected="true"/>
+    <select idref="V-72147" selected="true"/>
+    <select idref="V-72149" selected="true"/>
+    <select idref="V-72151" selected="true"/>
+    <select idref="V-72153" selected="true"/>
+    <select idref="V-72155" selected="true"/>
+    <select idref="V-72157" selected="true"/>
+    <select idref="V-72159" selected="true"/>
+    <select idref="V-72161" selected="true"/>
+    <select idref="V-72163" selected="true"/>
+    <select idref="V-72165" selected="true"/>
+    <select idref="V-72167" selected="true"/>
+    <select idref="V-72169" selected="true"/>
+    <select idref="V-72171" selected="true"/>
+    <select idref="V-72173" selected="true"/>
+    <select idref="V-72175" selected="true"/>
+    <select idref="V-72177" selected="true"/>
+    <select idref="V-72179" selected="true"/>
+    <select idref="V-72181" selected="true"/>
+    <select idref="V-72183" selected="true"/>
+    <select idref="V-72185" selected="true"/>
+    <select idref="V-72187" selected="true"/>
+    <select idref="V-72189" selected="true"/>
+    <select idref="V-72191" selected="true"/>
+    <select idref="V-72193" selected="true"/>
+    <select idref="V-72195" selected="true"/>
+    <select idref="V-72197" selected="true"/>
+    <select idref="V-72199" selected="true"/>
+    <select idref="V-72201" selected="true"/>
+    <select idref="V-72203" selected="true"/>
+    <select idref="V-72205" selected="true"/>
+    <select idref="V-72207" selected="true"/>
+    <select idref="V-72209" selected="true"/>
+    <select idref="V-72211" selected="true"/>
+    <select idref="V-72213" selected="true"/>
+    <select idref="V-72215" selected="true"/>
+    <select idref="V-72217" selected="true"/>
+    <select idref="V-72219" selected="true"/>
+    <select idref="V-72221" selected="true"/>
+    <select idref="V-72223" selected="true"/>
+    <select idref="V-72225" selected="true"/>
+    <select idref="V-72227" selected="true"/>
+    <select idref="V-72229" selected="true"/>
+    <select idref="V-72231" selected="true"/>
+    <select idref="V-72233" selected="true"/>
+    <select idref="V-72235" selected="true"/>
+    <select idref="V-72237" selected="true"/>
+    <select idref="V-72239" selected="true"/>
+    <select idref="V-72241" selected="true"/>
+    <select idref="V-72243" selected="true"/>
+    <select idref="V-72245" selected="true"/>
+    <select idref="V-72247" selected="true"/>
+    <select idref="V-72249" selected="true"/>
+    <select idref="V-72251" selected="true"/>
+    <select idref="V-72253" selected="true"/>
+    <select idref="V-72255" selected="true"/>
+    <select idref="V-72257" selected="true"/>
+    <select idref="V-72259" selected="true"/>
+    <select idref="V-72261" selected="true"/>
+    <select idref="V-72263" selected="true"/>
+    <select idref="V-72265" selected="true"/>
+    <select idref="V-72267" selected="true"/>
+    <select idref="V-72269" selected="true"/>
+    <select idref="V-72271" selected="true"/>
+    <select idref="V-72273" selected="true"/>
+    <select idref="V-72275" selected="true"/>
+    <select idref="V-72277" selected="true"/>
+    <select idref="V-72279" selected="true"/>
+    <select idref="V-72281" selected="true"/>
+    <select idref="V-72283" selected="true"/>
+    <select idref="V-72285" selected="true"/>
+    <select idref="V-72287" selected="true"/>
+    <select idref="V-72289" selected="true"/>
+    <select idref="V-72291" selected="true"/>
+    <select idref="V-72293" selected="true"/>
+    <select idref="V-72295" selected="true"/>
+    <select idref="V-72297" selected="true"/>
+    <select idref="V-72299" selected="true"/>
+    <select idref="V-72301" selected="true"/>
+    <select idref="V-72303" selected="true"/>
+    <select idref="V-72305" selected="true"/>
+    <select idref="V-72307" selected="true"/>
+    <select idref="V-72309" selected="true"/>
+    <select idref="V-72311" selected="true"/>
+    <select idref="V-72313" selected="true"/>
+    <select idref="V-72315" selected="true"/>
+    <select idref="V-72317" selected="true"/>
+    <select idref="V-72319" selected="true"/>
+    <select idref="V-72417" selected="true"/>
+    <select idref="V-72427" selected="true"/>
+    <select idref="V-72433" selected="true"/>
+    <select idref="V-72435" selected="true"/>
+    <select idref="V-73155" selected="true"/>
+    <select idref="V-73157" selected="true"/>
+    <select idref="V-73159" selected="true"/>
+    <select idref="V-73161" selected="true"/>
+    <select idref="V-73163" selected="true"/>
+    <select idref="V-73165" selected="true"/>
+    <select idref="V-73167" selected="true"/>
+    <select idref="V-73171" selected="true"/>
+    <select idref="V-73173" selected="true"/>
+    <select idref="V-73175" selected="true"/>
+    <select idref="V-73177" 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-71849" selected="true"/>
+    <select idref="V-71855" selected="true"/>
+    <select idref="V-71859" selected="true"/>
+    <select idref="V-71861" selected="true"/>
+    <select idref="V-71863" selected="true"/>
+    <select idref="V-71891" selected="true"/>
+    <select idref="V-71893" selected="true"/>
+    <select idref="V-71895" selected="true"/>
+    <select idref="V-71897" selected="true"/>
+    <select idref="V-71899" selected="true"/>
+    <select idref="V-71901" selected="true"/>
+    <select idref="V-71903" selected="true"/>
+    <select idref="V-71905" selected="true"/>
+    <select idref="V-71907" selected="true"/>
+    <select idref="V-71909" selected="true"/>
+    <select idref="V-71911" selected="true"/>
+    <select idref="V-71913" selected="true"/>
+    <select idref="V-71915" selected="true"/>
+    <select idref="V-71917" selected="true"/>
+    <select idref="V-71919" selected="true"/>
+    <select idref="V-71921" selected="true"/>
+    <select idref="V-71923" selected="true"/>
+    <select idref="V-71925" selected="true"/>
+    <select idref="V-71927" selected="true"/>
+    <select idref="V-71929" selected="true"/>
+    <select idref="V-71931" selected="true"/>
+    <select idref="V-71933" selected="true"/>
+    <select idref="V-71935" selected="true"/>
+    <select idref="V-71937" selected="true"/>
+    <select idref="V-71939" selected="true"/>
+    <select idref="V-71941" selected="true"/>
+    <select idref="V-71943" selected="true"/>
+    <select idref="V-71945" selected="true"/>
+    <select idref="V-71947" selected="true"/>
+    <select idref="V-71949" selected="true"/>
+    <select idref="V-71951" selected="true"/>
+    <select idref="V-71953" selected="true"/>
+    <select idref="V-71955" selected="true"/>
+    <select idref="V-71957" selected="true"/>
+    <select idref="V-71959" selected="true"/>
+    <select idref="V-71961" selected="true"/>
+    <select idref="V-71963" selected="true"/>
+    <select idref="V-71965" selected="true"/>
+    <select idref="V-71967" selected="true"/>
+    <select idref="V-71969" selected="true"/>
+    <select idref="V-71971" selected="true"/>
+    <select idref="V-71973" selected="true"/>
+    <select idref="V-71975" selected="true"/>
+    <select idref="V-71977" selected="true"/>
+    <select idref="V-71979" selected="true"/>
+    <select idref="V-71981" selected="true"/>
+    <select idref="V-71983" selected="true"/>
+    <select idref="V-71985" selected="true"/>
+    <select idref="V-71987" selected="true"/>
+    <select idref="V-71989" selected="true"/>
+    <select idref="V-71991" selected="true"/>
+    <select idref="V-71993" selected="true"/>
+    <select idref="V-71995" selected="true"/>
+    <select idref="V-71997" selected="true"/>
+    <select idref="V-71999" selected="true"/>
+    <select idref="V-72001" selected="true"/>
+    <select idref="V-72003" selected="true"/>
+    <select idref="V-72005" selected="true"/>
+    <select idref="V-72007" selected="true"/>
+    <select idref="V-72009" selected="true"/>
+    <select idref="V-72011" selected="true"/>
+    <select idref="V-72013" selected="true"/>
+    <select idref="V-72015" selected="true"/>
+    <select idref="V-72017" selected="true"/>
+    <select idref="V-72019" selected="true"/>
+    <select idref="V-72021" selected="true"/>
+    <select idref="V-72023" selected="true"/>
+    <select idref="V-72025" selected="true"/>
+    <select idref="V-72027" selected="true"/>
+    <select idref="V-72029" selected="true"/>
+    <select idref="V-72031" selected="true"/>
+    <select idref="V-72033" selected="true"/>
+    <select idref="V-72035" selected="true"/>
+    <select idref="V-72037" selected="true"/>
+    <select idref="V-72039" selected="true"/>
+    <select idref="V-72041" selected="true"/>
+    <select idref="V-72043" selected="true"/>
+    <select idref="V-72045" selected="true"/>
+    <select idref="V-72047" selected="true"/>
+    <select idref="V-72049" selected="true"/>
+    <select idref="V-72051" selected="true"/>
+    <select idref="V-72053" selected="true"/>
+    <select idref="V-72055" selected="true"/>
+    <select idref="V-72057" selected="true"/>
+    <select idref="V-72059" selected="true"/>
+    <select idref="V-72061" selected="true"/>
+    <select idref="V-72063" selected="true"/>
+    <select idref="V-72065" selected="true"/>
+    <select idref="V-72067" selected="true"/>
+    <select idref="V-72069" selected="true"/>
+    <select idref="V-72071" selected="true"/>
+    <select idref="V-72073" selected="true"/>
+    <select idref="V-72075" selected="true"/>
+    <select idref="V-72077" selected="true"/>
+    <select idref="V-72079" selected="true"/>
+    <select idref="V-72081" selected="true"/>
+    <select idref="V-72083" selected="true"/>
+    <select idref="V-72085" selected="true"/>
+    <select idref="V-72087" selected="true"/>
+    <select idref="V-72089" selected="true"/>
+    <select idref="V-72091" selected="true"/>
+    <select idref="V-72093" selected="true"/>
+    <select idref="V-72095" selected="true"/>
+    <select idref="V-72097" selected="true"/>
+    <select idref="V-72099" selected="true"/>
+    <select idref="V-72101" selected="true"/>
+    <select idref="V-72103" selected="true"/>
+    <select idref="V-72105" selected="true"/>
+    <select idref="V-72107" selected="true"/>
+    <select idref="V-72109" selected="true"/>
+    <select idref="V-72111" selected="true"/>
+    <select idref="V-72113" selected="true"/>
+    <select idref="V-72115" selected="true"/>
+    <select idref="V-72117" selected="true"/>
+    <select idref="V-72119" selected="true"/>
+    <select idref="V-72121" selected="true"/>
+    <select idref="V-72123" selected="true"/>
+    <select idref="V-72125" selected="true"/>
+    <select idref="V-72127" selected="true"/>
+    <select idref="V-72129" selected="true"/>
+    <select idref="V-72131" selected="true"/>
+    <select idref="V-72133" selected="true"/>
+    <select idref="V-72135" selected="true"/>
+    <select idref="V-72137" selected="true"/>
+    <select idref="V-72139" selected="true"/>
+    <select idref="V-72141" selected="true"/>
+    <select idref="V-72143" selected="true"/>
+    <select idref="V-72145" selected="true"/>
+    <select idref="V-72147" selected="true"/>
+    <select idref="V-72149" selected="true"/>
+    <select idref="V-72151" selected="true"/>
+    <select idref="V-72153" selected="true"/>
+    <select idref="V-72155" selected="true"/>
+    <select idref="V-72157" selected="true"/>
+    <select idref="V-72159" selected="true"/>
+    <select idref="V-72161" selected="true"/>
+    <select idref="V-72163" selected="true"/>
+    <select idref="V-72165" selected="true"/>
+    <select idref="V-72167" selected="true"/>
+    <select idref="V-72169" selected="true"/>
+    <select idref="V-72171" selected="true"/>
+    <select idref="V-72173" selected="true"/>
+    <select idref="V-72175" selected="true"/>
+    <select idref="V-72177" selected="true"/>
+    <select idref="V-72179" selected="true"/>
+    <select idref="V-72181" selected="true"/>
+    <select idref="V-72183" selected="true"/>
+    <select idref="V-72185" selected="true"/>
+    <select idref="V-72187" selected="true"/>
+    <select idref="V-72189" selected="true"/>
+    <select idref="V-72191" selected="true"/>
+    <select idref="V-72193" selected="true"/>
+    <select idref="V-72195" selected="true"/>
+    <select idref="V-72197" selected="true"/>
+    <select idref="V-72199" selected="true"/>
+    <select idref="V-72201" selected="true"/>
+    <select idref="V-72203" selected="true"/>
+    <select idref="V-72205" selected="true"/>
+    <select idref="V-72207" selected="true"/>
+    <select idref="V-72209" selected="true"/>
+    <select idref="V-72211" selected="true"/>
+    <select idref="V-72213" selected="true"/>
+    <select idref="V-72215" selected="true"/>
+    <select idref="V-72217" selected="true"/>
+    <select idref="V-72219" selected="true"/>
+    <select idref="V-72221" selected="true"/>
+    <select idref="V-72223" selected="true"/>
+    <select idref="V-72225" selected="true"/>
+    <select idref="V-72227" selected="true"/>
+    <select idref="V-72229" selected="true"/>
+    <select idref="V-72231" selected="true"/>
+    <select idref="V-72233" selected="true"/>
+    <select idref="V-72235" selected="true"/>
+    <select idref="V-72237" selected="true"/>
+    <select idref="V-72239" selected="true"/>
+    <select idref="V-72241" selected="true"/>
+    <select idref="V-72243" selected="true"/>
+    <select idref="V-72245" selected="true"/>
+    <select idref="V-72247" selected="true"/>
+    <select idref="V-72249" selected="true"/>
+    <select idref="V-72251" selected="true"/>
+    <select idref="V-72253" selected="true"/>
+    <select idref="V-72255" selected="true"/>
+    <select idref="V-72257" selected="true"/>
+    <select idref="V-72259" selected="true"/>
+    <select idref="V-72261" selected="true"/>
+    <select idref="V-72263" selected="true"/>
+    <select idref="V-72265" selected="true"/>
+    <select idref="V-72267" selected="true"/>
+    <select idref="V-72269" selected="true"/>
+    <select idref="V-72271" selected="true"/>
+    <select idref="V-72273" selected="true"/>
+    <select idref="V-72275" selected="true"/>
+    <select idref="V-72277" selected="true"/>
+    <select idref="V-72279" selected="true"/>
+    <select idref="V-72281" selected="true"/>
+    <select idref="V-72283" selected="true"/>
+    <select idref="V-72285" selected="true"/>
+    <select idref="V-72287" selected="true"/>
+    <select idref="V-72289" selected="true"/>
+    <select idref="V-72291" selected="true"/>
+    <select idref="V-72293" selected="true"/>
+    <select idref="V-72295" selected="true"/>
+    <select idref="V-72297" selected="true"/>
+    <select idref="V-72299" selected="true"/>
+    <select idref="V-72301" selected="true"/>
+    <select idref="V-72303" selected="true"/>
+    <select idref="V-72305" selected="true"/>
+    <select idref="V-72307" selected="true"/>
+    <select idref="V-72309" selected="true"/>
+    <select idref="V-72311" selected="true"/>
+    <select idref="V-72313" selected="true"/>
+    <select idref="V-72315" selected="true"/>
+    <select idref="V-72317" selected="true"/>
+    <select idref="V-72319" selected="true"/>
+    <select idref="V-72417" selected="true"/>
+    <select idref="V-72427" selected="true"/>
+    <select idref="V-72433" selected="true"/>
+    <select idref="V-72435" selected="true"/>
+    <select idref="V-73155" selected="true"/>
+    <select idref="V-73157" selected="true"/>
+    <select idref="V-73159" selected="true"/>
+    <select idref="V-73161" selected="true"/>
+    <select idref="V-73163" selected="true"/>
+    <select idref="V-73165" selected="true"/>
+    <select idref="V-73167" selected="true"/>
+    <select idref="V-73171" selected="true"/>
+    <select idref="V-73173" selected="true"/>
+    <select idref="V-73175" selected="true"/>
+    <select idref="V-73177" 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-71849" selected="true"/>
+    <select idref="V-71855" selected="true"/>
+    <select idref="V-71859" selected="true"/>
+    <select idref="V-71861" selected="true"/>
+    <select idref="V-71863" selected="true"/>
+    <select idref="V-71891" selected="true"/>
+    <select idref="V-71893" selected="true"/>
+    <select idref="V-71895" selected="true"/>
+    <select idref="V-71897" selected="true"/>
+    <select idref="V-71899" selected="true"/>
+    <select idref="V-71901" selected="true"/>
+    <select idref="V-71903" selected="true"/>
+    <select idref="V-71905" selected="true"/>
+    <select idref="V-71907" selected="true"/>
+    <select idref="V-71909" selected="true"/>
+    <select idref="V-71911" selected="true"/>
+    <select idref="V-71913" selected="true"/>
+    <select idref="V-71915" selected="true"/>
+    <select idref="V-71917" selected="true"/>
+    <select idref="V-71919" selected="true"/>
+    <select idref="V-71921" selected="true"/>
+    <select idref="V-71923" selected="true"/>
+    <select idref="V-71925" selected="true"/>
+    <select idref="V-71927" selected="true"/>
+    <select idref="V-71929" selected="true"/>
+    <select idref="V-71931" selected="true"/>
+    <select idref="V-71933" selected="true"/>
+    <select idref="V-71935" selected="true"/>
+    <select idref="V-71937" selected="true"/>
+    <select idref="V-71939" selected="true"/>
+    <select idref="V-71941" selected="true"/>
+    <select idref="V-71943" selected="true"/>
+    <select idref="V-71945" selected="true"/>
+    <select idref="V-71947" selected="true"/>
+    <select idref="V-71949" selected="true"/>
+    <select idref="V-71951" selected="true"/>
+    <select idref="V-71953" selected="true"/>
+    <select idref="V-71955" selected="true"/>
+    <select idref="V-71957" selected="true"/>
+    <select idref="V-71959" selected="true"/>
+    <select idref="V-71961" selected="true"/>
+    <select idref="V-71963" selected="true"/>
+    <select idref="V-71965" selected="true"/>
+    <select idref="V-71967" selected="true"/>
+    <select idref="V-71969" selected="true"/>
+    <select idref="V-71971" selected="true"/>
+    <select idref="V-71973" selected="true"/>
+    <select idref="V-71975" selected="true"/>
+    <select idref="V-71977" selected="true"/>
+    <select idref="V-71979" selected="true"/>
+    <select idref="V-71981" selected="true"/>
+    <select idref="V-71983" selected="true"/>
+    <select idref="V-71985" selected="true"/>
+    <select idref="V-71987" selected="true"/>
+    <select idref="V-71989" selected="true"/>
+    <select idref="V-71991" selected="true"/>
+    <select idref="V-71993" selected="true"/>
+    <select idref="V-71995" selected="true"/>
+    <select idref="V-71997" selected="true"/>
+    <select idref="V-71999" selected="true"/>
+    <select idref="V-72001" selected="true"/>
+    <select idref="V-72003" selected="true"/>
+    <select idref="V-72005" selected="true"/>
+    <select idref="V-72007" selected="true"/>
+    <select idref="V-72009" selected="true"/>
+    <select idref="V-72011" selected="true"/>
+    <select idref="V-72013" selected="true"/>
+    <select idref="V-72015" selected="true"/>
+    <select idref="V-72017" selected="true"/>
+    <select idref="V-72019" selected="true"/>
+    <select idref="V-72021" selected="true"/>
+    <select idref="V-72023" selected="true"/>
+    <select idref="V-72025" selected="true"/>
+    <select idref="V-72027" selected="true"/>
+    <select idref="V-72029" selected="true"/>
+    <select idref="V-72031" selected="true"/>
+    <select idref="V-72033" selected="true"/>
+    <select idref="V-72035" selected="true"/>
+    <select idref="V-72037" selected="true"/>
+    <select idref="V-72039" selected="true"/>
+    <select idref="V-72041" selected="true"/>
+    <select idref="V-72043" selected="true"/>
+    <select idref="V-72045" selected="true"/>
+    <select idref="V-72047" selected="true"/>
+    <select idref="V-72049" selected="true"/>
+    <select idref="V-72051" selected="true"/>
+    <select idref="V-72053" selected="true"/>
+    <select idref="V-72055" selected="true"/>
+    <select idref="V-72057" selected="true"/>
+    <select idref="V-72059" selected="true"/>
+    <select idref="V-72061" selected="true"/>
+    <select idref="V-72063" selected="true"/>
+    <select idref="V-72065" selected="true"/>
+    <select idref="V-72067" selected="true"/>
+    <select idref="V-72069" selected="true"/>
+    <select idref="V-72071" selected="true"/>
+    <select idref="V-72073" selected="true"/>
+    <select idref="V-72075" selected="true"/>
+    <select idref="V-72077" selected="true"/>
+    <select idref="V-72079" selected="true"/>
+    <select idref="V-72081" selected="true"/>
+    <select idref="V-72083" selected="true"/>
+    <select idref="V-72085" selected="true"/>
+    <select idref="V-72087" selected="true"/>
+    <select idref="V-72089" selected="true"/>
+    <select idref="V-72091" selected="true"/>
+    <select idref="V-72093" selected="true"/>
+    <select idref="V-72095" selected="true"/>
+    <select idref="V-72097" selected="true"/>
+    <select idref="V-72099" selected="true"/>
+    <select idref="V-72101" selected="true"/>
+    <select idref="V-72103" selected="true"/>
+    <select idref="V-72105" selected="true"/>
+    <select idref="V-72107" selected="true"/>
+    <select idref="V-72109" selected="true"/>
+    <select idref="V-72111" selected="true"/>
+    <select idref="V-72113" selected="true"/>
+    <select idref="V-72115" selected="true"/>
+    <select idref="V-72117" selected="true"/>
+    <select idref="V-72119" selected="true"/>
+    <select idref="V-72121" selected="true"/>
+    <select idref="V-72123" selected="true"/>
+    <select idref="V-72125" selected="true"/>
+    <select idref="V-72127" selected="true"/>
+    <select idref="V-72129" selected="true"/>
+    <select idref="V-72131" selected="true"/>
+    <select idref="V-72133" selected="true"/>
+    <select idref="V-72135" selected="true"/>
+    <select idref="V-72137" selected="true"/>
+    <select idref="V-72139" selected="true"/>
+    <select idref="V-72141" selected="true"/>
+    <select idref="V-72143" selected="true"/>
+    <select idref="V-72145" selected="true"/>
+    <select idref="V-72147" selected="true"/>
+    <select idref="V-72149" selected="true"/>
+    <select idref="V-72151" selected="true"/>
+    <select idref="V-72153" selected="true"/>
+    <select idref="V-72155" selected="true"/>
+    <select idref="V-72157" selected="true"/>
+    <select idref="V-72159" selected="true"/>
+    <select idref="V-72161" selected="true"/>
+    <select idref="V-72163" selected="true"/>
+    <select idref="V-72165" selected="true"/>
+    <select idref="V-72167" selected="true"/>
+    <select idref="V-72169" selected="true"/>
+    <select idref="V-72171" selected="true"/>
+    <select idref="V-72173" selected="true"/>
+    <select idref="V-72175" selected="true"/>
+    <select idref="V-72177" selected="true"/>
+    <select idref="V-72179" selected="true"/>
+    <select idref="V-72181" selected="true"/>
+    <select idref="V-72183" selected="true"/>
+    <select idref="V-72185" selected="true"/>
+    <select idref="V-72187" selected="true"/>
+    <select idref="V-72189" selected="true"/>
+    <select idref="V-72191" selected="true"/>
+    <select idref="V-72193" selected="true"/>
+    <select idref="V-72195" selected="true"/>
+    <select idref="V-72197" selected="true"/>
+    <select idref="V-72199" selected="true"/>
+    <select idref="V-72201" selected="true"/>
+    <select idref="V-72203" selected="true"/>
+    <select idref="V-72205" selected="true"/>
+    <select idref="V-72207" selected="true"/>
+    <select idref="V-72209" selected="true"/>
+    <select idref="V-72211" selected="true"/>
+    <select idref="V-72213" selected="true"/>
+    <select idref="V-72215" selected="true"/>
+    <select idref="V-72217" selected="true"/>
+    <select idref="V-72219" selected="true"/>
+    <select idref="V-72221" selected="true"/>
+    <select idref="V-72223" selected="true"/>
+    <select idref="V-72225" selected="true"/>
+    <select idref="V-72227" selected="true"/>
+    <select idref="V-72229" selected="true"/>
+    <select idref="V-72231" selected="true"/>
+    <select idref="V-72233" selected="true"/>
+    <select idref="V-72235" selected="true"/>
+    <select idref="V-72237" selected="true"/>
+    <select idref="V-72239" selected="true"/>
+    <select idref="V-72241" selected="true"/>
+    <select idref="V-72243" selected="true"/>
+    <select idref="V-72245" selected="true"/>
+    <select idref="V-72247" selected="true"/>
+    <select idref="V-72249" selected="true"/>
+    <select idref="V-72251" selected="true"/>
+    <select idref="V-72253" selected="true"/>
+    <select idref="V-72255" selected="true"/>
+    <select idref="V-72257" selected="true"/>
+    <select idref="V-72259" selected="true"/>
+    <select idref="V-72261" selected="true"/>
+    <select idref="V-72263" selected="true"/>
+    <select idref="V-72265" selected="true"/>
+    <select idref="V-72267" selected="true"/>
+    <select idref="V-72269" selected="true"/>
+    <select idref="V-72271" selected="true"/>
+    <select idref="V-72273" selected="true"/>
+    <select idref="V-72275" selected="true"/>
+    <select idref="V-72277" selected="true"/>
+    <select idref="V-72279" selected="true"/>
+    <select idref="V-72281" selected="true"/>
+    <select idref="V-72283" selected="true"/>
+    <select idref="V-72285" selected="true"/>
+    <select idref="V-72287" selected="true"/>
+    <select idref="V-72289" selected="true"/>
+    <select idref="V-72291" selected="true"/>
+    <select idref="V-72293" selected="true"/>
+    <select idref="V-72295" selected="true"/>
+    <select idref="V-72297" selected="true"/>
+    <select idref="V-72299" selected="true"/>
+    <select idref="V-72301" selected="true"/>
+    <select idref="V-72303" selected="true"/>
+    <select idref="V-72305" selected="true"/>
+    <select idref="V-72307" selected="true"/>
+    <select idref="V-72309" selected="true"/>
+    <select idref="V-72311" selected="true"/>
+    <select idref="V-72313" selected="true"/>
+    <select idref="V-72315" selected="true"/>
+    <select idref="V-72317" selected="true"/>
+    <select idref="V-72319" selected="true"/>
+    <select idref="V-72417" selected="true"/>
+    <select idref="V-72427" selected="true"/>
+    <select idref="V-72433" selected="true"/>
+    <select idref="V-72435" selected="true"/>
+    <select idref="V-73155" selected="true"/>
+    <select idref="V-73157" selected="true"/>
+    <select idref="V-73159" selected="true"/>
+    <select idref="V-73161" selected="true"/>
+    <select idref="V-73163" selected="true"/>
+    <select idref="V-73165" selected="true"/>
+    <select idref="V-73167" selected="true"/>
+    <select idref="V-73171" selected="true"/>
+    <select idref="V-73173" selected="true"/>
+    <select idref="V-73175" selected="true"/>
+    <select idref="V-73177" 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-71849" selected="true"/>
+    <select idref="V-71855" selected="true"/>
+    <select idref="V-71859" selected="true"/>
+    <select idref="V-71861" selected="true"/>
+    <select idref="V-71863" selected="true"/>
+    <select idref="V-71891" selected="true"/>
+    <select idref="V-71893" selected="true"/>
+    <select idref="V-71895" selected="true"/>
+    <select idref="V-71897" selected="true"/>
+    <select idref="V-71899" selected="true"/>
+    <select idref="V-71901" selected="true"/>
+    <select idref="V-71903" selected="true"/>
+    <select idref="V-71905" selected="true"/>
+    <select idref="V-71907" selected="true"/>
+    <select idref="V-71909" selected="true"/>
+    <select idref="V-71911" selected="true"/>
+    <select idref="V-71913" selected="true"/>
+    <select idref="V-71915" selected="true"/>
+    <select idref="V-71917" selected="true"/>
+    <select idref="V-71919" selected="true"/>
+    <select idref="V-71921" selected="true"/>
+    <select idref="V-71923" selected="true"/>
+    <select idref="V-71925" selected="true"/>
+    <select idref="V-71927" selected="true"/>
+    <select idref="V-71929" selected="true"/>
+    <select idref="V-71931" selected="true"/>
+    <select idref="V-71933" selected="true"/>
+    <select idref="V-71935" selected="true"/>
+    <select idref="V-71937" selected="true"/>
+    <select idref="V-71939" selected="true"/>
+    <select idref="V-71941" selected="true"/>
+    <select idref="V-71943" selected="true"/>
+    <select idref="V-71945" selected="true"/>
+    <select idref="V-71947" selected="true"/>
+    <select idref="V-71949" selected="true"/>
+    <select idref="V-71951" selected="true"/>
+    <select idref="V-71953" selected="true"/>
+    <select idref="V-71955" selected="true"/>
+    <select idref="V-71957" selected="true"/>
+    <select idref="V-71959" selected="true"/>
+    <select idref="V-71961" selected="true"/>
+    <select idref="V-71963" selected="true"/>
+    <select idref="V-71965" selected="true"/>
+    <select idref="V-71967" selected="true"/>
+    <select idref="V-71969" selected="true"/>
+    <select idref="V-71971" selected="true"/>
+    <select idref="V-71973" selected="true"/>
+    <select idref="V-71975" selected="true"/>
+    <select idref="V-71977" selected="true"/>
+    <select idref="V-71979" selected="true"/>
+    <select idref="V-71981" selected="true"/>
+    <select idref="V-71983" selected="true"/>
+    <select idref="V-71985" selected="true"/>
+    <select idref="V-71987" selected="true"/>
+    <select idref="V-71989" selected="true"/>
+    <select idref="V-71991" selected="true"/>
+    <select idref="V-71993" selected="true"/>
+    <select idref="V-71995" selected="true"/>
+    <select idref="V-71997" selected="true"/>
+    <select idref="V-71999" selected="true"/>
+    <select idref="V-72001" selected="true"/>
+    <select idref="V-72003" selected="true"/>
+    <select idref="V-72005" selected="true"/>
+    <select idref="V-72007" selected="true"/>
+    <select idref="V-72009" selected="true"/>
+    <select idref="V-72011" selected="true"/>
+    <select idref="V-72013" selected="true"/>
+    <select idref="V-72015" selected="true"/>
+    <select idref="V-72017" selected="true"/>
+    <select idref="V-72019" selected="true"/>
+    <select idref="V-72021" selected="true"/>
+    <select idref="V-72023" selected="true"/>
+    <select idref="V-72025" selected="true"/>
+    <select idref="V-72027" selected="true"/>
+    <select idref="V-72029" selected="true"/>
+    <select idref="V-72031" selected="true"/>
+    <select idref="V-72033" selected="true"/>
+    <select idref="V-72035" selected="true"/>
+    <select idref="V-72037" selected="true"/>
+    <select idref="V-72039" selected="true"/>
+    <select idref="V-72041" selected="true"/>
+    <select idref="V-72043" selected="true"/>
+    <select idref="V-72045" selected="true"/>
+    <select idref="V-72047" selected="true"/>
+    <select idref="V-72049" selected="true"/>
+    <select idref="V-72051" selected="true"/>
+    <select idref="V-72053" selected="true"/>
+    <select idref="V-72055" selected="true"/>
+    <select idref="V-72057" selected="true"/>
+    <select idref="V-72059" selected="true"/>
+    <select idref="V-72061" selected="true"/>
+    <select idref="V-72063" selected="true"/>
+    <select idref="V-72065" selected="true"/>
+    <select idref="V-72067" selected="true"/>
+    <select idref="V-72069" selected="true"/>
+    <select idref="V-72071" selected="true"/>
+    <select idref="V-72073" selected="true"/>
+    <select idref="V-72075" selected="true"/>
+    <select idref="V-72077" selected="true"/>
+    <select idref="V-72079" selected="true"/>
+    <select idref="V-72081" selected="true"/>
+    <select idref="V-72083" selected="true"/>
+    <select idref="V-72085" selected="true"/>
+    <select idref="V-72087" selected="true"/>
+    <select idref="V-72089" selected="true"/>
+    <select idref="V-72091" selected="true"/>
+    <select idref="V-72093" selected="true"/>
+    <select idref="V-72095" selected="true"/>
+    <select idref="V-72097" selected="true"/>
+    <select idref="V-72099" selected="true"/>
+    <select idref="V-72101" selected="true"/>
+    <select idref="V-72103" selected="true"/>
+    <select idref="V-72105" selected="true"/>
+    <select idref="V-72107" selected="true"/>
+    <select idref="V-72109" selected="true"/>
+    <select idref="V-72111" selected="true"/>
+    <select idref="V-72113" selected="true"/>
+    <select idref="V-72115" selected="true"/>
+    <select idref="V-72117" selected="true"/>
+    <select idref="V-72119" selected="true"/>
+    <select idref="V-72121" selected="true"/>
+    <select idref="V-72123" selected="true"/>
+    <select idref="V-72125" selected="true"/>
+    <select idref="V-72127" selected="true"/>
+    <select idref="V-72129" selected="true"/>
+    <select idref="V-72131" selected="true"/>
+    <select idref="V-72133" selected="true"/>
+    <select idref="V-72135" selected="true"/>
+    <select idref="V-72137" selected="true"/>
+    <select idref="V-72139" selected="true"/>
+    <select idref="V-72141" selected="true"/>
+    <select idref="V-72143" selected="true"/>
+    <select idref="V-72145" selected="true"/>
+    <select idref="V-72147" selected="true"/>
+    <select idref="V-72149" selected="true"/>
+    <select idref="V-72151" selected="true"/>
+    <select idref="V-72153" selected="true"/>
+    <select idref="V-72155" selected="true"/>
+    <select idref="V-72157" selected="true"/>
+    <select idref="V-72159" selected="true"/>
+    <select idref="V-72161" selected="true"/>
+    <select idref="V-72163" selected="true"/>
+    <select idref="V-72165" selected="true"/>
+    <select idref="V-72167" selected="true"/>
+    <select idref="V-72169" selected="true"/>
+    <select idref="V-72171" selected="true"/>
+    <select idref="V-72173" selected="true"/>
+    <select idref="V-72175" selected="true"/>
+    <select idref="V-72177" selected="true"/>
+    <select idref="V-72179" selected="true"/>
+    <select idref="V-72181" selected="true"/>
+    <select idref="V-72183" selected="true"/>
+    <select idref="V-72185" selected="true"/>
+    <select idref="V-72187" selected="true"/>
+    <select idref="V-72189" selected="true"/>
+    <select idref="V-72191" selected="true"/>
+    <select idref="V-72193" selected="true"/>
+    <select idref="V-72195" selected="true"/>
+    <select idref="V-72197" selected="true"/>
+    <select idref="V-72199" selected="true"/>
+    <select idref="V-72201" selected="true"/>
+    <select idref="V-72203" selected="true"/>
+    <select idref="V-72205" selected="true"/>
+    <select idref="V-72207" selected="true"/>
+    <select idref="V-72209" selected="true"/>
+    <select idref="V-72211" selected="true"/>
+    <select idref="V-72213" selected="true"/>
+    <select idref="V-72215" selected="true"/>
+    <select idref="V-72217" selected="true"/>
+    <select idref="V-72219" selected="true"/>
+    <select idref="V-72221" selected="true"/>
+    <select idref="V-72223" selected="true"/>
+    <select idref="V-72225" selected="true"/>
+    <select idref="V-72227" selected="true"/>
+    <select idref="V-72229" selected="true"/>
+    <select idref="V-72231" selected="true"/>
+    <select idref="V-72233" selected="true"/>
+    <select idref="V-72235" selected="true"/>
+    <select idref="V-72237" selected="true"/>
+    <select idref="V-72239" selected="true"/>
+    <select idref="V-72241" selected="true"/>
+    <select idref="V-72243" selected="true"/>
+    <select idref="V-72245" selected="true"/>
+    <select idref="V-72247" selected="true"/>
+    <select idref="V-72249" selected="true"/>
+    <select idref="V-72251" selected="true"/>
+    <select idref="V-72253" selected="true"/>
+    <select idref="V-72255" selected="true"/>
+    <select idref="V-72257" selected="true"/>
+    <select idref="V-72259" selected="true"/>
+    <select idref="V-72261" selected="true"/>
+    <select idref="V-72263" selected="true"/>
+    <select idref="V-72265" selected="true"/>
+    <select idref="V-72267" selected="true"/>
+    <select idref="V-72269" selected="true"/>
+    <select idref="V-72271" selected="true"/>
+    <select idref="V-72273" selected="true"/>
+    <select idref="V-72275" selected="true"/>
+    <select idref="V-72277" selected="true"/>
+    <select idref="V-72279" selected="true"/>
+    <select idref="V-72281" selected="true"/>
+    <select idref="V-72283" selected="true"/>
+    <select idref="V-72285" selected="true"/>
+    <select idref="V-72287" selected="true"/>
+    <select idref="V-72289" selected="true"/>
+    <select idref="V-72291" selected="true"/>
+    <select idref="V-72293" selected="true"/>
+    <select idref="V-72295" selected="true"/>
+    <select idref="V-72297" selected="true"/>
+    <select idref="V-72299" selected="true"/>
+    <select idref="V-72301" selected="true"/>
+    <select idref="V-72303" selected="true"/>
+    <select idref="V-72305" selected="true"/>
+    <select idref="V-72307" selected="true"/>
+    <select idref="V-72309" selected="true"/>
+    <select idref="V-72311" selected="true"/>
+    <select idref="V-72313" selected="true"/>
+    <select idref="V-72315" selected="true"/>
+    <select idref="V-72317" selected="true"/>
+    <select idref="V-72319" selected="true"/>
+    <select idref="V-72417" selected="true"/>
+    <select idref="V-72427" selected="true"/>
+    <select idref="V-72433" selected="true"/>
+    <select idref="V-72435" selected="true"/>
+    <select idref="V-73155" selected="true"/>
+    <select idref="V-73157" selected="true"/>
+    <select idref="V-73159" selected="true"/>
+    <select idref="V-73161" selected="true"/>
+    <select idref="V-73163" selected="true"/>
+    <select idref="V-73165" selected="true"/>
+    <select idref="V-73167" selected="true"/>
+    <select idref="V-73171" selected="true"/>
+    <select idref="V-73173" selected="true"/>
+    <select idref="V-73175" selected="true"/>
+    <select idref="V-73177" 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-71849" selected="true"/>
+    <select idref="V-71855" selected="true"/>
+    <select idref="V-71859" selected="true"/>
+    <select idref="V-71861" selected="true"/>
+    <select idref="V-71863" selected="true"/>
+    <select idref="V-71891" selected="true"/>
+    <select idref="V-71893" selected="true"/>
+    <select idref="V-71895" selected="true"/>
+    <select idref="V-71897" selected="true"/>
+    <select idref="V-71899" selected="true"/>
+    <select idref="V-71901" selected="true"/>
+    <select idref="V-71903" selected="true"/>
+    <select idref="V-71905" selected="true"/>
+    <select idref="V-71907" selected="true"/>
+    <select idref="V-71909" selected="true"/>
+    <select idref="V-71911" selected="true"/>
+    <select idref="V-71913" selected="true"/>
+    <select idref="V-71915" selected="true"/>
+    <select idref="V-71917" selected="true"/>
+    <select idref="V-71919" selected="true"/>
+    <select idref="V-71921" selected="true"/>
+    <select idref="V-71923" selected="true"/>
+    <select idref="V-71925" selected="true"/>
+    <select idref="V-71927" selected="true"/>
+    <select idref="V-71929" selected="true"/>
+    <select idref="V-71931" selected="true"/>
+    <select idref="V-71933" selected="true"/>
+    <select idref="V-71935" selected="true"/>
+    <select idref="V-71937" selected="true"/>
+    <select idref="V-71939" selected="true"/>
+    <select idref="V-71941" selected="true"/>
+    <select idref="V-71943" selected="true"/>
+    <select idref="V-71945" selected="true"/>
+    <select idref="V-71947" selected="true"/>
+    <select idref="V-71949" selected="true"/>
+    <select idref="V-71951" selected="true"/>
+    <select idref="V-71953" selected="true"/>
+    <select idref="V-71955" selected="true"/>
+    <select idref="V-71957" selected="true"/>
+    <select idref="V-71959" selected="true"/>
+    <select idref="V-71961" selected="true"/>
+    <select idref="V-71963" selected="true"/>
+    <select idref="V-71965" selected="true"/>
+    <select idref="V-71967" selected="true"/>
+    <select idref="V-71969" selected="true"/>
+    <select idref="V-71971" selected="true"/>
+    <select idref="V-71973" selected="true"/>
+    <select idref="V-71975" selected="true"/>
+    <select idref="V-71977" selected="true"/>
+    <select idref="V-71979" selected="true"/>
+    <select idref="V-71981" selected="true"/>
+    <select idref="V-71983" selected="true"/>
+    <select idref="V-71985" selected="true"/>
+    <select idref="V-71987" selected="true"/>
+    <select idref="V-71989" selected="true"/>
+    <select idref="V-71991" selected="true"/>
+    <select idref="V-71993" selected="true"/>
+    <select idref="V-71995" selected="true"/>
+    <select idref="V-71997" selected="true"/>
+    <select idref="V-71999" selected="true"/>
+    <select idref="V-72001" selected="true"/>
+    <select idref="V-72003" selected="true"/>
+    <select idref="V-72005" selected="true"/>
+    <select idref="V-72007" selected="true"/>
+    <select idref="V-72009" selected="true"/>
+    <select idref="V-72011" selected="true"/>
+    <select idref="V-72013" selected="true"/>
+    <select idref="V-72015" selected="true"/>
+    <select idref="V-72017" selected="true"/>
+    <select idref="V-72019" selected="true"/>
+    <select idref="V-72021" selected="true"/>
+    <select idref="V-72023" selected="true"/>
+    <select idref="V-72025" selected="true"/>
+    <select idref="V-72027" selected="true"/>
+    <select idref="V-72029" selected="true"/>
+    <select idref="V-72031" selected="true"/>
+    <select idref="V-72033" selected="true"/>
+    <select idref="V-72035" selected="true"/>
+    <select idref="V-72037" selected="true"/>
+    <select idref="V-72039" selected="true"/>
+    <select idref="V-72041" selected="true"/>
+    <select idref="V-72043" selected="true"/>
+    <select idref="V-72045" selected="true"/>
+    <select idref="V-72047" selected="true"/>
+    <select idref="V-72049" selected="true"/>
+    <select idref="V-72051" selected="true"/>
+    <select idref="V-72053" selected="true"/>
+    <select idref="V-72055" selected="true"/>
+    <select idref="V-72057" selected="true"/>
+    <select idref="V-72059" selected="true"/>
+    <select idref="V-72061" selected="true"/>
+    <select idref="V-72063" selected="true"/>
+    <select idref="V-72065" selected="true"/>
+    <select idref="V-72067" selected="true"/>
+    <select idref="V-72069" selected="true"/>
+    <select idref="V-72071" selected="true"/>
+    <select idref="V-72073" selected="true"/>
+    <select idref="V-72075" selected="true"/>
+    <select idref="V-72077" selected="true"/>
+    <select idref="V-72079" selected="true"/>
+    <select idref="V-72081" selected="true"/>
+    <select idref="V-72083" selected="true"/>
+    <select idref="V-72085" selected="true"/>
+    <select idref="V-72087" selected="true"/>
+    <select idref="V-72089" selected="true"/>
+    <select idref="V-72091" selected="true"/>
+    <select idref="V-72093" selected="true"/>
+    <select idref="V-72095" selected="true"/>
+    <select idref="V-72097" selected="true"/>
+    <select idref="V-72099" selected="true"/>
+    <select idref="V-72101" selected="true"/>
+    <select idref="V-72103" selected="true"/>
+    <select idref="V-72105" selected="true"/>
+    <select idref="V-72107" selected="true"/>
+    <select idref="V-72109" selected="true"/>
+    <select idref="V-72111" selected="true"/>
+    <select idref="V-72113" selected="true"/>
+    <select idref="V-72115" selected="true"/>
+    <select idref="V-72117" selected="true"/>
+    <select idref="V-72119" selected="true"/>
+    <select idref="V-72121" selected="true"/>
+    <select idref="V-72123" selected="true"/>
+    <select idref="V-72125" selected="true"/>
+    <select idref="V-72127" selected="true"/>
+    <select idref="V-72129" selected="true"/>
+    <select idref="V-72131" selected="true"/>
+    <select idref="V-72133" selected="true"/>
+    <select idref="V-72135" selected="true"/>
+    <select idref="V-72137" selected="true"/>
+    <select idref="V-72139" selected="true"/>
+    <select idref="V-72141" selected="true"/>
+    <select idref="V-72143" selected="true"/>
+    <select idref="V-72145" selected="true"/>
+    <select idref="V-72147" selected="true"/>
+    <select idref="V-72149" selected="true"/>
+    <select idref="V-72151" selected="true"/>
+    <select idref="V-72153" selected="true"/>
+    <select idref="V-72155" selected="true"/>
+    <select idref="V-72157" selected="true"/>
+    <select idref="V-72159" selected="true"/>
+    <select idref="V-72161" selected="true"/>
+    <select idref="V-72163" selected="true"/>
+    <select idref="V-72165" selected="true"/>
+    <select idref="V-72167" selected="true"/>
+    <select idref="V-72169" selected="true"/>
+    <select idref="V-72171" selected="true"/>
+    <select idref="V-72173" selected="true"/>
+    <select idref="V-72175" selected="true"/>
+    <select idref="V-72177" selected="true"/>
+    <select idref="V-72179" selected="true"/>
+    <select idref="V-72181" selected="true"/>
+    <select idref="V-72183" selected="true"/>
+    <select idref="V-72185" selected="true"/>
+    <select idref="V-72187" selected="true"/>
+    <select idref="V-72189" selected="true"/>
+    <select idref="V-72191" selected="true"/>
+    <select idref="V-72193" selected="true"/>
+    <select idref="V-72195" selected="true"/>
+    <select idref="V-72197" selected="true"/>
+    <select idref="V-72199" selected="true"/>
+    <select idref="V-72201" selected="true"/>
+    <select idref="V-72203" selected="true"/>
+    <select idref="V-72205" selected="true"/>
+    <select idref="V-72207" selected="true"/>
+    <select idref="V-72209" selected="true"/>
+    <select idref="V-72211" selected="true"/>
+    <select idref="V-72213" selected="true"/>
+    <select idref="V-72215" selected="true"/>
+    <select idref="V-72217" selected="true"/>
+    <select idref="V-72219" selected="true"/>
+    <select idref="V-72221" selected="true"/>
+    <select idref="V-72223" selected="true"/>
+    <select idref="V-72225" selected="true"/>
+    <select idref="V-72227" selected="true"/>
+    <select idref="V-72229" selected="true"/>
+    <select idref="V-72231" selected="true"/>
+    <select idref="V-72233" selected="true"/>
+    <select idref="V-72235" selected="true"/>
+    <select idref="V-72237" selected="true"/>
+    <select idref="V-72239" selected="true"/>
+    <select idref="V-72241" selected="true"/>
+    <select idref="V-72243" selected="true"/>
+    <select idref="V-72245" selected="true"/>
+    <select idref="V-72247" selected="true"/>
+    <select idref="V-72249" selected="true"/>
+    <select idref="V-72251" selected="true"/>
+    <select idref="V-72253" selected="true"/>
+    <select idref="V-72255" selected="true"/>
+    <select idref="V-72257" selected="true"/>
+    <select idref="V-72259" selected="true"/>
+    <select idref="V-72261" selected="true"/>
+    <select idref="V-72263" selected="true"/>
+    <select idref="V-72265" selected="true"/>
+    <select idref="V-72267" selected="true"/>
+    <select idref="V-72269" selected="true"/>
+    <select idref="V-72271" selected="true"/>
+    <select idref="V-72273" selected="true"/>
+    <select idref="V-72275" selected="true"/>
+    <select idref="V-72277" selected="true"/>
+    <select idref="V-72279" selected="true"/>
+    <select idref="V-72281" selected="true"/>
+    <select idref="V-72283" selected="true"/>
+    <select idref="V-72285" selected="true"/>
+    <select idref="V-72287" selected="true"/>
+    <select idref="V-72289" selected="true"/>
+    <select idref="V-72291" selected="true"/>
+    <select idref="V-72293" selected="true"/>
+    <select idref="V-72295" selected="true"/>
+    <select idref="V-72297" selected="true"/>
+    <select idref="V-72299" selected="true"/>
+    <select idref="V-72301" selected="true"/>
+    <select idref="V-72303" selected="true"/>
+    <select idref="V-72305" selected="true"/>
+    <select idref="V-72307" selected="true"/>
+    <select idref="V-72309" selected="true"/>
+    <select idref="V-72311" selected="true"/>
+    <select idref="V-72313" selected="true"/>
+    <select idref="V-72315" selected="true"/>
+    <select idref="V-72317" selected="true"/>
+    <select idref="V-72319" selected="true"/>
+    <select idref="V-72417" selected="true"/>
+    <select idref="V-72427" selected="true"/>
+    <select idref="V-72433" selected="true"/>
+    <select idref="V-72435" selected="true"/>
+    <select idref="V-73155" selected="true"/>
+    <select idref="V-73157" selected="true"/>
+    <select idref="V-73159" selected="true"/>
+    <select idref="V-73161" selected="true"/>
+    <select idref="V-73163" selected="true"/>
+    <select idref="V-73165" selected="true"/>
+    <select idref="V-73167" selected="true"/>
+    <select idref="V-73171" selected="true"/>
+    <select idref="V-73173" selected="true"/>
+    <select idref="V-73175" selected="true"/>
+    <select idref="V-73177" selected="true"/>
+  </Profile>
+  <Profile id="MAC-3_Classified">
+    <title>III - Administrative Classified</title>
+    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
+    <select idref="V-71849" selected="true"/>
+    <select idref="V-71855" selected="true"/>
+    <select idref="V-71859" selected="true"/>
+    <select idref="V-71861" selected="true"/>
+    <select idref="V-71863" selected="true"/>
+    <select idref="V-71891" selected="true"/>
+    <select idref="V-71893" selected="true"/>
+    <select idref="V-71895" selected="true"/>
+    <select idref="V-71897" selected="true"/>
+    <select idref="V-71899" selected="true"/>
+    <select idref="V-71901" selected="true"/>
+    <select idref="V-71903" selected="true"/>
+    <select idref="V-71905" selected="true"/>
+    <select idref="V-71907" selected="true"/>
+    <select idref="V-71909" selected="true"/>
+    <select idref="V-71911" selected="true"/>
+    <select idref="V-71913" selected="true"/>
+    <select idref="V-71915" selected="true"/>
+    <select idref="V-71917" selected="true"/>
+    <select idref="V-71919" selected="true"/>
+    <select idref="V-71921" selected="true"/>
+    <select idref="V-71923" selected="true"/>
+    <select idref="V-71925" selected="true"/>
+    <select idref="V-71927" selected="true"/>
+    <select idref="V-71929" selected="true"/>
+    <select idref="V-71931" selected="true"/>
+    <select idref="V-71933" selected="true"/>
+    <select idref="V-71935" selected="true"/>
+    <select idref="V-71937" selected="true"/>
+    <select idref="V-71939" selected="true"/>
+    <select idref="V-71941" selected="true"/>
+    <select idref="V-71943" selected="true"/>
+    <select idref="V-71945" selected="true"/>
+    <select idref="V-71947" selected="true"/>
+    <select idref="V-71949" selected="true"/>
+    <select idref="V-71951" selected="true"/>
+    <select idref="V-71953" selected="true"/>
+    <select idref="V-71955" selected="true"/>
+    <select idref="V-71957" selected="true"/>
+    <select idref="V-71959" selected="true"/>
+    <select idref="V-71961" selected="true"/>
+    <select idref="V-71963" selected="true"/>
+    <select idref="V-71965" selected="true"/>
+    <select idref="V-71967" selected="true"/>
+    <select idref="V-71969" selected="true"/>
+    <select idref="V-71971" selected="true"/>
+    <select idref="V-71973" selected="true"/>
+    <select idref="V-71975" selected="true"/>
+    <select idref="V-71977" selected="true"/>
+    <select idref="V-71979" selected="true"/>
+    <select idref="V-71981" selected="true"/>
+    <select idref="V-71983" selected="true"/>
+    <select idref="V-71985" selected="true"/>
+    <select idref="V-71987" selected="true"/>
+    <select idref="V-71989" selected="true"/>
+    <select idref="V-71991" selected="true"/>
+    <select idref="V-71993" selected="true"/>
+    <select idref="V-71995" selected="true"/>
+    <select idref="V-71997" selected="true"/>
+    <select idref="V-71999" selected="true"/>
+    <select idref="V-72001" selected="true"/>
+    <select idref="V-72003" selected="true"/>
+    <select idref="V-72005" selected="true"/>
+    <select idref="V-72007" selected="true"/>
+    <select idref="V-72009" selected="true"/>
+    <select idref="V-72011" selected="true"/>
+    <select idref="V-72013" selected="true"/>
+    <select idref="V-72015" selected="true"/>
+    <select idref="V-72017" selected="true"/>
+    <select idref="V-72019" selected="true"/>
+    <select idref="V-72021" selected="true"/>
+    <select idref="V-72023" selected="true"/>
+    <select idref="V-72025" selected="true"/>
+    <select idref="V-72027" selected="true"/>
+    <select idref="V-72029" selected="true"/>
+    <select idref="V-72031" selected="true"/>
+    <select idref="V-72033" selected="true"/>
+    <select idref="V-72035" selected="true"/>
+    <select idref="V-72037" selected="true"/>
+    <select idref="V-72039" selected="true"/>
+    <select idref="V-72041" selected="true"/>
+    <select idref="V-72043" selected="true"/>
+    <select idref="V-72045" selected="true"/>
+    <select idref="V-72047" selected="true"/>
+    <select idref="V-72049" selected="true"/>
+    <select idref="V-72051" selected="true"/>
+    <select idref="V-72053" selected="true"/>
+    <select idref="V-72055" selected="true"/>
+    <select idref="V-72057" selected="true"/>
+    <select idref="V-72059" selected="true"/>
+    <select idref="V-72061" selected="true"/>
+    <select idref="V-72063" selected="true"/>
+    <select idref="V-72065" selected="true"/>
+    <select idref="V-72067" selected="true"/>
+    <select idref="V-72069" selected="true"/>
+    <select idref="V-72071" selected="true"/>
+    <select idref="V-72073" selected="true"/>
+    <select idref="V-72075" selected="true"/>
+    <select idref="V-72077" selected="true"/>
+    <select idref="V-72079" selected="true"/>
+    <select idref="V-72081" selected="true"/>
+    <select idref="V-72083" selected="true"/>
+    <select idref="V-72085" selected="true"/>
+    <select idref="V-72087" selected="true"/>
+    <select idref="V-72089" selected="true"/>
+    <select idref="V-72091" selected="true"/>
+    <select idref="V-72093" selected="true"/>
+    <select idref="V-72095" selected="true"/>
+    <select idref="V-72097" selected="true"/>
+    <select idref="V-72099" selected="true"/>
+    <select idref="V-72101" selected="true"/>
+    <select idref="V-72103" selected="true"/>
+    <select idref="V-72105" selected="true"/>
+    <select idref="V-72107" selected="true"/>
+    <select idref="V-72109" selected="true"/>
+    <select idref="V-72111" selected="true"/>
+    <select idref="V-72113" selected="true"/>
+    <select idref="V-72115" selected="true"/>
+    <select idref="V-72117" selected="true"/>
+    <select idref="V-72119" selected="true"/>
+    <select idref="V-72121" selected="true"/>
+    <select idref="V-72123" selected="true"/>
+    <select idref="V-72125" selected="true"/>
+    <select idref="V-72127" selected="true"/>
+    <select idref="V-72129" selected="true"/>
+    <select idref="V-72131" selected="true"/>
+    <select idref="V-72133" selected="true"/>
+    <select idref="V-72135" selected="true"/>
+    <select idref="V-72137" selected="true"/>
+    <select idref="V-72139" selected="true"/>
+    <select idref="V-72141" selected="true"/>
+    <select idref="V-72143" selected="true"/>
+    <select idref="V-72145" selected="true"/>
+    <select idref="V-72147" selected="true"/>
+    <select idref="V-72149" selected="true"/>
+    <select idref="V-72151" selected="true"/>
+    <select idref="V-72153" selected="true"/>
+    <select idref="V-72155" selected="true"/>
+    <select idref="V-72157" selected="true"/>
+    <select idref="V-72159" selected="true"/>
+    <select idref="V-72161" selected="true"/>
+    <select idref="V-72163" selected="true"/>
+    <select idref="V-72165" selected="true"/>
+    <select idref="V-72167" selected="true"/>
+    <select idref="V-72169" selected="true"/>
+    <select idref="V-72171" selected="true"/>
+    <select idref="V-72173" selected="true"/>
+    <select idref="V-72175" selected="true"/>
+    <select idref="V-72177" selected="true"/>
+    <select idref="V-72179" selected="true"/>
+    <select idref="V-72181" selected="true"/>
+    <select idref="V-72183" selected="true"/>
+    <select idref="V-72185" selected="true"/>
+    <select idref="V-72187" selected="true"/>
+    <select idref="V-72189" selected="true"/>
+    <select idref="V-72191" selected="true"/>
+    <select idref="V-72193" selected="true"/>
+    <select idref="V-72195" selected="true"/>
+    <select idref="V-72197" selected="true"/>
+    <select idref="V-72199" selected="true"/>
+    <select idref="V-72201" selected="true"/>
+    <select idref="V-72203" selected="true"/>
+    <select idref="V-72205" selected="true"/>
+    <select idref="V-72207" selected="true"/>
+    <select idref="V-72209" selected="true"/>
+    <select idref="V-72211" selected="true"/>
+    <select idref="V-72213" selected="true"/>
+    <select idref="V-72215" selected="true"/>
+    <select idref="V-72217" selected="true"/>
+    <select idref="V-72219" selected="true"/>
+    <select idref="V-72221" selected="true"/>
+    <select idref="V-72223" selected="true"/>
+    <select idref="V-72225" selected="true"/>
+    <select idref="V-72227" selected="true"/>
+    <select idref="V-72229" selected="true"/>
+    <select idref="V-72231" selected="true"/>
+    <select idref="V-72233" selected="true"/>
+    <select idref="V-72235" selected="true"/>
+    <select idref="V-72237" selected="true"/>
+    <select idref="V-72239" selected="true"/>
+    <select idref="V-72241" selected="true"/>
+    <select idref="V-72243" selected="true"/>
+    <select idref="V-72245" selected="true"/>
+    <select idref="V-72247" selected="true"/>
+    <select idref="V-72249" selected="true"/>
+    <select idref="V-72251" selected="true"/>
+    <select idref="V-72253" selected="true"/>
+    <select idref="V-72255" selected="true"/>
+    <select idref="V-72257" selected="true"/>
+    <select idref="V-72259" selected="true"/>
+    <select idref="V-72261" selected="true"/>
+    <select idref="V-72263" selected="true"/>
+    <select idref="V-72265" selected="true"/>
+    <select idref="V-72267" selected="true"/>
+    <select idref="V-72269" selected="true"/>
+    <select idref="V-72271" selected="true"/>
+    <select idref="V-72273" selected="true"/>
+    <select idref="V-72275" selected="true"/>
+    <select idref="V-72277" selected="true"/>
+    <select idref="V-72279" selected="true"/>
+    <select idref="V-72281" selected="true"/>
+    <select idref="V-72283" selected="true"/>
+    <select idref="V-72285" selected="true"/>
+    <select idref="V-72287" selected="true"/>
+    <select idref="V-72289" selected="true"/>
+    <select idref="V-72291" selected="true"/>
+    <select idref="V-72293" selected="true"/>
+    <select idref="V-72295" selected="true"/>
+    <select idref="V-72297" selected="true"/>
+    <select idref="V-72299" selected="true"/>
+    <select idref="V-72301" selected="true"/>
+    <select idref="V-72303" selected="true"/>
+    <select idref="V-72305" selected="true"/>
+    <select idref="V-72307" selected="true"/>
+    <select idref="V-72309" selected="true"/>
+    <select idref="V-72311" selected="true"/>
+    <select idref="V-72313" selected="true"/>
+    <select idref="V-72315" selected="true"/>
+    <select idref="V-72317" selected="true"/>
+    <select idref="V-72319" selected="true"/>
+    <select idref="V-72417" selected="true"/>
+    <select idref="V-72427" selected="true"/>
+    <select idref="V-72433" selected="true"/>
+    <select idref="V-72435" selected="true"/>
+    <select idref="V-73155" selected="true"/>
+    <select idref="V-73157" selected="true"/>
+    <select idref="V-73159" selected="true"/>
+    <select idref="V-73161" selected="true"/>
+    <select idref="V-73163" selected="true"/>
+    <select idref="V-73165" selected="true"/>
+    <select idref="V-73167" selected="true"/>
+    <select idref="V-73171" selected="true"/>
+    <select idref="V-73173" selected="true"/>
+    <select idref="V-73175" selected="true"/>
+    <select idref="V-73177" selected="true"/>
+  </Profile>
+  <Profile id="MAC-3_Public">
+    <title>III - Administrative Public</title>
+    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
+    <select idref="V-71849" selected="true"/>
+    <select idref="V-71855" selected="true"/>
+    <select idref="V-71859" selected="true"/>
+    <select idref="V-71861" selected="true"/>
+    <select idref="V-71863" selected="true"/>
+    <select idref="V-71891" selected="true"/>
+    <select idref="V-71893" selected="true"/>
+    <select idref="V-71895" selected="true"/>
+    <select idref="V-71897" selected="true"/>
+    <select idref="V-71899" selected="true"/>
+    <select idref="V-71901" selected="true"/>
+    <select idref="V-71903" selected="true"/>
+    <select idref="V-71905" selected="true"/>
+    <select idref="V-71907" selected="true"/>
+    <select idref="V-71909" selected="true"/>
+    <select idref="V-71911" selected="true"/>
+    <select idref="V-71913" selected="true"/>
+    <select idref="V-71915" selected="true"/>
+    <select idref="V-71917" selected="true"/>
+    <select idref="V-71919" selected="true"/>
+    <select idref="V-71921" selected="true"/>
+    <select idref="V-71923" selected="true"/>
+    <select idref="V-71925" selected="true"/>
+    <select idref="V-71927" selected="true"/>
+    <select idref="V-71929" selected="true"/>
+    <select idref="V-71931" selected="true"/>
+    <select idref="V-71933" selected="true"/>
+    <select idref="V-71935" selected="true"/>
+    <select idref="V-71937" selected="true"/>
+    <select idref="V-71939" selected="true"/>
+    <select idref="V-71941" selected="true"/>
+    <select idref="V-71943" selected="true"/>
+    <select idref="V-71945" selected="true"/>
+    <select idref="V-71947" selected="true"/>
+    <select idref="V-71949" selected="true"/>
+    <select idref="V-71951" selected="true"/>
+    <select idref="V-71953" selected="true"/>
+    <select idref="V-71955" selected="true"/>
+    <select idref="V-71957" selected="true"/>
+    <select idref="V-71959" selected="true"/>
+    <select idref="V-71961" selected="true"/>
+    <select idref="V-71963" selected="true"/>
+    <select idref="V-71965" selected="true"/>
+    <select idref="V-71967" selected="true"/>
+    <select idref="V-71969" selected="true"/>
+    <select idref="V-71971" selected="true"/>
+    <select idref="V-71973" selected="true"/>
+    <select idref="V-71975" selected="true"/>
+    <select idref="V-71977" selected="true"/>
+    <select idref="V-71979" selected="true"/>
+    <select idref="V-71981" selected="true"/>
+    <select idref="V-71983" selected="true"/>
+    <select idref="V-71985" selected="true"/>
+    <select idref="V-71987" selected="true"/>
+    <select idref="V-71989" selected="true"/>
+    <select idref="V-71991" selected="true"/>
+    <select idref="V-71993" selected="true"/>
+    <select idref="V-71995" selected="true"/>
+    <select idref="V-71997" selected="true"/>
+    <select idref="V-71999" selected="true"/>
+    <select idref="V-72001" selected="true"/>
+    <select idref="V-72003" selected="true"/>
+    <select idref="V-72005" selected="true"/>
+    <select idref="V-72007" selected="true"/>
+    <select idref="V-72009" selected="true"/>
+    <select idref="V-72011" selected="true"/>
+    <select idref="V-72013" selected="true"/>
+    <select idref="V-72015" selected="true"/>
+    <select idref="V-72017" selected="true"/>
+    <select idref="V-72019" selected="true"/>
+    <select idref="V-72021" selected="true"/>
+    <select idref="V-72023" selected="true"/>
+    <select idref="V-72025" selected="true"/>
+    <select idref="V-72027" selected="true"/>
+    <select idref="V-72029" selected="true"/>
+    <select idref="V-72031" selected="true"/>
+    <select idref="V-72033" selected="true"/>
+    <select idref="V-72035" selected="true"/>
+    <select idref="V-72037" selected="true"/>
+    <select idref="V-72039" selected="true"/>
+    <select idref="V-72041" selected="true"/>
+    <select idref="V-72043" selected="true"/>
+    <select idref="V-72045" selected="true"/>
+    <select idref="V-72047" selected="true"/>
+    <select idref="V-72049" selected="true"/>
+    <select idref="V-72051" selected="true"/>
+    <select idref="V-72053" selected="true"/>
+    <select idref="V-72055" selected="true"/>
+    <select idref="V-72057" selected="true"/>
+    <select idref="V-72059" selected="true"/>
+    <select idref="V-72061" selected="true"/>
+    <select idref="V-72063" selected="true"/>
+    <select idref="V-72065" selected="true"/>
+    <select idref="V-72067" selected="true"/>
+    <select idref="V-72069" selected="true"/>
+    <select idref="V-72071" selected="true"/>
+    <select idref="V-72073" selected="true"/>
+    <select idref="V-72075" selected="true"/>
+    <select idref="V-72077" selected="true"/>
+    <select idref="V-72079" selected="true"/>
+    <select idref="V-72081" selected="true"/>
+    <select idref="V-72083" selected="true"/>
+    <select idref="V-72085" selected="true"/>
+    <select idref="V-72087" selected="true"/>
+    <select idref="V-72089" selected="true"/>
+    <select idref="V-72091" selected="true"/>
+    <select idref="V-72093" selected="true"/>
+    <select idref="V-72095" selected="true"/>
+    <select idref="V-72097" selected="true"/>
+    <select idref="V-72099" selected="true"/>
+    <select idref="V-72101" selected="true"/>
+    <select idref="V-72103" selected="true"/>
+    <select idref="V-72105" selected="true"/>
+    <select idref="V-72107" selected="true"/>
+    <select idref="V-72109" selected="true"/>
+    <select idref="V-72111" selected="true"/>
+    <select idref="V-72113" selected="true"/>
+    <select idref="V-72115" selected="true"/>
+    <select idref="V-72117" selected="true"/>
+    <select idref="V-72119" selected="true"/>
+    <select idref="V-72121" selected="true"/>
+    <select idref="V-72123" selected="true"/>
+    <select idref="V-72125" selected="true"/>
+    <select idref="V-72127" selected="true"/>
+    <select idref="V-72129" selected="true"/>
+    <select idref="V-72131" selected="true"/>
+    <select idref="V-72133" selected="true"/>
+    <select idref="V-72135" selected="true"/>
+    <select idref="V-72137" selected="true"/>
+    <select idref="V-72139" selected="true"/>
+    <select idref="V-72141" selected="true"/>
+    <select idref="V-72143" selected="true"/>
+    <select idref="V-72145" selected="true"/>
+    <select idref="V-72147" selected="true"/>
+    <select idref="V-72149" selected="true"/>
+    <select idref="V-72151" selected="true"/>
+    <select idref="V-72153" selected="true"/>
+    <select idref="V-72155" selected="true"/>
+    <select idref="V-72157" selected="true"/>
+    <select idref="V-72159" selected="true"/>
+    <select idref="V-72161" selected="true"/>
+    <select idref="V-72163" selected="true"/>
+    <select idref="V-72165" selected="true"/>
+    <select idref="V-72167" selected="true"/>
+    <select idref="V-72169" selected="true"/>
+    <select idref="V-72171" selected="true"/>
+    <select idref="V-72173" selected="true"/>
+    <select idref="V-72175" selected="true"/>
+    <select idref="V-72177" selected="true"/>
+    <select idref="V-72179" selected="true"/>
+    <select idref="V-72181" selected="true"/>
+    <select idref="V-72183" selected="true"/>
+    <select idref="V-72185" selected="true"/>
+    <select idref="V-72187" selected="true"/>
+    <select idref="V-72189" selected="true"/>
+    <select idref="V-72191" selected="true"/>
+    <select idref="V-72193" selected="true"/>
+    <select idref="V-72195" selected="true"/>
+    <select idref="V-72197" selected="true"/>
+    <select idref="V-72199" selected="true"/>
+    <select idref="V-72201" selected="true"/>
+    <select idref="V-72203" selected="true"/>
+    <select idref="V-72205" selected="true"/>
+    <select idref="V-72207" selected="true"/>
+    <select idref="V-72209" selected="true"/>
+    <select idref="V-72211" selected="true"/>
+    <select idref="V-72213" selected="true"/>
+    <select idref="V-72215" selected="true"/>
+    <select idref="V-72217" selected="true"/>
+    <select idref="V-72219" selected="true"/>
+    <select idref="V-72221" selected="true"/>
+    <select idref="V-72223" selected="true"/>
+    <select idref="V-72225" selected="true"/>
+    <select idref="V-72227" selected="true"/>
+    <select idref="V-72229" selected="true"/>
+    <select idref="V-72231" selected="true"/>
+    <select idref="V-72233" selected="true"/>
+    <select idref="V-72235" selected="true"/>
+    <select idref="V-72237" selected="true"/>
+    <select idref="V-72239" selected="true"/>
+    <select idref="V-72241" selected="true"/>
+    <select idref="V-72243" selected="true"/>
+    <select idref="V-72245" selected="true"/>
+    <select idref="V-72247" selected="true"/>
+    <select idref="V-72249" selected="true"/>
+    <select idref="V-72251" selected="true"/>
+    <select idref="V-72253" selected="true"/>
+    <select idref="V-72255" selected="true"/>
+    <select idref="V-72257" selected="true"/>
+    <select idref="V-72259" selected="true"/>
+    <select idref="V-72261" selected="true"/>
+    <select idref="V-72263" selected="true"/>
+    <select idref="V-72265" selected="true"/>
+    <select idref="V-72267" selected="true"/>
+    <select idref="V-72269" selected="true"/>
+    <select idref="V-72271" selected="true"/>
+    <select idref="V-72273" selected="true"/>
+    <select idref="V-72275" selected="true"/>
+    <select idref="V-72277" selected="true"/>
+    <select idref="V-72279" selected="true"/>
+    <select idref="V-72281" selected="true"/>
+    <select idref="V-72283" selected="true"/>
+    <select idref="V-72285" selected="true"/>
+    <select idref="V-72287" selected="true"/>
+    <select idref="V-72289" selected="true"/>
+    <select idref="V-72291" selected="true"/>
+    <select idref="V-72293" selected="true"/>
+    <select idref="V-72295" selected="true"/>
+    <select idref="V-72297" selected="true"/>
+    <select idref="V-72299" selected="true"/>
+    <select idref="V-72301" selected="true"/>
+    <select idref="V-72303" selected="true"/>
+    <select idref="V-72305" selected="true"/>
+    <select idref="V-72307" selected="true"/>
+    <select idref="V-72309" selected="true"/>
+    <select idref="V-72311" selected="true"/>
+    <select idref="V-72313" selected="true"/>
+    <select idref="V-72315" selected="true"/>
+    <select idref="V-72317" selected="true"/>
+    <select idref="V-72319" selected="true"/>
+    <select idref="V-72417" selected="true"/>
+    <select idref="V-72427" selected="true"/>
+    <select idref="V-72433" selected="true"/>
+    <select idref="V-72435" selected="true"/>
+    <select idref="V-73155" selected="true"/>
+    <select idref="V-73157" selected="true"/>
+    <select idref="V-73159" selected="true"/>
+    <select idref="V-73161" selected="true"/>
+    <select idref="V-73163" selected="true"/>
+    <select idref="V-73165" selected="true"/>
+    <select idref="V-73167" selected="true"/>
+    <select idref="V-73171" selected="true"/>
+    <select idref="V-73173" selected="true"/>
+    <select idref="V-73175" selected="true"/>
+    <select idref="V-73177" selected="true"/>
+  </Profile>
+  <Profile id="MAC-3_Sensitive">
+    <title>III - Administrative Sensitive</title>
+    <description>&lt;ProfileDescription&gt;&lt;/ProfileDescription&gt;</description>
+    <select idref="V-71849" selected="true"/>
+    <select idref="V-71855" selected="true"/>
+    <select idref="V-71859" selected="true"/>
+    <select idref="V-71861" selected="true"/>
+    <select idref="V-71863" selected="true"/>
+    <select idref="V-71891" selected="true"/>
+    <select idref="V-71893" selected="true"/>
+    <select idref="V-71895" selected="true"/>
+    <select idref="V-71897" selected="true"/>
+    <select idref="V-71899" selected="true"/>
+    <select idref="V-71901" selected="true"/>
+    <select idref="V-71903" selected="true"/>
+    <select idref="V-71905" selected="true"/>
+    <select idref="V-71907" selected="true"/>
+    <select idref="V-71909" selected="true"/>
+    <select idref="V-71911" selected="true"/>
+    <select idref="V-71913" selected="true"/>
+    <select idref="V-71915" selected="true"/>
+    <select idref="V-71917" selected="true"/>
+    <select idref="V-71919" selected="true"/>
+    <select idref="V-71921" selected="true"/>
+    <select idref="V-71923" selected="true"/>
+    <select idref="V-71925" selected="true"/>
+    <select idref="V-71927" selected="true"/>
+    <select idref="V-71929" selected="true"/>
+    <select idref="V-71931" selected="true"/>
+    <select idref="V-71933" selected="true"/>
+    <select idref="V-71935" selected="true"/>
+    <select idref="V-71937" selected="true"/>
+    <select idref="V-71939" selected="true"/>
+    <select idref="V-71941" selected="true"/>
+    <select idref="V-71943" selected="true"/>
+    <select idref="V-71945" selected="true"/>
+    <select idref="V-71947" selected="true"/>
+    <select idref="V-71949" selected="true"/>
+    <select idref="V-71951" selected="true"/>
+    <select idref="V-71953" selected="true"/>
+    <select idref="V-71955" selected="true"/>
+    <select idref="V-71957" selected="true"/>
+    <select idref="V-71959" selected="true"/>
+    <select idref="V-71961" selected="true"/>
+    <select idref="V-71963" selected="true"/>
+    <select idref="V-71965" selected="true"/>
+    <select idref="V-71967" selected="true"/>
+    <select idref="V-71969" selected="true"/>
+    <select idref="V-71971" selected="true"/>
+    <select idref="V-71973" selected="true"/>
+    <select idref="V-71975" selected="true"/>
+    <select idref="V-71977" selected="true"/>
+    <select idref="V-71979" selected="true"/>
+    <select idref="V-71981" selected="true"/>
+    <select idref="V-71983" selected="true"/>
+    <select idref="V-71985" selected="true"/>
+    <select idref="V-71987" selected="true"/>
+    <select idref="V-71989" selected="true"/>
+    <select idref="V-71991" selected="true"/>
+    <select idref="V-71993" selected="true"/>
+    <select idref="V-71995" selected="true"/>
+    <select idref="V-71997" selected="true"/>
+    <select idref="V-71999" selected="true"/>
+    <select idref="V-72001" selected="true"/>
+    <select idref="V-72003" selected="true"/>
+    <select idref="V-72005" selected="true"/>
+    <select idref="V-72007" selected="true"/>
+    <select idref="V-72009" selected="true"/>
+    <select idref="V-72011" selected="true"/>
+    <select idref="V-72013" selected="true"/>
+    <select idref="V-72015" selected="true"/>
+    <select idref="V-72017" selected="true"/>
+    <select idref="V-72019" selected="true"/>
+    <select idref="V-72021" selected="true"/>
+    <select idref="V-72023" selected="true"/>
+    <select idref="V-72025" selected="true"/>
+    <select idref="V-72027" selected="true"/>
+    <select idref="V-72029" selected="true"/>
+    <select idref="V-72031" selected="true"/>
+    <select idref="V-72033" selected="true"/>
+    <select idref="V-72035" selected="true"/>
+    <select idref="V-72037" selected="true"/>
+    <select idref="V-72039" selected="true"/>
+    <select idref="V-72041" selected="true"/>
+    <select idref="V-72043" selected="true"/>
+    <select idref="V-72045" selected="true"/>
+    <select idref="V-72047" selected="true"/>
+    <select idref="V-72049" selected="true"/>
+    <select idref="V-72051" selected="true"/>
+    <select idref="V-72053" selected="true"/>
+    <select idref="V-72055" selected="true"/>
+    <select idref="V-72057" selected="true"/>
+    <select idref="V-72059" selected="true"/>
+    <select idref="V-72061" selected="true"/>
+    <select idref="V-72063" selected="true"/>
+    <select idref="V-72065" selected="true"/>
+    <select idref="V-72067" selected="true"/>
+    <select idref="V-72069" selected="true"/>
+    <select idref="V-72071" selected="true"/>
+    <select idref="V-72073" selected="true"/>
+    <select idref="V-72075" selected="true"/>
+    <select idref="V-72077" selected="true"/>
+    <select idref="V-72079" selected="true"/>
+    <select idref="V-72081" selected="true"/>
+    <select idref="V-72083" selected="true"/>
+    <select idref="V-72085" selected="true"/>
+    <select idref="V-72087" selected="true"/>
+    <select idref="V-72089" selected="true"/>
+    <select idref="V-72091" selected="true"/>
+    <select idref="V-72093" selected="true"/>
+    <select idref="V-72095" selected="true"/>
+    <select idref="V-72097" selected="true"/>
+    <select idref="V-72099" selected="true"/>
+    <select idref="V-72101" selected="true"/>
+    <select idref="V-72103" selected="true"/>
+    <select idref="V-72105" selected="true"/>
+    <select idref="V-72107" selected="true"/>
+    <select idref="V-72109" selected="true"/>
+    <select idref="V-72111" selected="true"/>
+    <select idref="V-72113" selected="true"/>
+    <select idref="V-72115" selected="true"/>
+    <select idref="V-72117" selected="true"/>
+    <select idref="V-72119" selected="true"/>
+    <select idref="V-72121" selected="true"/>
+    <select idref="V-72123" selected="true"/>
+    <select idref="V-72125" selected="true"/>
+    <select idref="V-72127" selected="true"/>
+    <select idref="V-72129" selected="true"/>
+    <select idref="V-72131" selected="true"/>
+    <select idref="V-72133" selected="true"/>
+    <select idref="V-72135" selected="true"/>
+    <select idref="V-72137" selected="true"/>
+    <select idref="V-72139" selected="true"/>
+    <select idref="V-72141" selected="true"/>
+    <select idref="V-72143" selected="true"/>
+    <select idref="V-72145" selected="true"/>
+    <select idref="V-72147" selected="true"/>
+    <select idref="V-72149" selected="true"/>
+    <select idref="V-72151" selected="true"/>
+    <select idref="V-72153" selected="true"/>
+    <select idref="V-72155" selected="true"/>
+    <select idref="V-72157" selected="true"/>
+    <select idref="V-72159" selected="true"/>
+    <select idref="V-72161" selected="true"/>
+    <select idref="V-72163" selected="true"/>
+    <select idref="V-72165" selected="true"/>
+    <select idref="V-72167" selected="true"/>
+    <select idref="V-72169" selected="true"/>
+    <select idref="V-72171" selected="true"/>
+    <select idref="V-72173" selected="true"/>
+    <select idref="V-72175" selected="true"/>
+    <select idref="V-72177" selected="true"/>
+    <select idref="V-72179" selected="true"/>
+    <select idref="V-72181" selected="true"/>
+    <select idref="V-72183" selected="true"/>
+    <select idref="V-72185" selected="true"/>
+    <select idref="V-72187" selected="true"/>
+    <select idref="V-72189" selected="true"/>
+    <select idref="V-72191" selected="true"/>
+    <select idref="V-72193" selected="true"/>
+    <select idref="V-72195" selected="true"/>
+    <select idref="V-72197" selected="true"/>
+    <select idref="V-72199" selected="true"/>
+    <select idref="V-72201" selected="true"/>
+    <select idref="V-72203" selected="true"/>
+    <select idref="V-72205" selected="true"/>
+    <select idref="V-72207" selected="true"/>
+    <select idref="V-72209" selected="true"/>
+    <select idref="V-72211" selected="true"/>
+    <select idref="V-72213" selected="true"/>
+    <select idref="V-72215" selected="true"/>
+    <select idref="V-72217" selected="true"/>
+    <select idref="V-72219" selected="true"/>
+    <select idref="V-72221" selected="true"/>
+    <select idref="V-72223" selected="true"/>
+    <select idref="V-72225" selected="true"/>
+    <select idref="V-72227" selected="true"/>
+    <select idref="V-72229" selected="true"/>
+    <select idref="V-72231" selected="true"/>
+    <select idref="V-72233" selected="true"/>
+    <select idref="V-72235" selected="true"/>
+    <select idref="V-72237" selected="true"/>
+    <select idref="V-72239" selected="true"/>
+    <select idref="V-72241" selected="true"/>
+    <select idref="V-72243" selected="true"/>
+    <select idref="V-72245" selected="true"/>
+    <select idref="V-72247" selected="true"/>
+    <select idref="V-72249" selected="true"/>
+    <select idref="V-72251" selected="true"/>
+    <select idref="V-72253" selected="true"/>
+    <select idref="V-72255" selected="true"/>
+    <select idref="V-72257" selected="true"/>
+    <select idref="V-72259" selected="true"/>
+    <select idref="V-72261" selected="true"/>
+    <select idref="V-72263" selected="true"/>
+    <select idref="V-72265" selected="true"/>
+    <select idref="V-72267" selected="true"/>
+    <select idref="V-72269" selected="true"/>
+    <select idref="V-72271" selected="true"/>
+    <select idref="V-72273" selected="true"/>
+    <select idref="V-72275" selected="true"/>
+    <select idref="V-72277" selected="true"/>
+    <select idref="V-72279" selected="true"/>
+    <select idref="V-72281" selected="true"/>
+    <select idref="V-72283" selected="true"/>
+    <select idref="V-72285" selected="true"/>
+    <select idref="V-72287" selected="true"/>
+    <select idref="V-72289" selected="true"/>
+    <select idref="V-72291" selected="true"/>
+    <select idref="V-72293" selected="true"/>
+    <select idref="V-72295" selected="true"/>
+    <select idref="V-72297" selected="true"/>
+    <select idref="V-72299" selected="true"/>
+    <select idref="V-72301" selected="true"/>
+    <select idref="V-72303" selected="true"/>
+    <select idref="V-72305" selected="true"/>
+    <select idref="V-72307" selected="true"/>
+    <select idref="V-72309" selected="true"/>
+    <select idref="V-72311" selected="true"/>
+    <select idref="V-72313" selected="true"/>
+    <select idref="V-72315" selected="true"/>
+    <select idref="V-72317" selected="true"/>
+    <select idref="V-72319" selected="true"/>
+    <select idref="V-72417" selected="true"/>
+    <select idref="V-72427" selected="true"/>
+    <select idref="V-72433" selected="true"/>
+    <select idref="V-72435" selected="true"/>
+    <select idref="V-73155" selected="true"/>
+    <select idref="V-73157" selected="true"/>
+    <select idref="V-73159" selected="true"/>
+    <select idref="V-73161" selected="true"/>
+    <select idref="V-73163" selected="true"/>
+    <select idref="V-73165" selected="true"/>
+    <select idref="V-73167" selected="true"/>
+    <select idref="V-73171" selected="true"/>
+    <select idref="V-73173" selected="true"/>
+    <select idref="V-73175" selected="true"/>
+    <select idref="V-73177" selected="true"/>
+  </Profile>
+  <Group id="V-71849">
+    <title>SRG-OS-000257-GPOS-00098</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86473r2_rule" severity="high" weight="10.0">
+      <version>RHEL-07-010010</version>
+      <title>The file permissions, ownership, and group membership of system files and commands must match the vendor values.</title>
+      <description>&lt;VulnDiscussion&gt;Discretionary access control is weakened if a user or group has access permissions to system files and directories greater than the default.
+
+Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000278-GPOS-00108&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001494</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001496</ident>
+      <fixtext fixref="F-78201r3_fix">Run the following command to determine which package owns the file:
+
+# rpm -qf &lt;filename&gt;
+
+Reset the permissions of files within a package with the following command:
+
+#rpm --setperms &lt;packagename&gt;
+
+Reset the user and group ownership of files within a package with the following command:
+
+#rpm --setugids &lt;packagename&gt;</fixtext>
+      <fix id="F-78201r3_fix"/>
+      <check system="C-72081r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the file permissions, ownership, and group membership of system files and commands match the vendor values.
+
+Check the file permissions, ownership, and group membership of system files and commands with the following command:
+
+# rpm -Va | grep '^.M'
+
+If there is any output from the command indicating that the ownership or group of a system file or command, or a system file, has permissions less restrictive than the default, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71855">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86479r2_rule" severity="high" weight="10.0">
+      <version>RHEL-07-010020</version>
+      <title>The cryptographic hash of system files and commands must match vendor values.</title>
+      <description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections, system command and files can be altered by unauthorized users without detection.
+
+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the key used to generate the hash.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000663</ident>
+      <fixtext fixref="F-78207r1_fix">Run the following command to determine which package owns the file:
+
+# rpm -qf &lt;filename&gt;
+
+The package can be reinstalled from a yum repository using the command:
+
+# sudo yum reinstall &lt;packagename&gt;
+
+Alternatively, the package can be reinstalled from trusted media using the command:
+
+# sudo rpm -Uvh &lt;packagename&gt;</fixtext>
+      <fix id="F-78207r1_fix"/>
+      <check system="C-72087r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the cryptographic hash of system files and commands match the vendor values.
+
+Check the cryptographic hash of system files and commands with the following command:
+
+Note: System configuration files (indicated by a "c" in the second column) are expected to change over time. Unusual modifications should be investigated through the system audit log.
+
+# rpm -Va | grep '^..5'
+
+If there is any output from the command for system binaries, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71859">
+    <title>SRG-OS-000023-GPOS-00006</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86483r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010030</version>
+      <title>The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon.</title>
+      <description>&lt;VulnDiscussion&gt;Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
+
+System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.
+
+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 &amp; consent to terms in IS user agreem't."
+
+Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000048</ident>
+      <fixtext fixref="F-78211r3_fix">Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+
+Create a database to contain the system-wide graphical user logon settings (if it does not already exist) with the following command:
+
+# touch /etc/dconf/db/local.d/01-banner-message
+
+Add the following line to the [org/gnome/login-screen] section of the "/etc/dconf/db/local.d/01-banner-message":
+
+[org/gnome/login-screen]
+banner-message-enable=true</fixtext>
+      <fix id="F-78211r3_fix"/>
+      <check system="C-72091r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a graphical user logon.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
+
+Check to see if the operating system displays a banner at the logon screen with the following command:
+
+# grep banner-message-enable /etc/dconf/db/local.d/*
+banner-message-enable=true
+
+If "banner-message-enable" is set to "false" or is missing, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71861">
+    <title>SRG-OS-000023-GPOS-00006</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86485r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010040</version>
+      <title>The operating system must display the approved Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon.</title>
+      <description>&lt;VulnDiscussion&gt;Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
+
+System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.
+
+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 &amp; consent to terms in IS user agreem't."
+
+Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000048</ident>
+      <fixtext fixref="F-78213r4_fix">Configure the operating system to display the approved Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+
+Create a database to contain the system-wide graphical user logon settings (if it does not already exist) with the following command:
+
+# touch /etc/dconf/db/local.d/01-banner-message
+
+Add the following line to the [org/gnome/login-screen] section of the "/etc/dconf/db/local.d/01-banner-message":
+
+[org/gnome/login-screen]
+banner-message-text=’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.’</fixtext>
+      <fix id="F-78213r4_fix"/>
+      <check system="C-72093r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system displays the approved Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a graphical user logon.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
+
+Check that the operating system displays the exact approved Standard Mandatory DoD Notice and Consent Banner text with the command:
+
+# grep banner-message-text /etc/dconf/db/local.d/*
+banner-message-text=
+‘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 does not match the approved Standard Mandatory DoD Notice and Consent Banner, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71863">
+    <title>SRG-OS-000023-GPOS-00006</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86487r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010050</version>
+      <title>The operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a command line user logon.</title>
+      <description>&lt;VulnDiscussion&gt;Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
+
+System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.
+
+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 &amp; consent to terms in IS user agreem't."
+
+Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000048</ident>
+      <fixtext fixref="F-78217r1_fix">Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via the command line by editing the "/etc/issue" file.
+
+Replace the default text with the Standard Mandatory DoD Notice and Consent Banner. The DoD required text is:
+
+"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."</fixtext>
+      <fix id="F-78217r1_fix"/>
+      <check system="C-72097r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the operating system via a command line user logon.
+
+Check to see if the operating system displays a banner at the command line logon screen with the following command:
+
+# more /etc/issue
+
+The command should return the following text:
+"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 operating system does not display a graphical logon banner or the banner does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding.
+
+If the text in the "/etc/issue" file does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71891">
+    <title>SRG-OS-000028-GPOS-00009</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86515r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010060</version>
+      <title>The operating system must enable a user session lock until that user re-establishes 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, the session lock must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system.
+
+Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000056</ident>
+      <fixtext fixref="F-78243r4_fix">Configure the operating system to enable a user's session lock until that user re-establishes access using established identification and authentication procedures.
+
+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command:
+
+# touch /etc/dconf/db/local.d/00-screensaver
+
+Edit “org/gnome/desktop/session” and add or update the following lines:
+
+# Set the lock time out to 900 seconds before the session is considered idle
+idle-delay=uint32 900
+
+Edit "org/gnome/desktop/screensaver" and add or update the following lines:
+
+# Set this to true to lock the screen when the screensaver activates
+lock-enabled=true
+# Set the lock timeout to 180 seconds after the screensaver has been activated
+lock-delay=uint32 180
+
+You must include the "uint32" along with the integer key values as shown.
+
+Override the user's setting and prevent the user from changing it by editing “/etc/dconf/db/local.d/locks/screensaver” and adding or updating the following lines:
+
+# Lock desktop screensaver settings
+/org/gnome/desktop/session/idle-delay
+/org/gnome/desktop/screensaver/lock-enabled
+/org/gnome/desktop/screensaver/lock-delay
+
+Update the system databases:
+
+# dconf update
+
+Users must log out and back in again before the system-wide settings take effect.</fixtext>
+      <fix id="F-78243r4_fix"/>
+      <check system="C-72123r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system enables a user's session lock until that user re-establishes access using established identification and authentication procedures. The screen program must be installed to lock sessions on the console.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+
+Check to see if the screen lock is enabled with the following command:
+
+# grep -i lock-enabled /etc/dconf/db/local.d/00-screensaver
+lock-enabled=true
+
+If the "lock-enabled" setting is missing or is not set to "true", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71893">
+    <title>SRG-OS-000029-GPOS-00010</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86517r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010070</version>
+      <title>The operating system must initiate a screensaver after a 15-minute period of inactivity for graphical user interfaces.</title>
+      <description>&lt;VulnDiscussion&gt;A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
+
+The session lock is implemented at the point where session activity can be determined and/or controlled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000057</ident>
+      <fixtext fixref="F-78245r3_fix">Configure the operating system to initiate a screensaver after a 15-minute period of inactivity for graphical user interfaces.
+
+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command:
+
+# touch /etc/dconf/db/local.d/00-screensaver
+
+Edit “org/gnome/desktop/session” and add or update the following lines:
+
+# Set the lock time out to 900 seconds before the session is considered idle
+idle-delay=uint32 900
+
+Edit "org/gnome/desktop/screensaver" and add or update the following lines:
+
+# Set this to true to lock the screen when the screensaver activates
+lock-enabled=true
+# Set the lock timeout to 180 seconds after the screensaver has been activated
+lock-delay=uint32 180
+
+You must include the "uint32" along with the integer key values as shown.
+
+Override the user's setting and prevent the user from changing it by editing “/etc/dconf/db/local.d/locks/screensaver” and adding or updating the following lines:
+
+# Lock desktop screensaver settings
+/org/gnome/desktop/session/idle-delay
+/org/gnome/desktop/screensaver/lock-enabled
+/org/gnome/desktop/screensaver/lock-delay
+
+Update the system databases:
+
+# dconf update
+
+Users must log out and back in again before the system-wide settings take effect.</fixtext>
+      <fix id="F-78245r3_fix"/>
+      <check system="C-72125r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system initiates a screensaver after a 15-minute period of inactivity for graphical user interfaces. The screen program must be installed to lock sessions on the console.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+
+Check to see if GNOME is configured to display a screensaver after a 15 minute delay with the following command:
+
+# grep -i idle-delay /etc/dconf/db/local.d/*
+idle-delay=uint32 900
+
+If the "idle-delay" setting is missing or is not set to "900" or less, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71895">
+    <title>SRG-OS-000029-GPOS-00010</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86519r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010080</version>
+      <title>The operating system must set the idle delay setting for all connection types.</title>
+      <description>&lt;VulnDiscussion&gt;A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
+
+The session lock is implemented at the point where session activity can be determined and/or controlled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000057</ident>
+      <fixtext fixref="F-78247r2_fix">Configure the operating system to prevent a user from overriding a session lock after a 15-minute period of inactivity for graphical user interfaces.
+
+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: 
+
+Note: The example below is using the database "local" for the system, so if the system is using another database in /etc/dconf/profile/user, the file should be created under the appropriate subdirectory.
+
+# touch /etc/dconf/db/local.d/locks/session
+
+Add the setting to lock the screensaver idle delay:
+
+/org/gnome/desktop/screensaver/idle-delay</fixtext>
+      <fix id="F-78247r2_fix"/>
+      <check system="C-72127r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system prevents a user from overriding session lock after a 15-minute period of inactivity for graphical user interfaces. The screen program must be installed to lock sessions on the console.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+
+Determine which profile the system database is using with the following command:
+#grep system-db /etc/dconf/profile/user
+
+system-db:local
+
+Check for the lock delay setting with the following command:
+
+Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used.
+
+# grep -i idle-delay /etc/dconf/db/local.d/locks/*
+
+/org/gnome/desktop/screensaver/idle-delay
+
+If the command does not return a result, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71897">
+    <title>SRG-OS-000029-GPOS-00010</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86521r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010090</version>
+      <title>The operating system must have the screen package installed.</title>
+      <description>&lt;VulnDiscussion&gt;A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
+
+The screen package allows for a session lock to be implemented and configured.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000057</ident>
+      <fixtext fixref="F-78249r1_fix">Install the screen package to allow the initiation a session lock after a 15-minute period of inactivity for graphical users interfaces.
+
+Install the screen program (if it is not on the system) with the following command:
+
+# yum install screen
+
+The console can now be locked with the following key combination: 
+
+ctrl+A x</fixtext>
+      <fix id="F-78249r1_fix"/>
+      <check system="C-72129r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system has the screen package installed.
+
+Check to see if the screen package is installed with the following command:
+
+# yum list installed | grep screen
+screen-4.3.1-3-x86_64.rpm
+
+If is not installed, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71899">
+    <title>SRG-OS-000029-GPOS-00010</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86523r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010100</version>
+      <title>The operating system must initiate a session lock for the screensaver after a period of inactivity for graphical user interfaces.</title>
+      <description>&lt;VulnDiscussion&gt;A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
+
+The session lock is implemented at the point where session activity can be determined and/or controlled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000057</ident>
+      <fixtext fixref="F-78251r1_fix">Configure the operating system to initiate a session lock after a 15-minute period of inactivity for graphical user interfaces.
+
+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: 
+
+# touch /etc/dconf/db/local.d/00-screensaver
+
+Add the setting to enable screensaver locking after 15 minutes of inactivity:
+
+[org/gnome/desktop/screensaver]
+
+idle-activation-enabled=true</fixtext>
+      <fix id="F-78251r1_fix"/>
+      <check system="C-72131r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system initiates a session lock after a 15-minute period of inactivity for graphical user interfaces. The screen program must be installed to lock sessions on the console.
+
+If it is installed, GNOME must be configured to enforce a session lock after a 15-minute delay. Check for the session lock settings with the following commands:
+
+# grep -i  idle_activation_enabled /etc/dconf/db/local.d/*
+[org/gnome/desktop/screensaver]   idle-activation-enabled=true
+
+If "idle-activation-enabled" is not set to "true", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71901">
+    <title>SRG-OS-000029-GPOS-00010</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86525r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010110</version>
+      <title>The operating system must initiate a session lock for graphical user interfaces when the screensaver is activated.</title>
+      <description>&lt;VulnDiscussion&gt;A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
+
+The session lock is implemented at the point where session activity can be determined and/or controlled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000057</ident>
+      <fixtext fixref="F-78253r1_fix">Configure the operating system to initiate a session lock for graphical user interfaces when a screensaver is activated.
+
+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: 
+
+# touch /etc/dconf/db/local.d/00-screensaver
+
+Add the setting to enable session locking when a screensaver is activated:
+
+[org/gnome/desktop/screensaver]
+lock-delay=uint32 5
+
+After the setting has been set, run dconf update.</fixtext>
+      <fix id="F-78253r1_fix"/>
+      <check system="C-72133r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system initiates a session lock a for graphical user interfaces when the screensaver is activated. The screen program must be installed to lock sessions on the console.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+
+If GNOME is installed, check to see a session lock occurs when the screensaver is activated with the following command:
+
+# grep -i lock-delay /etc/dconf/db/local.d/*
+lock-delay=uint32 5
+
+If the "lock-delay" setting is missing, or is not set, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71903">
+    <title>SRG-OS-000069-GPOS-00037</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86527r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010120</version>
+      <title>When passwords are changed or new passwords are established, the new password must contain at least one upper-case character.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000192</ident>
+      <fixtext fixref="F-78255r1_fix">Configure the operating system to enforce password complexity by requiring that at least one upper-case character be used by setting the "ucredit" option.
+
+Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value):
+
+ucredit = -1</fixtext>
+      <fix id="F-78255r1_fix"/>
+      <check system="C-72135r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Note: The value to require a number of upper-case characters to be set is expressed as a negative number in "/etc/security/pwquality.conf".
+
+Check the value for "ucredit" in "/etc/security/pwquality.conf" with the following command:
+
+# grep ucredit /etc/security/pwquality.conf 
+ucredit = -1
+
+If the value of "ucredit" is not set to a negative value, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71905">
+    <title>SRG-OS-000070-GPOS-00038</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86529r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010130</version>
+      <title>When passwords are changed or new passwords are established, the new password must contain at least one lower-case character.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000193</ident>
+      <fixtext fixref="F-78257r4_fix">Configure the operating system to lock an account for the maximum period when three unsuccessful logon attempts in 15 minutes are made.
+
+Modify the first three lines of the "auth" section of the "/etc/pam.d/system-auth-ac" and "/etc/pam.d/password-auth-ac" files to match the following lines:
+
+Note: RHEL 7.3 and later allows for a value of “never” for "unlock_time". This is an acceptable value but should be used with caution if availability is a concern.
+
+auth        required       pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=604800
+auth        sufficient     pam_unix.so try_first_pass
+auth        [default=die]  pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=604800
+
+and run the "authconfig" command.</fixtext>
+      <fix id="F-78257r4_fix"/>
+      <check system="C-72137r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Note: The value to require a number of lower-case characters to be set is expressed as a negative number in "/etc/security/pwquality.conf".
+
+Check the value for "lcredit" in "/etc/security/pwquality.conf" with the following command:
+
+# grep lcredit /etc/security/pwquality.conf 
+lcredit = -1 
+
+If the value of "lcredit" is not set to a negative value, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71907">
+    <title>SRG-OS-000071-GPOS-00039</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86531r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010140</version>
+      <title>When passwords are changed or new passwords are assigned, the new password must contain at least one numeric character.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000194</ident>
+      <fixtext fixref="F-78259r1_fix">Configure the operating system to enforce password complexity by requiring that at least one numeric character be used by setting the "dcredit" option.
+
+Add the following line to /etc/security/pwquality.conf (or modify the line to have the required value):
+
+dcredit = -1</fixtext>
+      <fix id="F-78259r1_fix"/>
+      <check system="C-72139r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Note: The value to require a number of numeric characters to be set is expressed as a negative number in "/etc/security/pwquality.conf".
+
+Check the value for "dcredit" in "/etc/security/pwquality.conf" with the following command:
+
+# grep dcredit /etc/security/pwquality.conf 
+dcredit = -1 
+
+If the value of "dcredit" is not set to a negative value, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71909">
+    <title>SRG-OS-000266-GPOS-00101</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86533r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010150</version>
+      <title>When passwords are changed or new passwords are assigned, the new password must contain at least one special character.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001619</ident>
+      <fixtext fixref="F-78261r1_fix">Configure the operating system to enforce password complexity by requiring that at least one special character be used by setting the "dcredit" option.
+
+Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value):
+
+ocredit = -1</fixtext>
+      <fix id="F-78261r1_fix"/>
+      <check system="C-72141r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system enforces password complexity by requiring that at least one special character be used.
+
+Note: The value to require a number of special characters to be set is expressed as a negative number in "/etc/security/pwquality.conf".
+
+Check the value for "ocredit" in "/etc/security/pwquality.conf" with the following command:
+
+# grep ocredit /etc/security/pwquality.conf 
+ocredit=-1
+
+If the value of "ocredit" is not set to a negative value, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71911">
+    <title>SRG-OS-000072-GPOS-00040</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86535r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010160</version>
+      <title>When passwords are changed a minimum of eight of the total number of characters must be changed.</title>
+      <description>&lt;VulnDiscussion&gt;Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+
+Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000195</ident>
+      <fixtext fixref="F-78263r1_fix">Configure the operating system to require the change of at least eight of the total number of characters when passwords are changed by setting the "difok" option.
+
+Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value):
+
+difok = 8</fixtext>
+      <fix id="F-78263r1_fix"/>
+      <check system="C-72143r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>The "difok" option sets the number of characters in a password that must not be present in the old password.
+
+Check for the value of the "difok" option in "/etc/security/pwquality.conf" with the following command:
+
+# grep difok /etc/security/pwquality.conf 
+difok = 8
+
+If the value of "difok" is set to less than "8", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71913">
+    <title>SRG-OS-000072-GPOS-00040</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86537r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010170</version>
+      <title>When passwords are changed a minimum of four character classes must be changed.</title>
+      <description>&lt;VulnDiscussion&gt;Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
+
+Password complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000195</ident>
+      <fixtext fixref="F-78265r1_fix">Configure the operating system to require the change of at least four character classes when passwords are changed by setting the "minclass" option.
+
+Add the following line to "/etc/security/pwquality.conf conf" (or modify the line to have the required value):
+
+minclass = 4</fixtext>
+      <fix id="F-78265r1_fix"/>
+      <check system="C-72145r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>The "minclass" option sets the minimum number of required classes of characters for the new password (digits, upper-case, lower-case, others).
+
+Check for the value of the "minclass" option in "/etc/security/pwquality.conf" with the following command:
+
+# grep minclass /etc/security/pwquality.conf 
+minclass = 4
+
+If the value of "minclass" is set to less than "4", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71915">
+    <title>SRG-OS-000072-GPOS-00040</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86539r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010180</version>
+      <title>When passwords are changed the number of repeating consecutive characters must not be more than four characters.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000195</ident>
+      <fixtext fixref="F-78267r1_fix">Configure the operating system to require the change of the number of repeating consecutive characters when passwords are changed by setting the "maxrepeat" option.
+
+Add the following line to "/etc/security/pwquality.conf conf" (or modify the line to have the required value):
+
+maxrepeat = 2</fixtext>
+      <fix id="F-78267r1_fix"/>
+      <check system="C-72147r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>The "maxrepeat" option sets the maximum number of allowed same consecutive characters in a new password.
+
+Check for the value of the "maxrepeat" option in "/etc/security/pwquality.conf" with the following command:
+
+# grep maxrepeat /etc/security/pwquality.conf 
+maxrepeat = 2
+
+If the value of "maxrepeat" is set to more than "2", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71917">
+    <title>SRG-OS-000072-GPOS-00040</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86541r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010190</version>
+      <title>When passwords are changed the number of repeating characters of the same character class must not be more than four characters.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000195</ident>
+      <fixtext fixref="F-78269r1_fix">Configure the operating system to require the change of the number of repeating characters of the same character class when passwords are changed by setting the "maxclassrepeat" option.
+
+Add the following line to "/etc/security/pwquality.conf" conf (or modify the line to have the required value):
+
+maxclassrepeat = 4</fixtext>
+      <fix id="F-78269r1_fix"/>
+      <check system="C-72149r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>The "maxclassrepeat" option sets the maximum number of allowed same consecutive characters in the same class in the new password.
+
+Check for the value of the "maxclassrepeat" option in "/etc/security/pwquality.conf" with the following command:
+
+# grep maxclassrepeat /etc/security/pwquality.conf 
+maxclassrepeat = 4
+
+If the value of "maxclassrepeat" is set to more than "4", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71919">
+    <title>SRG-OS-000073-GPOS-00041</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86543r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010200</version>
+      <title>The PAM system service must be configured to store only encrypted representations of passwords.</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. Passwords encrypted with a weak algorithm are no more protected than if they are kept in plain text.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000196</ident>
+      <fixtext fixref="F-78271r1_fix">Configure the operating system to store only SHA512 encrypted representations of passwords.
+
+Add the following line in "/etc/pam.d/system-auth-ac":
+
+password sufficient pam_unix.so sha512
+
+and run the "authconfig" command.</fixtext>
+      <fix id="F-78271r1_fix"/>
+      <check system="C-72151r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the PAM system service is configured to store only encrypted representations of passwords. The strength of encryption that must be used to hash passwords for all accounts is SHA512.
+
+Check that the system is configured to create SHA512 hashed passwords with the following command:
+
+# grep password /etc/pam.d/system-auth-ac
+password sufficient pam_unix.so sha512
+
+If the "/etc/pam.d/system-auth-ac" configuration files allow for password hashes other than SHA512 to be used, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71921">
+    <title>SRG-OS-000073-GPOS-00041</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86545r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010210</version>
+      <title>The shadow file must be configured to store only encrypted representations of passwords.</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. Passwords encrypted with a weak algorithm are no more protected than if they are kept in plain text.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000196</ident>
+      <fixtext fixref="F-78273r1_fix">Configure the operating system to store only SHA512 encrypted representations of passwords.
+
+Add or update the following line in "/etc/login.defs":
+
+ENCRYPT_METHOD SHA512</fixtext>
+      <fix id="F-78273r1_fix"/>
+      <check system="C-72153r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system's shadow file is configured to store only encrypted representations of passwords. The strength of encryption that must be used to hash passwords for all accounts is SHA512.
+
+Check that the system is configured to create SHA512 hashed passwords with the following command:
+
+# grep -i encrypt /etc/login.defs
+ENCRYPT_METHOD SHA512
+
+If the "/etc/login.defs" configuration file does not exist or allows for password hashes other than SHA512 to be used, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71923">
+    <title>SRG-OS-000073-GPOS-00041</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86547r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010220</version>
+      <title>User and group account administration utilities must be configured to store only encrypted representations of passwords.</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. Passwords encrypted with a weak algorithm are no more protected than if they are kept in plain text.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000196</ident>
+      <fixtext fixref="F-78275r1_fix">Configure the operating system to store only SHA512 encrypted representations of passwords.
+
+Add or update the following line in "/etc/libuser.conf" in the [defaults] section: 
+
+crypt_style = sha512</fixtext>
+      <fix id="F-78275r1_fix"/>
+      <check system="C-72155r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the user and group account administration utilities are configured to store only encrypted representations of passwords. The strength of encryption that must be used to hash passwords for all accounts is "SHA512".
+
+Check that the system is configured to create "SHA512" hashed passwords with the following command:
+
+# cat /etc/libuser.conf | grep -i sha512
+
+crypt_style = sha512
+
+If the "crypt_style" variable is not set to "sha512", is not in the defaults section, or does not exist, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71925">
+    <title>SRG-OS-000075-GPOS-00043</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86549r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010230</version>
+      <title>Passwords for new users must be restricted to a 24 hours/1 day minimum lifetime.</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, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000198</ident>
+      <fixtext fixref="F-78277r1_fix">Configure the operating system to enforce 24 hours/1 day as the minimum password lifetime.
+
+Add the following line in "/etc/login.defs" (or modify the line to have the required value):
+
+PASS_MIN_DAYS     1</fixtext>
+      <fix id="F-78277r1_fix"/>
+      <check system="C-72157r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system enforces 24 hours/1 day as the minimum password lifetime for new user accounts.
+
+Check for the value of "PASS_MIN_DAYS" in "/etc/login.defs" with the following command: 
+
+# grep -i pass_min_days /etc/login.defs
+PASS_MIN_DAYS     1
+
+If the "PASS_MIN_DAYS" parameter value is not "1" or greater, or is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71927">
+    <title>SRG-OS-000075-GPOS-00043</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86551r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010240</version>
+      <title>Passwords must be restricted to a 24 hours/1 day minimum lifetime.</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, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000198</ident>
+      <fixtext fixref="F-78279r1_fix">Configure non-compliant accounts to enforce a 24 hours/1 day minimum password lifetime:
+
+# chage -m 1 [user]</fixtext>
+      <fix id="F-78279r1_fix"/>
+      <check system="C-72159r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Check whether the minimum time period between password changes for each user account is one day or greater.
+
+# awk -F: '$4 &lt; 1 {print $1}' /etc/shadow
+
+If any results are returned that are not associated with a system account, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71929">
+    <title>SRG-OS-000076-GPOS-00044</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86553r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010250</version>
+      <title>Passwords for new users must be restricted to a 60-day maximum lifetime.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000199</ident>
+      <fixtext fixref="F-78281r1_fix">Configure the operating system to enforce a 60-day maximum password lifetime restriction.
+
+Add the following line in "/etc/login.defs" (or modify the line to have the required value):
+
+PASS_MAX_DAYS     60</fixtext>
+      <fix id="F-78281r1_fix"/>
+      <check system="C-72161r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system enforces a 60-day maximum password lifetime restriction for new user accounts.
+
+Check for the value of "PASS_MAX_DAYS" in "/etc/login.defs" with the following command:
+
+# grep -i pass_max_days /etc/login.defs
+PASS_MAX_DAYS     60
+
+If the "PASS_MAX_DAYS" parameter value is not 60 or less, or is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71931">
+    <title>SRG-OS-000076-GPOS-00044</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86555r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010260</version>
+      <title>Existing passwords must be restricted to a 60-day maximum lifetime.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000199</ident>
+      <fixtext fixref="F-78283r1_fix">Configure non-compliant accounts to enforce a 60-day maximum password lifetime restriction.
+
+# chage -M 60 [user]</fixtext>
+      <fix id="F-78283r1_fix"/>
+      <check system="C-72163r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Check whether the maximum time period for existing passwords is restricted to 60 days.
+
+# awk -F: '$5 &gt; 60 {print $1}' /etc/shadow
+
+If any results are returned that are not associated with a system account, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71933">
+    <title>SRG-OS-000077-GPOS-00045</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86557r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010270</version>
+      <title>Passwords must be prohibited from reuse for a minimum of five generations.</title>
+      <description>&lt;VulnDiscussion&gt;Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000200</ident>
+      <fixtext fixref="F-78285r1_fix">Configure the operating system to prohibit password reuse for a minimum of five generations.
+
+Add the following line in "/etc/pam.d/system-auth-ac" (or modify the line to have the required value):
+
+password sufficient pam_unix.so use_authtok sha512 shadow remember=5
+
+and run the "authconfig" command.</fixtext>
+      <fix id="F-78285r1_fix"/>
+      <check system="C-72165r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system prohibits password reuse for a minimum of five generations.
+
+Check for the value of the "remember" argument in "/etc/pam.d/system-auth-ac" with the following command:
+
+# grep -i remember /etc/pam.d/system-auth-ac
+password sufficient pam_unix.so use_authtok sha512 shadow remember=5
+
+If the line containing the "pam_unix.so" line does not have the "remember" module argument set, or the value of the "remember" module argument is set to less than "5", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71935">
+    <title>SRG-OS-000078-GPOS-00046</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86559r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010280</version>
+      <title>Passwords must be a minimum of 15 characters in 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000205</ident>
+      <fixtext fixref="F-78287r1_fix">Configure operating system to enforce a minimum 15-character password length.
+
+Add the following line to "/etc/security/pwquality.conf" (or modify the line to have the required value):
+
+minlen = 15</fixtext>
+      <fix id="F-78287r1_fix"/>
+      <check system="C-72167r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system enforces a minimum 15-character password length. The "minlen" option sets the minimum number of characters in a new password.
+
+Check for the value of the "minlen" option in "/etc/security/pwquality.conf" with the following command:
+
+# grep minlen /etc/security/pwquality.conf
+minlen = 15
+
+If the command does not return a "minlen" value of 15 or greater, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71937">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86561r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-010290</version>
+      <title>The system must not have accounts configured with blank or null passwords.</title>
+      <description>&lt;VulnDiscussion&gt;If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78289r1_fix">If an account is configured for password authentication but does not have an assigned password, it may be possible to log on to the account without authenticating.
+
+Remove any instances of the "nullok" option in "/etc/pam.d/system-auth-ac" to prevent logons with empty passwords and run the "authconfig" command.</fixtext>
+      <fix id="F-78289r1_fix"/>
+      <check system="C-72169r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>To verify that null passwords cannot be used, run the following command: 
+
+# grep nullok /etc/pam.d/system-auth-ac
+
+If this produces any output, it may be possible to log on with accounts with empty passwords.
+
+If null passwords can be used, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71939">
+    <title>SRG-OS-000106-GPOS-00053</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86563r2_rule" severity="high" weight="10.0">
+      <version>RHEL-07-010300</version>
+      <title>The SSH daemon must not allow authentication using an empty password.</title>
+      <description>&lt;VulnDiscussion&gt;Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000766</ident>
+      <fixtext fixref="F-78291r2_fix">To explicitly disallow remote logon from accounts with empty passwords, add or correct the following line in "/etc/ssh/sshd_config":
+
+PermitEmptyPasswords no
+
+The SSH service must be restarted for changes to take effect.  Any accounts with empty passwords should be disabled immediately, and PAM configuration should prevent users from being able to assign themselves empty passwords.</fixtext>
+      <fix id="F-78291r2_fix"/>
+      <check system="C-72171r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>To determine how the SSH daemon's "PermitEmptyPasswords" option is set, run the following command:
+
+# grep -i PermitEmptyPasswords /etc/ssh/sshd_config
+PermitEmptyPasswords no
+
+If no line, a commented line, or a line indicating the value "no" is returned, the required value is set.
+
+If the required value is not set, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71941">
+    <title>SRG-OS-000118-GPOS-00060</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86565r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010310</version>
+      <title>The operating system must disable account identifiers (individuals, groups, roles, and devices) if the password expires.</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 zero 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000795</ident>
+      <fixtext fixref="F-78293r1_fix">Configure the operating system to disable account identifiers (individuals, groups, roles, and devices) after the password expires.
+
+Add the following line to "/etc/default/useradd" (or modify the line to have the required value):
+
+INACTIVE=0</fixtext>
+      <fix id="F-78293r1_fix"/>
+      <check system="C-72173r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system disables account identifiers (individuals, groups, roles, and devices) after the password expires with the following command:
+
+# grep -i inactive /etc/default/useradd
+INACTIVE=0
+
+If the value is not set to "0", is commented out, or is not defined, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71943">
+    <title>SRG-OS-000329-GPOS-00128</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86567r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010320</version>
+      <title>Accounts subject to three unsuccessful logon attempts within 15 minutes must be locked for the maximum configurable period.</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-000329-GPOS-00128, SRG-OS-000021-GPOS-00005&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002238</ident>
+      <fixtext fixref="F-78295r2_fix">Configure the operating system to lock an account for the maximum period when three unsuccessful logon attempts in 15 minutes are made.
+
+Modify the first three lines of the auth section of the "/etc/pam.d/system-auth-ac" and "/etc/pam.d/password-auth-ac" files to match the following lines:
+
+auth        required       pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=604800
+auth        sufficient     pam_unix.so try_first_pass
+auth        [default=die]  pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=604800
+
+and run the "authconfig" command.</fixtext>
+      <fix id="F-78295r2_fix"/>
+      <check system="C-72175r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system automatically locks an account for the maximum period for which the system can be configured.
+
+Check that the system locks an account for the maximum period after three unsuccessful logon attempts within a period of 15 minutes with the following command:
+
+# grep pam_faillock.so /etc/pam.d/password-auth-ac
+auth        required       pam_faillock.so preauth silent audit deny=3 even_deny_root unlock_time=604800
+auth        [default=die]  pam_faillock.so authfail audit deny=3 even_deny_root unlock_time=604800
+
+If the "unlock_time" setting is greater than "604800" on both lines with the "pam_faillock.so" module name or is missing from a line, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71945">
+    <title>SRG-OS-000329-GPOS-00128</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86569r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010330</version>
+      <title>If three unsuccessful root logon attempts within 15 minutes occur the associated account must be locked.</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-000329-GPOS-00128, SRG-OS-000021-GPOS-00005&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002238</ident>
+      <fixtext fixref="F-78297r1_fix">Configure the operating system to automatically lock the root account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are made.
+
+Modify the first three lines of the auth section of the "/etc/pam.d/system-auth-ac" and "/etc/pam.d/password-auth-ac" files to match the following lines:
+
+auth        required       pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900 unlock_time=604800
+auth        sufficient     pam_unix.so try_first_pass
+auth        [default=die]  pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900 unlock_time=604800
+
+and run the "authconfig" command.</fixtext>
+      <fix id="F-78297r1_fix"/>
+      <check system="C-72177r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system automatically locks the root account until it is released by an administrator when three unsuccessful logon attempts in 15 minutes are made.
+
+# grep pam_faillock.so /etc/pam.d/password-auth-ac
+auth        required       pam_faillock.so preauth silent audit deny=3 even_deny_root fail_interval=900
+auth        [default=die]  pam_faillock.so authfail audit deny=3 even_deny_root fail_interval=900
+
+If the "even_deny_root" setting is not defined on both lines with the "pam_faillock.so" module name, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71947">
+    <title>SRG-OS-000373-GPOS-00156</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86571r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010340</version>
+      <title>Users must provide a password for privilege escalation.</title>
+      <description>&lt;VulnDiscussion&gt;Without re-authentication, users may access resources or perform tasks for which they do not have authorization. 
+
+When operating systems provide the capability to escalate a functional capability, it is critical the user re-authenticate.
+
+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002038</ident>
+      <fixtext fixref="F-78299r1_fix">Configure the operating system to require users to supply a password for privilege escalation.
+
+Check the configuration of the "/etc/sudoers" and "/etc/sudoers.d/*" files with the following command:
+
+# grep -i nopasswd /etc/sudoers /etc/sudoers.d/*
+
+Remove any occurrences of "NOPASSWD" tags in the file.</fixtext>
+      <fix id="F-78299r1_fix"/>
+      <check system="C-72179r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system requires users to supply a password for privilege escalation.
+
+Check the configuration of the "/etc/sudoers" and "/etc/sudoers.d/*" files with the following command:
+
+# grep -i nopasswd /etc/sudoers /etc/sudoers.d/*
+
+If any uncommented line is found with a "NOPASSWD" tag, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71949">
+    <title>SRG-OS-000373-GPOS-00156</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86573r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010350</version>
+      <title>Users must re-authenticate for privilege escalation.</title>
+      <description>&lt;VulnDiscussion&gt;Without re-authentication, users may access resources or perform tasks for which they do not have authorization. 
+
+When operating systems provide the capability to escalate a functional capability, it is critical the user reauthenticate.
+
+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002038</ident>
+      <fixtext fixref="F-78301r2_fix">Configure the operating system to require users to reauthenticate for privilege escalation.
+
+Check the configuration of the "/etc/sudoers" and "/etc/sudoers.d/*" files with the following command:
+
+Remove any occurrences of "!authenticate" tags in the file.</fixtext>
+      <fix id="F-78301r2_fix"/>
+      <check system="C-72181r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system requires users to reauthenticate for privilege escalation.
+
+Check the configuration of the "/etc/sudoers" and "/etc/sudoers.d/*" files with the following command:
+
+# grep -i authenticate /etc/sudoers /etc/sudoers.d/*
+
+If any line is found with a "!authenticate" tag, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71951">
+    <title>SRG-OS-000480-GPOS-00226</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86575r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010430</version>
+      <title>The delay between logon prompts following a failed console logon attempt must be at least four seconds.</title>
+      <description>&lt;VulnDiscussion&gt;Configuring the operating system to implement organization-wide security implementation guides and security checklists verifies compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.
+
+Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example, registry settings; account, file, and directory permission settings; and settings for functions, ports, protocols, services, and remote connections.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78303r1_fix">Configure the operating system to enforce a delay of at least four seconds between logon prompts following a failed console logon attempt.
+
+Modify the "/etc/login.defs" file to set the "FAIL_DELAY" parameter to "4" or greater:
+
+FAIL_DELAY 4</fixtext>
+      <fix id="F-78303r1_fix"/>
+      <check system="C-72183r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system enforces a delay of at least four seconds between console logon prompts following a failed logon attempt.
+
+Check the value of the "fail_delay" parameter in the "/etc/login.defs" file with the following command:
+
+# grep -i fail_delay /etc/login.defs
+FAIL_DELAY 4
+
+If the value of "FAIL_DELAY" is not set to "4" or greater, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71953">
+    <title>SRG-OS-000480-GPOS-00229</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86577r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-010440</version>
+      <title>The operating system must not allow an unattended or automatic logon to the system via a graphical user interface.</title>
+      <description>&lt;VulnDiscussion&gt;Failure to restrict system access to authenticated users negatively impacts operating system 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78305r1_fix">Configure the operating system to not allow an unattended or automatic logon to the system via a graphical user interface.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+
+Add or edit the line for the "AutomaticLoginEnable" parameter in the [daemon] section of the "/etc/gdm/custom.conf" file to "false":
+
+[daemon]
+AutomaticLoginEnable=false</fixtext>
+      <fix id="F-78305r1_fix"/>
+      <check system="C-72185r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system does not allow an unattended or automatic logon to the system via a graphical user interface.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
+
+Check for the value of the "AutomaticLoginEnable" in the "/etc/gdm/custom.conf" file with the following command:
+
+# grep -i automaticloginenable /etc/gdm/custom.conf
+AutomaticLoginEnable=false
+
+If the value of "AutomaticLoginEnable" is not set to "false", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71955">
+    <title>SRG-OS-000480-GPOS-00229</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86579r2_rule" severity="high" weight="10.0">
+      <version>RHEL-07-010450</version>
+      <title>The operating system must not allow an unrestricted logon to the system.</title>
+      <description>&lt;VulnDiscussion&gt;Failure to restrict system access to authenticated users negatively impacts operating system 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78307r2_fix">Configure the operating system to not allow an unrestricted account to log on to the system via a graphical user interface.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable.
+
+Add or edit the line for the "TimedLoginEnable" parameter in the [daemon] section of the "/etc/gdm/custom.conf" file to "false":
+
+[daemon]
+TimedLoginEnable=false</fixtext>
+      <fix id="F-78307r2_fix"/>
+      <check system="C-72187r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system does not allow an unrestricted logon to the system via a graphical user interface.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
+
+Check for the value of the "TimedLoginEnable" parameter in "/etc/gdm/custom.conf" file with the following command:
+
+# grep -i timedloginenable /etc/gdm/custom.conf
+TimedLoginEnable=false
+
+If the value of "TimedLoginEnable" is not set to "false", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71957">
+    <title>SRG-OS-000480-GPOS-00229</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86581r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010460</version>
+      <title>The operating system must not allow users to override SSH environment variables.</title>
+      <description>&lt;VulnDiscussion&gt;Failure to restrict system access to authenticated users negatively impacts operating system 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78309r2_fix">Configure the operating system to not allow users to override environment variables to the SSH daemon.
+
+Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for "PermitUserEnvironment" keyword and set the value to "no":
+
+PermitUserEnvironment no
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78309r2_fix"/>
+      <check system="C-72189r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system does not allow users to override environment variables to the SSH daemon.
+
+Check for the value of the "PermitUserEnvironment" keyword with the following command:
+
+# grep -i permituserenvironment /etc/ssh/sshd_config
+PermitUserEnvironment no
+
+If the "PermitUserEnvironment" keyword is not set to "no", is missing, or is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71959">
+    <title>SRG-OS-000480-GPOS-00229</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86583r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010470</version>
+      <title>The operating system must not allow a non-certificate trusted host SSH logon to the system.</title>
+      <description>&lt;VulnDiscussion&gt;Failure to restrict system access to authenticated users negatively impacts operating system 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78311r3_fix">Configure the operating system to not allow a non-certificate trusted host SSH logon to the system.
+
+Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for "HostbasedAuthentication" keyword and set the value to "no":
+
+HostbasedAuthentication no
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78311r3_fix"/>
+      <check system="C-72191r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system does not allow a non-certificate trusted host SSH logon to the system.
+
+Check for the value of the "HostbasedAuthentication" keyword with the following command:
+
+# grep -i hostbasedauthentication /etc/ssh/sshd_config
+HostbasedAuthentication no
+
+If the "HostbasedAuthentication" keyword is not set to "no", is missing, or is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71961">
+    <title>SRG-OS-000080-GPOS-00048</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86585r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-010480</version>
+      <title>Systems with a Basic Input/Output System (BIOS) must require authentication upon booting into single-user and maintenance modes.</title>
+      <description>&lt;VulnDiscussion&gt;If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 7 and is designed to require a password to boot into single-user mode or make modifications to the boot menu.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000213</ident>
+      <fixtext fixref="F-78313r1_fix">Configure the system to encrypt the boot password for root.
+
+Generate an encrypted grub2 password for root with the following command:
+
+Note: The hash generated is an example.
+
+# grub-mkpasswd-pbkdf2
+Enter Password:
+Reenter Password:
+PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45
+
+Using this hash, modify the "/etc/grub.d/10_linux" file with the following commands to add the password to the root entry:
+
+# cat &lt;&lt; EOF
+&gt; set superusers="root" password_pbkdf2 smithj grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45
+&gt; EOF
+
+Generate a new "grub.conf" file with the new password with the following commands:
+
+# grub2-mkconfig --output=/tmp/grub2.cfg
+# mv /tmp/grub2.cfg /boot/grub2/grub.cfg</fixtext>
+      <fix id="F-78313r1_fix"/>
+      <check system="C-72193r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Check to see if an encrypted root password is set. On systems that use a BIOS, use the following command:
+
+# grep -i password /boot/grub2/grub.cfg
+password_pbkdf2 superusers-account password-hash
+
+If the root password entry does not begin with "password_pbkdf2", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71963">
+    <title>SRG-OS-000080-GPOS-00048</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86587r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-010490</version>
+      <title>Systems using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes.</title>
+      <description>&lt;VulnDiscussion&gt;If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system. GRUB 2 is the default boot loader for RHEL 7 and is designed to require a password to boot into single-user mode or make modifications to the boot menu.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000213</ident>
+      <fixtext fixref="F-78315r1_fix">Configure the system to encrypt the boot password for root.
+
+Generate an encrypted grub2 password for root with the following command:
+
+Note: The hash generated is an example.
+
+# grub-mkpasswd-pbkdf2
+Enter Password:
+Reenter Password:
+
+PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45
+
+Using this hash, modify the "/etc/grub.d/10_linux" file with the following commands to add the password to the root entry:
+
+# cat &lt;&lt; EOF
+&gt; set superusers="root" password_pbkdf2 smithj grub.pbkdf2.sha512.10000.F3A7CFAA5A51EED123BE8238C23B25B2A6909AFC9812F0D45
+&gt; EOF
+
+Generate a new "grub.conf" file with the new password with the following commands:
+
+# grub2-mkconfig --output=/tmp/grub2.cfg
+# mv /tmp/grub2.cfg /boot/efi/EFI/redhat/grub.cfg</fixtext>
+      <fix id="F-78315r1_fix"/>
+      <check system="C-72195r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Check to see if an encrypted root password is set. On systems that use UEFI, use the following command:
+
+# grep -i password /boot/efi/EFI/redhat/grub.cfg
+password_pbkdf2 superusers-account password-hash
+
+If the root password entry does not begin with "password_pbkdf2", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71965">
+    <title>SRG-OS-000104-GPOS-00051</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86589r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010500</version>
+      <title>The operating system must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users) using multifactor authentication.</title>
+      <description>&lt;VulnDiscussion&gt;To assure 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-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000109-GPOS-00056, SRG-OS-000108-GPOS-00055, SRG-OS-000108-GPOS-00057, SRG-OS-000108-GPOS-00058&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000766</ident>
+      <fixtext fixref="F-78317r1_fix">Configure the operating system to require individuals to be authenticated with a multifactor authenticator.
+
+Enable smartcard logons with the following commands:
+
+# authconfig --enablesmartcard --smartcardaction=1 --update
+# authconfig --enablerequiresmartcard -update
+
+Modify the "/etc/pam_pkcs11/pkcs11_eventmgr.conf" file to uncomment the following line:
+
+#/usr/X11R6/bin/xscreensaver-command -lock
+
+Modify the "/etc/pam_pkcs11/pam_pkcs11.conf" file to use the cackey module if required.</fixtext>
+      <fix id="F-78317r1_fix"/>
+      <check system="C-72197r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system requires multifactor authentication to uniquely identify organizational users using multifactor authentication.
+
+Check to see if smartcard authentication is enforced on the system:
+
+# authconfig --test | grep -i smartcard
+
+The entry for use only smartcard for logon may be enabled, and the smartcard module and smartcard removal actions must not be blank.
+
+If smartcard authentication is disabled or the smartcard and smartcard removal actions are blank, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71967">
+    <title>SRG-OS-000095-GPOS-00049</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86591r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-020000</version>
+      <title>The rsh-server package must not be 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.
+
+Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
+
+The rsh-server service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session and has very weak authentication.
+
+If a privileged user were to log on using this service, the privileged user password could be compromised.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000381</ident>
+      <fixtext fixref="F-78319r1_fix">Configure the operating system to disable non-essential capabilities by removing the rsh-server package from the system with the following command:
+
+# yum remove rsh-server</fixtext>
+      <fix id="F-78319r1_fix"/>
+      <check system="C-72199r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Check to see if the rsh-server package is installed with the following command:
+
+# yum list installed rsh-server
+
+If the rsh-server package is installed, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71969">
+    <title>SRG-OS-000095-GPOS-00049</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86593r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-020010</version>
+      <title>The ypserv package must not be installed.</title>
+      <description>&lt;VulnDiscussion&gt;Removing the "ypserv" package decreases the risk of the accidental (or intentional) activation of NIS or NIS+ services.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000381</ident>
+      <fixtext fixref="F-78321r1_fix">Configure the operating system to disable non-essential capabilities by removing the "ypserv" package from the system with the following command:
+
+# yum remove ypserv</fixtext>
+      <fix id="F-78321r1_fix"/>
+      <check system="C-72201r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>The NIS service provides an unencrypted authentication service that does not provide for the confidentiality and integrity of user passwords or the remote session.
+
+Check to see if the "ypserve" package is installed with the following command:
+
+# yum list installed ypserv
+
+If the "ypserv" package is installed, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71971">
+    <title>SRG-OS-000324-GPOS-00125</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86595r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020020</version>
+      <title>The operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.</title>
+      <description>&lt;VulnDiscussion&gt;Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
+
+Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals who do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002165</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002235</ident>
+      <fixtext fixref="F-78323r1_fix">Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
+
+Use the following command to map a new user to the "sysdam_u" role: 
+
+#semanage login -a -s sysadm_u &lt;username&gt;
+
+Use the following command to map an existing user to the "sysdam_u" role:
+
+#semanage login -m -s sysadm_u &lt;username&gt;
+
+Use the following command to map a new user to the "staff_u" role:
+
+#semanage login -a -s staff_u &lt;username&gt;
+
+Use the following command to map an existing user to the "staff_u" role:
+
+#semanage login -m -s staff_u &lt;username&gt;
+
+Use the following command to map a new user to the "user_u" role:
+
+# semanage login -a -s user_u &lt;username&gt;
+
+Use the following command to map an existing user to the "user_u" role:
+
+# semanage login -m -s user_u &lt;username&gt;</fixtext>
+      <fix id="F-78323r1_fix"/>
+      <check system="C-72203r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
+
+Get a list of authorized users (other than System Administrator and guest accounts) for the system.
+
+Check the list against the system by using the following command:
+
+# semanage login -l | more
+Login Name  SELinux User   MLS/MCS Range  Service
+__default__  user_u    s0-s0:c0.c1023   *
+root   unconfined_u   s0-s0:c0.c1023   *
+system_u  system_u   s0-s0:c0.c1023   *
+joe  staff_u   s0-s0:c0.c1023   *
+
+All administrators must be mapped to the "sysadm_u" or "staff_u" users with the appropriate domains (sysadm_t and staff_t).
+
+All authorized non-administrative users must be mapped to the "user_u" role or the appropriate domain (user_t).
+
+If they are not mapped in this way, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71973">
+    <title>SRG-OS-000363-GPOS-00150</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86597r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020030</version>
+      <title>A file integrity tool must verify the baseline operating system configuration at least weekly.</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 Information Management Officer (IMO)/Information System Security Officer (ISSO) and System Administrators (SAs) must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001744</ident>
+      <fixtext fixref="F-78325r1_fix">Configure the file integrity tool to automatically run on the system at least weekly. The following example output is generic. It will set cron to run AIDE daily, but other file integrity tools may be used:
+
+# cat /etc/cron.daily/aide 
+0 0 * * * /usr/sbin/aide --check | /bin/mail -s "aide integrity check run for &lt;system name&gt;" root@sysname.mil</fixtext>
+      <fix id="F-78325r1_fix"/>
+      <check system="C-72205r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system routinely checks the baseline configuration for unauthorized changes.
+
+Note: A file integrity tool other than Advanced Intrusion Detection Environment (AIDE) may be used, but the tool must be executed at least once per week.
+
+Check to see if AIDE is installed on the system with the following command:
+
+# yum list installed aide
+
+If AIDE is not installed, ask the SA how file integrity checks are performed on the system.
+
+Check for the presence of a cron job running daily or weekly on the system that executes AIDE daily to scan for changes to the system baseline. The command used in the example will use a daily occurrence.
+
+Check the "/etc/cron.daily" subdirectory for a "crontab" file controlling the execution of the file integrity application. For example, if AIDE is installed on the system, use the following command:
+
+# ls -al /etc/cron.* | grep aide
+-rwxr-xr-x  1 root root        29 Nov  22  2015 aide
+
+If the file integrity application does not exist, or a "crontab" file does not exist in the "/etc/cron.daily" or "/etc/cron.weekly" subdirectories, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71975">
+    <title>SRG-OS-000363-GPOS-00150</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86599r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020040</version>
+      <title>Designated personnel must be notified if baseline configurations are changed in an unauthorized manner.</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 Information Management Officer (IMO)/Information System Security Officer (ISSO) and System Administrators (SAs) must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001744</ident>
+      <fixtext fixref="F-78327r1_fix">Configure the operating system to notify designated personnel if baseline configurations are changed in an unauthorized manner. The AIDE tool can be configured to email designated personnel through the use of the cron system.  
+
+The following example output is generic. It will set cron to run AIDE daily and to send email at the completion of the analysis. 
+
+# more /etc/cron.daily/aide
+0 0 * * * /usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily aide integrity check run" root@sysname.mil</fixtext>
+      <fix id="F-78327r1_fix"/>
+      <check system="C-72207r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system notifies designated personnel if baseline configurations are changed in an unauthorized manner.
+
+Note: A file integrity tool other than Advanced Intrusion Detection Environment (AIDE) may be used, but the tool must be executed and notify specified individuals via email or an alert.
+
+Check to see if AIDE is installed on the system with the following command:
+
+# yum list installed aide
+
+If AIDE is not installed, ask the SA how file integrity checks are performed on the system. 
+
+Check for the presence of a cron job running routinely on the system that executes AIDE to scan for changes to the system baseline. The commands used in the example will use a daily occurrence.
+
+Check the "/etc/cron.daily" subdirectory for a "crontab" file controlling the execution of the file integrity application. For example, if AIDE is installed on the system, use the following commands:
+
+# ls -al /etc/cron.daily | grep aide
+-rwxr-xr-x  1 root root        32 Jul  1  2011 aide
+
+AIDE does not have a configuration that will send a notification, so the cron job uses the mail application on the system to email the results of the file integrity run as in the following example:
+
+# more /etc/cron.daily/aide
+0 0 * * * /usr/sbin/aide --check | /bin/mail -s "$HOSTNAME - Daily aide integrity check run" root@sysname.mil
+
+If the file integrity application does not notify designated personnel of changes, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71977">
+    <title>SRG-OS-000366-GPOS-00153</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86601r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-020050</version>
+      <title>The operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization.</title>
+      <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 verifies the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001749</ident>
+      <fixtext fixref="F-78329r1_fix">Configure the operating system to verify the signature of packages from a repository prior to install by setting the following option in the "/etc/yum.conf" file:
+
+gpgcheck=1</fixtext>
+      <fix id="F-78329r1_fix"/>
+      <check system="C-72209r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components from a repository without verification that they have been digitally signed using a certificate that is recognized and approved by the organization.
+
+Check that yum verifies the signature of packages from a repository prior to install with the following command:
+
+# grep gpgcheck /etc/yum.conf
+gpgcheck=1
+
+If "gpgcheck" is not set to "1", or if options are missing or commented out, ask the System Administrator how the certificates for patches and other operating system components are verified. 
+
+If there is no process to validate certificates that is approved by the organization, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71979">
+    <title>SRG-OS-000366-GPOS-00153</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86603r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-020060</version>
+      <title>The operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization.</title>
+      <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 verifies the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001749</ident>
+      <fixtext fixref="F-78331r1_fix">Configure the operating system to verify the signature of local packages prior to install by setting the following option in the "/etc/yum.conf" file:
+
+localpkg_gpgcheck=1</fixtext>
+      <fix id="F-78331r1_fix"/>
+      <check system="C-72211r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components of local packages without verification that they have been digitally signed using a certificate that is recognized and approved by the organization.
+
+Check that yum verifies the signature of local packages prior to install with the following command:
+
+# grep localpkg_gpgcheck /etc/yum.conf
+localpkg_gpgcheck=1
+
+If "localpkg_gpgcheck" is not set to "1", or if options are missing or commented out, ask the System Administrator how the signatures of local packages and other operating system components are verified. 
+
+If there is no process to validate the signatures of local packages that is approved by the organization, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71981">
+    <title>SRG-OS-000366-GPOS-00153</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86605r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-020070</version>
+      <title>The operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of packages without verification of the repository metadata.</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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001749</ident>
+      <fixtext fixref="F-78333r1_fix">Configure the operating system to verify the repository metadata by setting the following options in the "/etc/yum.conf" file:
+
+repo_gpgcheck=1</fixtext>
+      <fix id="F-78333r1_fix"/>
+      <check system="C-72213r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system prevents the installation of patches, service packs, device drivers, or operating system components of local packages without verification of the repository metadata.
+
+Check that yum verifies the package metadata prior to install with the following command:
+
+# grep repo_gpgcheck /etc/yum.conf
+repo_gpgcheck=1
+
+If "repo_gpgcheck" is not set to "1", or if options are missing or commented out, ask the System Administrator how the metadata of local packages and other operating system components are verified. 
+
+If there is no process to validate the metadata of packages that is approved by the organization, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71983">
+    <title>SRG-OS-000114-GPOS-00059</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86607r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020100</version>
+      <title>USB mass storage must be disabled.</title>
+      <description>&lt;VulnDiscussion&gt;USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity.
+
+Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000778</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001958</ident>
+      <fixtext fixref="F-78335r1_fix">Configure the operating system to disable the ability to use USB mass storage devices.
+
+Create a file under "/etc/modprobe.d" with the following command:
+
+#touch /etc/modprobe.d/nousbstorage
+
+Add the following line to the created file:
+
+install usb-storage /bin/true</fixtext>
+      <fix id="F-78335r1_fix"/>
+      <check system="C-72215r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>If there is an HBSS with a Device Control Module and a Data Loss Prevention mechanism, this requirement is not applicable.
+
+Verify the operating system disables the ability to use USB mass storage devices.
+
+Check to see if USB mass storage is disabled with the following command:
+
+#grep -i usb-storage /etc/modprobe.d/*
+
+install usb-storage /bin/true
+
+If the command does not return any output, and use of USB storage devices is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71985">
+    <title>SRG-OS-000114-GPOS-00059</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86609r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020110</version>
+      <title>File system automounter must be disabled unless required.</title>
+      <description>&lt;VulnDiscussion&gt;Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity.
+
+Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000778</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001958</ident>
+      <fixtext fixref="F-78337r1_fix">Configure the operating system to disable the ability to automount devices.
+
+Turn off the automount service with the following command:
+
+# systemctl disable autofs
+
+If "autofs" is required for Network File System (NFS), it must be documented with the ISSO.</fixtext>
+      <fix id="F-78337r1_fix"/>
+      <check system="C-72217r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system disables the ability to automount devices.
+
+Check to see if automounter service is active with the following command:
+
+# systemctl status autofs
+autofs.service - Automounts filesystems on demand
+   Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled)
+   Active: inactive (dead)
+
+If the "autofs" status is set to "active" and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71987">
+    <title>SRG-OS-000437-GPOS-00194</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86611r1_rule" severity="low" weight="10.0">
+      <version>RHEL-07-020200</version>
+      <title>The operating system must remove 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002617</ident>
+      <fixtext fixref="F-78339r1_fix">Configure the operating system to remove all software components after updated versions have been installed.
+
+Set the "clean_requirements_on_remove" option to "1" in the "/etc/yum.conf" file:
+
+clean_requirements_on_remove=1</fixtext>
+      <fix id="F-78339r1_fix"/>
+      <check system="C-72219r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system removes all software components after updated versions have been installed.
+
+Check if yum is configured to remove unneeded packages with the following command:
+
+# grep -i clean_requirements_on_remove /etc/yum.conf
+clean_requirements_on_remove=1
+
+If "clean_requirements_on_remove" is not set to "1", "True", or "yes", or is not set in "/etc/yum.conf", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71989">
+    <title>SRG-OS-000445-GPOS-00199</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86613r2_rule" severity="high" weight="10.0">
+      <version>RHEL-07-020210</version>
+      <title>The operating system must enable SELinux.</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 operating systems performing security function verification/testing and/or systems and environments that require this functionality.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002165</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002696</ident>
+      <fixtext fixref="F-78341r2_fix">Configure the operating system to verify correct operation of all security functions.
+
+Set the "SELinux" status and the "Enforcing" mode by modifying the "/etc/selinux/config" file to have the following line:
+
+SELINUX=enforcing
+
+A reboot is required for the changes to take effect.</fixtext>
+      <fix id="F-78341r2_fix"/>
+      <check system="C-72221r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system verifies correct operation of all security functions.
+
+Check if "SELinux" is active and in "Enforcing" mode with the following command:
+
+# getenforce
+Enforcing
+
+If "SELinux" is not active and not in "Enforcing" mode, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71991">
+    <title>SRG-OS-000445-GPOS-00199</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86615r2_rule" severity="high" weight="10.0">
+      <version>RHEL-07-020220</version>
+      <title>The operating system must enable the SELinux targeted policy.</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 operating systems performing security function verification/testing and/or systems and environments that require this functionality.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002165</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002696</ident>
+      <fixtext fixref="F-78343r2_fix">Configure the operating system to verify correct operation of all security functions.
+
+Set the "SELinuxtype" to the "targeted" policy by modifying the "/etc/selinux/config" file to have the following line:
+
+SELINUXTYPE=targeted
+
+A reboot is required for the changes to take effect.</fixtext>
+      <fix id="F-78343r2_fix"/>
+      <check system="C-72223r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system verifies correct operation of all security functions.
+
+Check if "SELinux" is active and is enforcing the targeted policy with the following command:
+
+# sestatus
+SELinux status:                 enabled
+SELinuxfs mount:                /selinu
+XCurrent mode:                   enforcing
+Mode from config file:          enforcing
+Policy version:                 24
+Policy from config file:        targeted
+
+If the "Policy from config file" is not set to "targeted", or the "Loaded policy name" is not set to "targeted", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71993">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86617r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-020230</version>
+      <title>The x86 Ctrl-Alt-Delete key sequence must be disabled.</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 GNOME 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78345r2_fix">Configure the system to disable the Ctrl-Alt_Delete sequence for the command line with the following command:
+
+# systemctl mask ctrl-alt-del.target
+
+If GNOME is active on the system, create a database to contain the system-wide setting (if it does not already exist) with the following command: 
+
+# cat /etc/dconf/db/local.d/00-disable-CAD 
+
+Add the setting to disable the Ctrl-Alt_Delete sequence for GNOME:
+
+[org/gnome/settings-daemon/plugins/media-keys]
+logout=’’</fixtext>
+      <fix id="F-78345r2_fix"/>
+      <check system="C-72225r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system is not configured to reboot the system when Ctrl-Alt-Delete is pressed.
+
+Check that the ctrl-alt-del.service is not active with the following command:
+
+# systemctl status ctrl-alt-del.service
+reboot.target - Reboot
+   Loaded: loaded (/usr/lib/systemd/system/reboot.target; disabled)
+   Active: inactive (dead)
+     Docs: man:systemd.special(7)
+
+If the ctrl-alt-del.service is active, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71995">
+    <title>SRG-OS-000480-GPOS-00228</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86619r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020240</version>
+      <title>The operating system must define default permissions for all authenticated users in such a way that the user can only read and modify their own files.</title>
+      <description>&lt;VulnDiscussion&gt;Setting the most restrictive default permissions ensures that when new accounts are created, they 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78347r1_fix">Configure the operating system to define default permissions for all authenticated users in such a way that the user can only read and modify their own files.
+
+Add or edit the line for the "UMASK" parameter in "/etc/login.defs" file to "077":
+
+UMASK  077</fixtext>
+      <fix id="F-78347r1_fix"/>
+      <check system="C-72227r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system defines default permissions for all authenticated users in such a way that the user can only read and modify their own files.
+
+Check for the value of the "UMASK" parameter in "/etc/login.defs" file with the following command:
+
+Note: If the value of the "UMASK" parameter is set to "000" in "/etc/login.defs" file, the Severity is raised to a CAT I.
+
+# grep -i umask /etc/login.defs
+UMASK  077
+
+If the value for the "UMASK" parameter is not "077", or the "UMASK" parameter is missing or is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71997">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86621r2_rule" severity="high" weight="10.0">
+      <version>RHEL-07-020250</version>
+      <title>The operating system must be a vendor supported release.</title>
+      <description>&lt;VulnDiscussion&gt;An operating system release is considered "supported" if the vendor continues to provide security patches for the product. With an unsupported release, it will not be possible to resolve security issues discovered in the system software.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78349r1_fix">Upgrade to a supported version of the operating system.</fixtext>
+      <fix id="F-78349r1_fix"/>
+      <check system="C-72229r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the version of the operating system is vendor supported.
+
+Check the version of the operating system with the following command:
+
+# cat /etc/redhat-release
+
+Red Hat Enterprise Linux Server release 7.2 (Maipo)
+
+Current End of Life for RHEL 7.2 is Q4 2020.
+
+Current End of Life for RHEL 7.3 is 30 June 2024.
+
+If the release is not supported by the vendor, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-71999">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86623r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020260</version>
+      <title>Vendor packaged system security patches and updates must be installed and up to date.</title>
+      <description>&lt;VulnDiscussion&gt;Timely patching is critical for maintaining the operational availability, confidentiality, and integrity of information technology (IT) systems. However, failure to keep operating system and application software patched is a common mistake made by IT professionals. New patches are released daily, and it is often difficult for even experienced System Administrators to keep abreast of all the new patches. When new weaknesses in an operating system exist, patches are usually made available by the vendor to resolve the problems. If the most recent security patches and updates are not installed, unauthorized users may take advantage of weaknesses in the unpatched software. The lack of prompt attention to patching could result in a system compromise.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78351r1_fix">Install the operating system patches or updated packages available from Red Hat within 30 days or sooner as local policy dictates.</fixtext>
+      <fix id="F-78351r1_fix"/>
+      <check system="C-72231r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system security patches and updates are installed and up to date. Updates are required to be applied with a frequency determined by the site or Program Management Office (PMO). 
+
+Obtain the list of available package security updates from Red Hat. The URL for updates is https://rhn.redhat.com/errata/. It is important to note that updates provided by Red Hat may not be present on the system if the underlying packages are not installed.
+
+Check that the available package security updates have been installed on the system with the following command:
+
+# yum history list | more
+Loaded plugins: langpacks, product-id, subscription-manager
+ID     | Command line             | Date and time    | Action(s)      | Altered
+-------------------------------------------------------------------------------
+    70 | install aide             | 2016-05-05 10:58 | Install       |     1   
+    69 | update -y                | 2016-05-04 14:34 | Update     |   18 EE
+    68 | install vlc                | 2016-04-21 17:12 | Install        |   21   
+    67 | update -y                | 2016-04-21 17:04 | Update     |     7 EE
+    66 | update -y                | 2016-04-15 16:47 | E, I, U         |   84 EE
+
+If package updates have not been performed on the system within the timeframe that the site/program documentation requires, this is a finding. 
+
+Typical update frequency may be overridden by Information Assurance Vulnerability Alert (IAVA) notifications from CYBERCOM.
+
+If the operating system is in non-compliance with the Information Assurance Vulnerability Management (IAVM) process, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72001">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86625r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020270</version>
+      <title>The system must not have unnecessary accounts.</title>
+      <description>&lt;VulnDiscussion&gt;Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for individuals not requiring access to the system and application accounts for applications not installed 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78353r1_fix">Configure the system so all accounts on the system are assigned to an active system, application, or user account. 
+
+Remove accounts that do not support approved system activities or that allow for a normal user to perform administrative-level actions. 
+
+Document all authorized accounts on the system.</fixtext>
+      <fix id="F-78353r1_fix"/>
+      <check system="C-72233r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify all accounts on the system are assigned to an active system, application, or user account.
+
+Obtain the list of authorized system accounts from the Information System Security Officer (ISSO).
+
+Check the system accounts on the system with the following command:
+
+# more /etc/passwd
+root:x:0:0:root:/root:/bin/bash
+bin:x:1:1:bin:/bin:/sbin/nologin
+daemon:x:2:2:daemon:/sbin:/sbin/nologin
+sync:x:5:0:sync:/sbin:/bin/sync
+shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown
+halt:x:7:0:halt:/sbin:/sbin/halt
+games:x:12:100:games:/usr/games:/sbin/nologin
+gopher:x:13:30:gopher:/var/gopher:/sbin/nologin
+
+Accounts such as "games" and "gopher" are not authorized accounts as they do not support authorized system functions. 
+
+If the accounts on the system do not match the provided documentation, or accounts that do not support an authorized system function are present, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72003">
+    <title>SRG-OS-000104-GPOS-00051</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86627r1_rule" severity="low" weight="10.0">
+      <version>RHEL-07-020300</version>
+      <title>All Group Identifiers (GIDs) referenced in the /etc/passwd file must be defined in the /etc/group file.</title>
+      <description>&lt;VulnDiscussion&gt;If a user is assigned the GID of a group not existing on the system, and a group with the GID is subsequently created, the user may have unintended rights to any files associated with the group.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000764</ident>
+      <fixtext fixref="F-78355r1_fix">Configure the system to define all GIDs found in the "/etc/passwd" file by modifying the "/etc/group" file to add any non-existent group referenced in the "/etc/passwd" file, or change the GIDs referenced in the "/etc/passwd" file to a group that exists in "/etc/group".</fixtext>
+      <fix id="F-78355r1_fix"/>
+      <check system="C-72235r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify all GIDs referenced in the "/etc/passwd" file are defined in the "/etc/group" file.
+
+Check that all referenced GIDs exist with the following command:
+
+# pwck -r
+
+If GIDs referenced in "/etc/passwd" file are returned as not defined in "/etc/group" file, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72005">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86629r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-020310</version>
+      <title>The root account must be the only account having unrestricted access to the system.</title>
+      <description>&lt;VulnDiscussion&gt;If an account other than root also has a User Identifier (UID) of "0", it has root authority, giving that account unrestricted access to the entire operating system. Multiple accounts with a UID of "0" afford an opportunity for potential intruders to guess a password for a privileged account.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78357r1_fix">Change the UID of any account on the system, other than root, that has a UID of "0". 
+
+If the account is associated with system commands or applications, the UID should be changed to one greater than "0" but less than "1000". Otherwise, assign a UID of greater than "1000" that has not already been assigned.</fixtext>
+      <fix id="F-78357r1_fix"/>
+      <check system="C-72237r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Check the system for duplicate UID "0" assignments with the following command:
+
+# awk -F: '$3 == 0 {print $1}' /etc/passwd
+
+If any accounts other than root have a UID of "0", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72007">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86631r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020320</version>
+      <title>All files and directories must have a valid owner.</title>
+      <description>&lt;VulnDiscussion&gt;Unowned files and directories may be unintentionally inherited if a user is assigned the same User Identifier "UID" as the UID of the un-owned 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002165</ident>
+      <fixtext fixref="F-78359r1_fix">Either remove all files and directories from the system that do not have a valid user, or assign a valid user to all unowned files and directories on the system with the "chown" command:
+
+# chown &lt;user&gt; &lt;file&gt;</fixtext>
+      <fix id="F-78359r1_fix"/>
+      <check system="C-72239r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify all files and directories on the system have a valid owner.
+
+Check the owner of all files and directories with the following command:
+
+Note: The value after -fstype must be replaced with the filesystem type. XFS is used as an example.
+
+# find / -xdev -fstype xfs -nouser
+
+If any files on the system do not have an assigned owner, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72009">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86633r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020330</version>
+      <title>All files and directories must have a valid group owner.</title>
+      <description>&lt;VulnDiscussion&gt;Files without a valid group owner may be unintentionally inherited if a group is assigned the same Group Identifier (GID) as the GID of the files without a valid group owner.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002165</ident>
+      <fixtext fixref="F-78361r1_fix">Either remove all files and directories from the system that do not have a valid group, or assign a valid group to all files and directories on the system with the "chgrp" command:
+
+# chgrp &lt;group&gt; &lt;file&gt;</fixtext>
+      <fix id="F-78361r1_fix"/>
+      <check system="C-72241r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify all files and directories on the system have a valid group.
+
+Check the owner of all files and directories with the following command:
+
+Note: The value after -fstype must be replaced with the filesystem type. XFS is used as an example.
+
+# find / -xdev -fstype xfs -nogroup
+
+If any files on the system do not have an assigned group, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72011">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86635r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020600</version>
+      <title>All local interactive users must have a home directory assigned in the /etc/passwd file.</title>
+      <description>&lt;VulnDiscussion&gt;If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78363r1_fix">Assign home directories to all local interactive users that currently do not have a home directory assigned.</fixtext>
+      <fix id="F-78363r1_fix"/>
+      <check system="C-72243r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify local interactive users on the system have a home directory assigned.
+
+Check for missing local interactive user home directories with the following command:
+
+# pwck -r
+user 'lp': directory '/var/spool/lpd' does not exist
+user 'news': directory '/var/spool/news' does not exist
+user 'uucp': directory '/var/spool/uucp' does not exist
+user 'smithj': directory '/home/smithj' does not exist
+
+Ask the System Administrator (SA) if any users found without home directories are local interactive users. If the SA is unable to provide a response, check for users with a User Identifier (UID) of 1000 or greater with the following command:
+
+# cut -d: -f 1,3 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$"
+
+If any interactive users do not have a home directory assigned, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72013">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86637r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020610</version>
+      <title>All local interactive user accounts, upon creation, must be assigned a home directory.</title>
+      <description>&lt;VulnDiscussion&gt;If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78365r1_fix">Configure the operating system to assign home directories to all new local interactive users by setting the "CREATE_HOME" parameter in "/etc/login.defs" to "yes" as follows.
+
+CREATE_HOME yes</fixtext>
+      <fix id="F-78365r1_fix"/>
+      <check system="C-72245r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify all local interactive users on the system are assigned a home directory upon creation.
+
+Check to see if the system is configured to create home directories for local interactive users with the following command:
+
+# grep -i create_home /etc/login.defs
+CREATE_HOME yes
+
+If the value for "CREATE_HOME" parameter is not set to "yes", the line is missing, or the line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72015">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86639r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020620</version>
+      <title>All local interactive user home directories defined in the /etc/passwd file must exist.</title>
+      <description>&lt;VulnDiscussion&gt;If a local interactive user has a home directory defined that does not exist, the user may be given access to the / directory as the current working directory upon logon. This could create a Denial of Service because the user would not be able to access their logon configuration files, and it may give them visibility to system files they normally would not be able to access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78367r1_fix">Create home directories to all local interactive users that currently do not have a home directory assigned. Use the following commands to create the user home directory assigned in "/etc/ passwd":
+
+Note: The example will be for the user smithj, who has a home directory of "/home/smithj", a UID of "smithj", and a Group Identifier (GID) of "users assigned" in "/etc/passwd".
+
+# mkdir /home/smithj 
+# chown smithj /home/smithj
+# chgrp users /home/smithj
+# chmod 0750 /home/smithj</fixtext>
+      <fix id="F-78367r1_fix"/>
+      <check system="C-72247r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the assigned home directory of all local interactive users on the system exists.
+
+Check the home directory assignment for all local interactive non-privileged users on the system with the following command:
+
+# cut -d: -f 1,3 /etc/passwd | egrep ":[1-9][0-9]{2}$|:[0-9]{1,2}$"
+smithj /home/smithj
+
+Note: This may miss interactive users that have been assigned a privileged UID. Evidence of interactive use may be obtained from a number of log files containing system logon information.
+
+Check that all referenced home directories exist with the following command:
+
+# pwck -r
+user 'smithj': directory '/home/smithj' does not exist
+
+If any home directories referenced in "/etc/passwd" are returned as not defined, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72017">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86641r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020630</version>
+      <title>All local interactive user home directories must have mode 0750 or less permissive.</title>
+      <description>&lt;VulnDiscussion&gt;Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78369r1_fix">Change the mode of interactive user’s home directories to "0750". To change the mode of a local interactive user’s home directory, use the following command:
+
+Note: The example will be for the user "smithj".
+
+# chmod 0750 /home/smithj</fixtext>
+      <fix id="F-78369r1_fix"/>
+      <check system="C-72249r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the assigned home directory of all local interactive users has a mode of "0750" or less permissive.
+
+Check the home directory assignment for all non-privileged users on the system with the following command:
+
+Note: This may miss interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information.
+
+# ls -ld $ (egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)
+-rwxr-x--- 1 smithj users  18 Mar  5 17:06 /home/smithj
+
+If home directories referenced in "/etc/passwd" do not have a mode of "0750" or less permissive, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72019">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86643r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020640</version>
+      <title>All local interactive user home directories must be owned by their respective users.</title>
+      <description>&lt;VulnDiscussion&gt;If a local interactive user does not own their home directory, unauthorized users could access or modify the user's files, and the users may not be able to access their own 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78371r1_fix">Change the owner of a local interactive user’s home directories to that owner. To change the owner of a local interactive user’s home directory, use the following command:
+
+Note: The example will be for the user smithj, who has a home directory of "/home/smithj".
+
+# chown smithj /home/smithj</fixtext>
+      <fix id="F-78371r1_fix"/>
+      <check system="C-72251r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the assigned home directory of all local interactive users on the system exists.
+
+Check the home directory assignment for all local interactive non-privileged users on the system with the following command:
+
+Note: This may miss interactive users that have been assigned a privileged UID. Evidence of interactive use may be obtained from a number of log files containing system logon information.
+
+# ls -ld $ (egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)
+-rwxr-x--- 1 smithj users  18 Mar  5 17:06 /home/smithj
+
+If any home directories referenced in "/etc/passwd" are returned as not defined, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72021">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86645r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020650</version>
+      <title>All local interactive user home directories must be group-owned by the home directory owners primary group.</title>
+      <description>&lt;VulnDiscussion&gt;If the Group Identifier (GID) of a local interactive user’s home directory is not the same as the primary GID of the user, this would allow unauthorized access to the user’s files, and users that share the same group may not be able to access files that they legitimately should.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78373r1_fix">Change the group owner of a local interactive user’s home directory to the group found in "/etc/passwd". To change the group owner of a local interactive user’s home directory, use the following command:
+
+Note: The example will be for the user "smithj", who has a home directory of "/home/smithj", and has a primary group of users.
+
+# chgrp users /home/smithj</fixtext>
+      <fix id="F-78373r1_fix"/>
+      <check system="C-72253r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the assigned home directory of all local interactive users is group-owned by that user’s primary GID.
+
+Check the home directory assignment for all non-privileged users on the system with the following command:
+
+Note: This may miss local interactive users that have been assigned a privileged UID. Evidence of interactive use may be obtained from a number of log files containing system logon information.
+
+# ls -ld $ (egrep ':[0-9]{4}' /etc/passwd | cut -d: -f6)
+-rwxr-x--- 1 smithj users  18 Mar  5 17:06 /home/smithj
+
+Check the user's primary group with the following command:
+
+# grep users /etc/group
+users:x:250:smithj,jonesj,jacksons
+
+If the user home directory referenced in "/etc/passwd" is not group-owned by that user’s primary GID, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72023">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86647r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020660</version>
+      <title>All files and directories contained in local interactive user home directories must be owned by the owner of the home directory.</title>
+      <description>&lt;VulnDiscussion&gt;If local interactive users do not own the files in their directories, unauthorized users may be able to access them. Additionally, if files are not owned by the user, this could be an indication of system compromise.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78375r1_fix">Change the owner of a local interactive user’s files and directories to that owner. To change the owner of a local interactive user’s files and directories, use the following command:
+
+Note: The example will be for the user smithj, who has a home directory of "/home/smithj".
+
+# chown smithj /home/smithj/&lt;file or directory&gt;</fixtext>
+      <fix id="F-78375r1_fix"/>
+      <check system="C-72255r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify all files and directories in a local interactive user’s home directory are owned by the user.
+
+Check the owner of all files and directories in a local interactive user’s home directory with the following command:
+
+Note: The example will be for the user "smithj", who has a home directory of "/home/smithj".
+
+# ls -lLR /home/smithj
+-rw-r--r-- 1 smithj smithj  18 Mar  5 17:06 file1
+-rw-r--r-- 1 smithj smithj 193 Mar  5 17:06 file2
+-rw-r--r-- 1 smithj smithj 231 Mar  5 17:06 file3
+
+If any files are found with an owner different than the home directory user, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72025">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86649r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020670</version>
+      <title>All files and directories contained in local interactive user home directories must be group-owned by a group of which the home directory owner is a member.</title>
+      <description>&lt;VulnDiscussion&gt;If a local interactive user’s files are group-owned by a group of which the user is not a member, unintended users may be able to access them.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78377r1_fix">Change the group of a local interactive user’s files and directories to a group that the interactive user is a member of. To change the group owner of a local interactive user’s files and directories, use the following command:
+
+Note: The example will be for the user smithj, who has a home directory of "/home/smithj" and is a member of the users group.
+
+# chgrp users /home/smithj/&lt;file&gt;</fixtext>
+      <fix id="F-78377r1_fix"/>
+      <check system="C-72257r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify all files and directories in a local interactive user home directory are group-owned by a group the user is a member of.
+
+Check the group owner of all files and directories in a local interactive user’s home directory with the following command:
+
+Note: The example will be for the user "smithj", who has a home directory of "/home/smithj".
+
+# ls -lLR /&lt;home directory&gt;/&lt;users home directory&gt;/
+-rw-r--r-- 1 smithj smithj  18 Mar  5 17:06 file1
+-rw-r--r-- 1 smithj smithj 193 Mar  5 17:06 file2
+-rw-r--r-- 1 smithj sa        231 Mar  5 17:06 file3
+
+If any files are found with an owner different than the group home directory user, check to see if the user is a member of that group with the following command:
+
+# grep smithj /etc/group
+sa:x:100:juan,shelley,bob,smithj 
+smithj:x:521:smithj
+
+If the user is not a member of a group that group owns file(s) in a local interactive user’s home directory, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72027">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86651r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020680</version>
+      <title>All files and directories contained in local interactive user home directories must have mode 0750 or less permissive.</title>
+      <description>&lt;VulnDiscussion&gt;If a local interactive user files have excessive permissions, unintended users may be able to access or modify them.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78379r1_fix">Set the mode on files and directories in the local interactive user home directory with the following command:
+
+Note: The example will be for the user smithj, who has a home directory of "/home/smithj" and is a member of the users group.
+
+# chmod 0750 /home/smithj/&lt;file&gt;</fixtext>
+      <fix id="F-78379r1_fix"/>
+      <check system="C-72259r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify all files and directories contained in a local interactive user home directory, excluding local initialization files, have a mode of "0750".
+
+Check the mode of all non-initialization files in a local interactive user home directory with the following command:
+
+Files that begin with a "." are excluded from this requirement.
+
+Note: The example will be for the user "smithj", who has a home directory of "/home/smithj".
+
+# ls -lLR /home/smithj
+-rwxr-x--- 1 smithj smithj  18 Mar  5 17:06 file1
+-rwxr----- 1 smithj smithj 193 Mar  5 17:06 file2
+-rw-r-x--- 1 smithj smithj 231 Mar  5 17:06 file3
+
+If any files are found with a mode more permissive than "0750", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72029">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86653r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020690</version>
+      <title>All local initialization files for interactive users must be owned by the home directory user or root.</title>
+      <description>&lt;VulnDiscussion&gt;Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78381r1_fix">Set the owner of the local initialization files for interactive users to either the directory owner or root with the following command:
+
+Note: The example will be for the smithj user, who has a home directory of "/home/smithj".
+
+# chown smithj /home/smithj/.*</fixtext>
+      <fix id="F-78381r1_fix"/>
+      <check system="C-72261r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify all local initialization files for interactive users are owned by the home directory user or root.
+
+Check the owner on all local initialization files with the following command:
+
+Note: The example will be for the "smithj" user, who has a home directory of "/home/smithj".
+
+# ls -al /home/smithj/.* | more
+-rwxr-xr-x  1 smithj users        896 Mar 10  2011 .bash_profile
+-rwxr-xr-x  1 smithj users        497 Jan  6  2007 .login
+-rwxr-xr-x  1 smithj users        886 Jan  6  2007 .profile
+
+If any file that sets a local interactive user’s environment variables to override the system is not owned by the home directory owner or root, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72031">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86655r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020700</version>
+      <title>Local initialization files for local interactive users must be group-owned by the users primary group or root.</title>
+      <description>&lt;VulnDiscussion&gt;Local initialization files for interactive users are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78383r1_fix">Change the group owner of a local interactive user’s files to the group found in "/etc/passwd" for the user. To change the group owner of a local interactive user home directory, use the following command:
+
+Note: The example will be for the user smithj, who has a home directory of "/home/smithj", and has a primary group of users.
+
+# chgrp users /home/smithj/&lt;file&gt;</fixtext>
+      <fix id="F-78383r1_fix"/>
+      <check system="C-72263r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the local initialization files of all local interactive users are group-owned by that user’s primary Group Identifier (GID).
+
+Check the home directory assignment for all non-privileged users on the system with the following command:
+
+Note: The example will be for the smithj user, who has a home directory of "/home/smithj" and a primary group of "users".
+
+# cut -d: -f 1,4,6 /etc/passwd | egrep ":[1-4][0-9]{3}"
+smithj:1000:/home/smithj
+
+# grep 1000 /etc/group
+users:x:1000:smithj,jonesj,jacksons 
+
+Note: This may miss interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information.
+
+Check the group owner of all local interactive users’ initialization files with the following command:
+
+# ls -al /home/smithj/.*
+-rwxr-xr-x  1 smithj users        896 Mar 10  2011 .profile
+-rwxr-xr-x  1 smithj users        497 Jan  6  2007 .login
+-rwxr-xr-x  1 smithj users        886 Jan  6  2007 .something
+
+If all local interactive users’ initialization files are not group-owned by that user’s primary GID, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72033">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86657r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020710</version>
+      <title>All local initialization files must have mode 0740 or less permissive.</title>
+      <description>&lt;VulnDiscussion&gt;Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78385r1_fix">Set the mode of the local initialization files to "0740" with the following command:
+
+Note: The example will be for the smithj user, who has a home directory of "/home/smithj".
+
+# chmod 0740 /home/smithj/.&lt;INIT_FILE&gt;</fixtext>
+      <fix id="F-78385r1_fix"/>
+      <check system="C-72265r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that all local initialization files have a mode of "0740" or less permissive.
+
+Check the mode on all local initialization files with the following command:
+
+Note: The example will be for the smithj user, who has a home directory of "/home/smithj".
+
+# ls -al /home/smithj/.* | more
+-rwxr-xr-x  1 smithj users        896 Mar 10  2011 .profile
+-rwxr-xr-x  1 smithj users        497 Jan  6  2007 .login
+-rwxr-xr-x  1 smithj users        886 Jan  6  2007 .something
+
+If any local initialization files have a mode more permissive than "0740", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72035">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86659r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020720</version>
+      <title>All local interactive user initialization files executable search paths must contain only paths that resolve to the users home directory.</title>
+      <description>&lt;VulnDiscussion&gt;The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If this path includes the current working directory (other than the user’s home directory), executables in these directories may be executed instead of system commands. This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon or two consecutive colons, this is interpreted as the current working directory. If deviations from the default system search path for the local interactive user are required, they must be documented with the Information System Security Officer (ISSO).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78387r2_fix">Configure the "/etc/fstab" to use the "nosuid" option on file systems that contain user home directories for interactive users.</fixtext>
+      <fix id="F-78387r2_fix"/>
+      <check system="C-72267r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that all local interactive user initialization files' executable search path statements do not contain statements that will reference a working directory other than the users’ home directory.
+
+Check the executable search path statement for all local interactive user initialization files in the users' home directory with the following commands:
+
+Note: The example will be for the smithj user, which has a home directory of "/home/smithj".
+
+# grep -i path /home/smithj/.*
+/home/smithj/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin
+/home/smithj/.bash_profile:export PATH
+
+If any local interactive user initialization files have executable search path statements that include directories outside of their home directory, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72037">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86661r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020730</version>
+      <title>Local initialization files must not execute world-writable programs.</title>
+      <description>&lt;VulnDiscussion&gt;If user start-up files execute world-writable programs, especially in unprotected directories, they could be maliciously modified to destroy user files or otherwise compromise the system at the user level. If the system is compromised at the user level, it is easier to elevate privileges to eventually compromise the system at the root and network level.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78389r1_fix">Set the mode on files being executed by the local initialization files with the following command:
+
+# chmod 0755  &lt;file&gt;</fixtext>
+      <fix id="F-78389r1_fix"/>
+      <check system="C-72269r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that local initialization files do not execute world-writable programs.
+
+Check the system for world-writable files with the following command:
+
+# find / -perm -002 -type f -exec ls -ld {} \; | more
+
+For all files listed, check for their presence in the local initialization files with the following commands:
+
+Note: The example will be for a system that is configured to create users’ home directories in the "/home" directory.
+
+# grep &lt;file&gt; /home/*/.*
+
+If any local initialization files are found to reference world-writable files, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72039">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86663r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-020900</version>
+      <title>All system device files must be correctly labeled to prevent unauthorized modification.</title>
+      <description>&lt;VulnDiscussion&gt;If an unauthorized or modified device is allowed to exist on the system, there is the possibility the system may perform unintended or unauthorized operations.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
+      <fixtext fixref="F-78391r1_fix">Run the following command to determine which package owns the device file:
+
+# rpm -qf &lt;filename&gt;
+
+The package can be reinstalled from a yum repository using the command:
+
+# sudo yum reinstall &lt;packagename&gt;
+
+Alternatively, the package can be reinstalled from trusted media using the command:
+
+# sudo rpm -Uvh &lt;packagename&gt;</fixtext>
+      <fix id="F-78391r1_fix"/>
+      <check system="C-72271r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that all system device files are correctly labeled to prevent unauthorized modification.
+
+List all device files on the system that are incorrectly labeled with the following commands:
+
+Note: Device files are normally found under "/dev", but applications may place device files in other directories and may necessitate a search of the entire system.
+
+#find /dev -context *:device_t:* \( -type c -o -type b \) -printf "%p %Z\n"
+
+#find /dev -context *:unlabeled_t:* \( -type c -o -type b \) -printf "%p %Z\n"
+
+Note: There are device files, such as "/dev/vmci", that are used when the operating system is a host virtual machine. They will not be owned by a user on the system and require the "device_t" label to operate. These device files are not a finding.
+
+If there is output from either of these commands, other than already noted, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72041">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86665r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-021000</version>
+      <title>File systems that contain user home directories must be mounted to prevent files with the setuid and setgid bit set from being executed.</title>
+      <description>&lt;VulnDiscussion&gt;The "nosuid" mount option causes the system to not execute setuid and setgid files with owner privileges. This option must be used for mounting any file system not containing approved setuid and setguid files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78393r2_fix">Configure the "/etc/fstab" to use the "nosuid" option on file systems that contain user home directories.</fixtext>
+      <fix id="F-78393r2_fix"/>
+      <check system="C-72273r6_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify file systems that contain user home directories are mounted with the "nosuid" option.
+
+Find the file system(s) that contain the user home directories with the following command:
+
+Note: If a separate file system has not been created for the user home directories (user home directories are mounted under "/"), this is not a finding as the "nosuid" option cannot be used on the "/" system.
+
+# cut -d: -f 1,6 /etc/passwd | egrep ":[1-4][0-9]{3}"
+smithj:/home/smithj
+thomasr:/home/thomasr
+
+Check the file systems that are mounted at boot time with the following command:
+
+# more /etc/fstab
+
+UUID=a411dc99-f2a1-4c87-9e05-184977be8539 /home   ext4   rw,relatime,discard,data=ordered,nosuid 0 2
+                                                            
+If a file system found in "/etc/fstab" refers to the user home directory file system and it does not have the "nosuid" option set, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72043">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86667r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-021010</version>
+      <title>File systems that are used with removable media must be mounted to prevent files with the setuid and setgid bit set from being executed.</title>
+      <description>&lt;VulnDiscussion&gt;The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78395r1_fix">Configure the "/etc/fstab" to use the "nosuid" option on file systems that are associated with removable media.</fixtext>
+      <fix id="F-78395r1_fix"/>
+      <check system="C-72275r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify file systems that are used for removable media are mounted with the "nouid" option.
+
+Check the file systems that are mounted at boot time with the following command:
+
+# more /etc/fstab
+
+UUID=2bc871e4-e2a3-4f29-9ece-3be60c835222     /mnt/usbflash      vfat   noauto,owner,ro,nosuid                        0 0
+
+If a file system found in "/etc/fstab" refers to removable media and it does not have the "nosuid" option set, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72045">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86669r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-021020</version>
+      <title>File systems that are being imported via Network File System (NFS) must be mounted to prevent files with the setuid and setgid bit set from being executed.</title>
+      <description>&lt;VulnDiscussion&gt;The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78397r1_fix">Configure the "/etc/fstab" to use the "nosuid" option on file systems that are being exported via NFS.</fixtext>
+      <fix id="F-78397r1_fix"/>
+      <check system="C-72277r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify file systems that are being NFS exported are mounted with the "nosuid" option.
+
+Find the file system(s) that contain the directories being exported with the following command:
+
+# more /etc/fstab | grep nfs
+
+UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d    /store           nfs           rw,nosuid                                                    0 0
+
+If a file system found in "/etc/fstab" refers to NFS and it does not have the "nosuid" option set, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72047">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86671r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-021030</version>
+      <title>All world-writable directories must be group-owned by root, sys, bin, or an application group.</title>
+      <description>&lt;VulnDiscussion&gt;If a world-writable directory has the sticky bit set and is not group-owned by a privileged Group Identifier (GID), unauthorized users may be able to modify files created by others.
+
+The only authorized public directories are those temporary directories supplied with the system or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system and by users for temporary file storage, (e.g., /tmp), and for directories requiring global read/write access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78399r1_fix">Change the group of the world-writable directories to root with the following command:
+
+# chgrp root &lt;directory&gt;</fixtext>
+      <fix id="F-78399r1_fix"/>
+      <check system="C-72279r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify all world-writable directories are group-owned by root, sys, bin, or an application group.
+
+Check the system for world-writable directories with the following command:
+
+Note: The value after -fstype must be replaced with the filesystem type. XFS is used as an example.
+
+# find / -perm -002 -xdev -type d -fstype xfs -exec ls -lLd {} \;
+drwxrwxrwt. 2 root root 40 Aug 26 13:07 /dev/mqueue
+drwxrwxrwt. 2 root root 220 Aug 26 13:23 /dev/shm
+drwxrwxrwt. 14 root root 4096 Aug 26 13:29 /tmp
+
+If any world-writable directories are not owned by root, sys, bin, or an application group associated with the directory, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72049">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86673r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-021040</version>
+      <title>The umask must be set to 077 for all local interactive user accounts.</title>
+      <description>&lt;VulnDiscussion&gt;The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 700 or less permissive. Although umask can be represented as a four-digit number, the first digit representing special access modes is typically ignored or required to be "0". This requirement applies to the globally configured system defaults and the local interactive user defaults for each account 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
+      <fixtext fixref="F-78401r1_fix">Remove the umask statement from all local interactive users’ initialization files. 
+
+If the account is for an application, the requirement for a umask less restrictive than "077" can be documented with the Information System Security Officer, but the user agreement for access to the account must specify that the local interactive user must log on to their account first and then switch the user to the application account with the correct option to gain the account’s environment variables.</fixtext>
+      <fix id="F-78401r1_fix"/>
+      <check system="C-72281r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that the default umask for all local interactive users is "077".
+
+Identify the locations of all local interactive user home directories by looking at the "/etc/passwd" file.
+
+Check all local interactive user initialization files for interactive users with the following command:
+
+Note: The example is for a system that is configured to create users home directories in the "/home" directory.
+
+# grep -i umask /home/*/.*
+
+If any local interactive user initialization files are found to have a umask statement that has a value less restrictive than "077", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72051">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86675r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-021100</version>
+      <title>Cron logging must be implemented.</title>
+      <description>&lt;VulnDiscussion&gt;Cron logging can be used to trace the successful or unsuccessful execution of cron jobs. It can also be used to spot intrusions into the use of the cron facility by unauthorized and malicious users.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78403r1_fix">Configure "rsyslog" to log all cron messages by adding or updating the following line to "/etc/rsyslog.conf":
+
+cron.* /var/log/cron.log
+
+Note: The line must be added before the following entry if it exists in "/etc/rsyslog.conf":
+
+*.* ~ # discards everything</fixtext>
+      <fix id="F-78403r1_fix"/>
+      <check system="C-72283r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that "rsyslog" is configured to log cron events.
+
+Check the configuration of "/etc/rsyslog.conf" for the cron facility with the following command:
+
+Note: If another logging package is used, substitute the utility configuration file for "/etc/rsyslog.conf". 
+
+# grep cron /etc/rsyslog.conf
+cron.* /var/log/cron.log
+
+If the command does not return a response, check for cron logging all facilities by inspecting the "/etc/rsyslog.conf" file:
+
+# more /etc/rsyslog.conf
+
+Look for the following entry:
+
+*.* /var/log/messages
+
+If "rsyslog" is not logging messages for the cron facility or all facilities, this is a finding.  
+
+If the entry is in the "/etc/rsyslog.conf" file but is after the entry "*.*", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72053">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86677r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-021110</version>
+      <title>If the cron.allow file exists it must be owned by root.</title>
+      <description>&lt;VulnDiscussion&gt;If the owner of the "cron.allow" file is not set to root, the possibility exists for an unauthorized user to view or to edit sensitive 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78405r1_fix">Set the owner on the "/etc/cron.allow" file to root with the following command:
+
+# chown root /etc/cron.allow</fixtext>
+      <fix id="F-78405r1_fix"/>
+      <check system="C-72285r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that the "cron.allow" file is owned by root.
+
+Check the owner of the "cron.allow" file with the following command:
+
+# l s -al /etc/cron.allow
+-rw------- 1 root root 6 Mar  5  2011 /etc/cron.allow
+
+If the "cron.allow" file exists and has an owner other than root, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72055">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86679r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-021120</version>
+      <title>If the cron.allow file exists it must be group-owned by root.</title>
+      <description>&lt;VulnDiscussion&gt;If the group owner of the "cron.allow" file is not set to root, sensitive information could be viewed or edited by unauthorized users.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78407r1_fix">Set the group owner on the "/etc/cron.allow" file to root with the following command:
+
+# chgrp root /etc/cron.allow</fixtext>
+      <fix id="F-78407r1_fix"/>
+      <check system="C-72287r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that the "cron.allow" file is group-owned by root.
+
+Check the group owner of the "cron.allow" file with the following command:
+
+# ls -al /etc/cron.allow
+-rw------- 1 root root 6 Mar  5  2011 /etc/cron.allow
+
+If the "cron.allow" file exists and has a group owner other than root, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72057">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86681r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-021300</version>
+      <title>Kernel core dumps must be disabled unless needed.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78409r1_fix">If kernel core dumps are not required, disable the "kdump" service with the following command:
+
+# systemctl disable kdump.service
+
+If kernel core dumps are required, document the need with the ISSO.</fixtext>
+      <fix id="F-78409r1_fix"/>
+      <check system="C-72289r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that kernel core dumps are disabled unless needed.
+
+Check the status of the "kdump" service with the following command:
+
+# systemctl status kdump.service
+kdump.service - Crash recovery kernel arming
+   Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled)
+   Active: active (exited) since Wed 2015-08-26 13:08:09 EDT; 43min ago
+ Main PID: 1130 (code=exited, status=0/SUCCESS)
+kernel arming.
+
+If the "kdump" service is active, ask the System Administrator 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-72059">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86683r1_rule" severity="low" weight="10.0">
+      <version>RHEL-07-021310</version>
+      <title>A separate file system must be used for user home directories (such as /home or an equivalent).</title>
+      <description>&lt;VulnDiscussion&gt;The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78411r1_fix">Migrate the "/home" directory onto a separate file system/partition.</fixtext>
+      <fix id="F-78411r1_fix"/>
+      <check system="C-72291r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that a separate file system/partition has been created for non-privileged local interactive user home directories.
+
+Check the home directory assignment for all non-privileged users (those with a UID greater than 1000) on the system with the following command:
+
+#cut -d: -f 1,3,6,7 /etc/passwd | egrep ":[1-4][0-9]{3}" | tr ":" "\t"
+
+adamsj /home/adamsj /bin/bash
+jacksonm /home/jacksonm /bin/bash
+smithj /home/smithj /bin/bash
+
+The output of the command will give the directory/partition that contains the home directories for the non-privileged users on the system (in this example, /home) and users’ shell. All accounts with a valid shell (such as /bin/bash) are considered interactive users.
+
+Check that a file system/partition has been created for the non-privileged interactive users with the following command:
+
+Note: The partition of /home is used in the example.
+
+# grep /home /etc/fstab
+UUID=333ada18    /home                   ext4    noatime,nobarrier,nodev  1 2
+
+If a separate entry for the file system/partition that contains the non-privileged interactive users' home directories does not exist, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72061">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86685r1_rule" severity="low" weight="10.0">
+      <version>RHEL-07-021320</version>
+      <title>The system must use a separate file system for /var.</title>
+      <description>&lt;VulnDiscussion&gt;The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78413r1_fix">Migrate the "/var" path onto a separate file system.</fixtext>
+      <fix id="F-78413r1_fix"/>
+      <check system="C-72293r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that a separate file system/partition has been created for "/var".
+
+Check that a file system/partition has been created for "/var" with the following command:
+
+# grep /var /etc/fstab
+UUID=c274f65f    /var                    ext4    noatime,nobarrier        1 2
+
+If a separate entry for "/var" is not in use, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72063">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86687r3_rule" severity="low" weight="10.0">
+      <version>RHEL-07-021330</version>
+      <title>The system must use a separate file system for the system audit data path.</title>
+      <description>&lt;VulnDiscussion&gt;The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78415r1_fix">Migrate the system audit data path onto a separate file system.</fixtext>
+      <fix id="F-78415r1_fix"/>
+      <check system="C-72295r7_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the file integrity tool is configured to use FIPS 140-2 approved cryptographic hashes for validating file contents and directories.
+
+Note: If RHEL-07-021350 is a finding, this is automatically a finding as the system cannot implement FIPS 140-2 approved cryptographic algorithms and hashes.
+
+Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command:
+
+# yum list installed aide
+
+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 file integrity checks, this is a finding.
+
+Note: AIDE is highly configurable at install time. These commands assume the "aide.conf" file is under the "/etc" directory. 
+
+Use the following command to determine if the file is in another location:
+
+# find / -name aide.conf
+
+Check the "aide.conf" file to determine if the "sha512" rule has been added to the rule list being applied to the files and directories selection lists.
+
+An example rule that includes the "sha512" rule follows:
+
+All=p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux
+/bin All            # apply the custom rule to the files in bin 
+/sbin All          # apply the same custom rule to the files in sbin 
+
+If the "sha512" rule is not being used on all selection lines in the "/etc/aide.conf" file, or another file integrity tool is not using FIPS 140-2 approved cryptographic hashes for validating file contents and directories, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72065">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86689r1_rule" severity="low" weight="10.0">
+      <version>RHEL-07-021340</version>
+      <title>The system must use a separate file system for /tmp (or equivalent).</title>
+      <description>&lt;VulnDiscussion&gt;The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78417r1_fix">Start the "tmp.mount" service with the following command:
+
+# systemctl enable tmp.mount</fixtext>
+      <fix id="F-78417r1_fix"/>
+      <check system="C-72297r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that a separate file system/partition has been created for "/tmp".
+
+Check that a file system/partition has been created for "/tmp" with the following command:
+
+# systemctl is-enabled tmp.mount
+enabled
+
+If the "tmp.mount" service is not enabled, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72067">
+    <title>SRG-OS-000033-GPOS-00014</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86691r2_rule" severity="high" weight="10.0">
+      <version>RHEL-07-021350</version>
+      <title>The operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections 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 using 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-000033-GPOS-00014, SRG-OS-000185-GPOS-00079, SRG-OS-000396-GPOS-00176, SRG-OS-000405-GPOS-00184, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000068</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001199</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002450</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002476</ident>
+      <fixtext fixref="F-78419r1_fix">Configure the operating system to implement DoD-approved encryption by installing the dracut-fips package.
+
+To enable strict FIPS compliance, the fips=1 kernel option needs to be added to the kernel command line during system installation so key generation is done with FIPS-approved algorithms and continuous monitoring tests in place.
+
+Configure the operating system to implement DoD-approved encryption by following the steps below: 
+
+The fips=1 kernel option needs to be added to the kernel command line during system installation so that key generation is done with FIPS-approved algorithms and continuous monitoring tests in place. Users should also ensure that the system has plenty of entropy during the installation process by moving the mouse around, or if no mouse is available, ensuring that many keystrokes are typed. The recommended amount of keystrokes is 256 and more. Less than 256 keystrokes may generate a non-unique key.
+
+For proper operation of the in-module integrity verification, the prelink has to be disabled. This can be done by configuring PRELINKING=no in the "/etc/sysconfig/prelink" configuration file. Existing prelinking, if any, should be undone on all system files using the prelink -u -a command.
+
+Install the dracut-fips package with the following command:
+
+# yum install dracut-fips
+
+Recreate the "initramfs" file with the following command:
+
+Note: This command will overwrite the existing "initramfs" file.
+
+# dracut -f
+
+Modify the kernel command line of the current kernel in the "grub.cfg" file by adding the following option to the GRUB_CMDLINE_LINUX key in the "/etc/default/grub" file and then rebuild the "grub.cfg" file:
+
+fips=1
+
+Changes to "/etc/default/grub" require rebuilding the "grub.cfg" file as follows:
+
+On BIOS-based machines, use the following command:
+
+# grub2-mkconfig -o /boot/grub2/grub.cfg
+
+On UEFI-based machines, use the following command:
+
+# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
+
+If /boot or /boot/efi reside on separate partitions, the kernel parameter boot=&lt;partition of /boot or /boot/efi&gt; must be added to the kernel command line. You can identify a partition by running the df /boot or df /boot/efi command:
+
+# df /boot
+Filesystem           1K-blocks      Used Available Use% Mounted on
+/dev/sda1               495844     53780    416464  12% /boot
+
+To ensure the boot= configuration option will work even if device naming changes between boots, identify the universally unique identifier (UUID) of the partition with the following command:
+
+# blkid /dev/sda1
+/dev/sda1: UUID="05c000f1-a213-759e-c7a2-f11b7424c797" TYPE="ext4"
+
+For the example above, append the following string to the kernel command line:
+
+boot=UUID=05c000f1-a213-759e-c7a2-f11b7424c797
+
+Reboot the system for the changes to take effect.</fixtext>
+      <fix id="F-78419r1_fix"/>
+      <check system="C-72299r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system implements DoD-approved encryption to protect the confidentiality of remote access sessions.
+
+Check to see if the "dracut-fips" package is installed with the following command:
+
+# yum list installed | grep dracut-fips
+
+dracut-fips-033-360.el7_2.x86_64.rpm
+
+If a "dracut-fips" package is installed, check to see if the kernel command line is configured to use FIPS mode with the following command:
+
+Note: GRUB 2 reads its configuration from the "/boot/grub2/grub.cfg" file on traditional BIOS-based machines and from the "/boot/efi/EFI/redhat/grub.cfg" file on UEFI machines.
+
+# grep fips /boot/grub2/grub.cfg
+/vmlinuz-3.8.0-0.40.el7.x86_64 root=/dev/mapper/rhel-root ro rd.md=0 rd.dm=0 rd.lvm.lv=rhel/swap crashkernel=auto rd.luks=0 vconsole.keymap=us rd.lvm.lv=rhel/root rhgb fips=1 quiet
+
+If the kernel command line is configured to use FIPS mode, check to see if the system is in FIPS mode with the following command:
+
+# cat /proc/sys/crypto/fips_enabled 
+1
+
+If a "dracut-fips" package is not installed, the kernel command line does not have a fips entry, or the system has a value of "0" for "fips_enabled" in "/proc/sys/crypto", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72069">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86693r2_rule" severity="low" weight="10.0">
+      <version>RHEL-07-021600</version>
+      <title>The file integrity tool must be configured to verify Access Control Lists (ACLs).</title>
+      <description>&lt;VulnDiscussion&gt;ACLs can provide permissions beyond those permitted through the file mode and must be verified by file integrity tools.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78421r1_fix">Configure the file integrity tool to check file and directory ACLs. 
+
+If AIDE is installed, ensure the "acl" rule is present on all file and directory selection lists.</fixtext>
+      <fix id="F-78421r1_fix"/>
+      <check system="C-72301r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the file integrity tool is configured to verify ACLs.
+
+Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command:
+
+# yum list installed aide
+
+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 file integrity checks, this is a finding.
+
+Note: AIDE is highly configurable at install time. These commands assume the "aide.conf" file is under the "/etc" directory. 
+
+Use the following command to determine if the file is in another location:
+
+# find / -name aide.conf
+
+Check the "aide.conf" file to determine if the "acl" rule has been added to the rule list being applied to the files and directories selection lists.
+
+An example rule that includes the "acl" rule is below:
+
+All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux
+/bin All            # apply the custom rule to the files in bin 
+/sbin All          # apply the same custom rule to the files in sbin 
+
+If the "acl" rule is not being used on all selection lines in the "/etc/aide.conf" file, or ACLs are not being checked by another file integrity tool, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72071">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86695r2_rule" severity="low" weight="10.0">
+      <version>RHEL-07-021610</version>
+      <title>The file integrity tool must be configured to verify extended attributes.</title>
+      <description>&lt;VulnDiscussion&gt;Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78423r1_fix">Configure the file integrity tool to check file and directory extended attributes. 
+
+If AIDE is installed, ensure the "xattrs" rule is present on all file and directory selection lists.</fixtext>
+      <fix id="F-78423r1_fix"/>
+      <check system="C-72303r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the file integrity tool is configured to verify extended attributes.
+
+Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command:
+
+# yum list installed aide
+
+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 file integrity checks, this is a finding.
+
+Note: AIDE is highly configurable at install time. These commands assume the "aide.conf" file is under the "/etc" directory.  
+
+Use the following command to determine if the file is in another location:
+
+# find / -name aide.conf
+
+Check the "aide.conf" file to determine if the "xattrs" rule has been added to the rule list being applied to the files and directories selection lists.
+
+An example rule that includes the "xattrs" rule follows:
+
+All= p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux
+/bin All            # apply the custom rule to the files in bin 
+/sbin All          # apply the same custom rule to the files in sbin 
+
+If the "xattrs" rule is not being used on all selection lines in the "/etc/aide.conf" file, or extended attributes are not being checked by another file integrity tool, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72073">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86697r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-021620</version>
+      <title>The file integrity tool must use FIPS 140-2 approved cryptographic hashes for validating file contents and directories.</title>
+      <description>&lt;VulnDiscussion&gt;File integrity tools use cryptographic hashes for verifying file contents and directories have not been altered. These hashes must be FIPS 140-2 approved cryptographic hashes.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78425r1_fix">Configure the file integrity tool to use FIPS 140-2 cryptographic hashes for validating file and directory contents. 
+
+If AIDE is installed, ensure the "sha512" rule is present on all file and directory selection lists.</fixtext>
+      <fix id="F-78425r1_fix"/>
+      <check system="C-72305r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the file integrity tool is configured to use FIPS 140-2 approved cryptographic hashes for validating file contents and directories.
+
+Note: If RHEL-07-021350 is a finding, this is automatically a finding as the system cannot implement FIPS 140-2 approved cryptographic algorithms and hashes.
+
+Check to see if Advanced Intrusion Detection Environment (AIDE) is installed on the system with the following command:
+
+# yum list installed aide
+
+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 file integrity checks, this is a finding.
+
+Note: AIDE is highly configurable at install time. These commands assume the "aide.conf" file is under the "/etc" directory. 
+
+Use the following command to determine if the file is in another location:
+
+# find / -name aide.conf
+
+Check the "aide.conf" file to determine if the "sha512" rule has been added to the rule list being applied to the files and directories selection lists.
+
+An example rule that includes the "sha512" rule follows:
+
+All=p+i+n+u+g+s+m+S+sha512+acl+xattrs+selinux
+/bin All            # apply the custom rule to the files in bin 
+/sbin All          # apply the same custom rule to the files in sbin 
+
+If the "sha512" rule is not being used on all selection lines in the "/etc/aide.conf" file, or another file integrity tool is not using FIPS 140-2 approved cryptographic hashes for validating file contents and directories, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72075">
+    <title>SRG-OS-000364-GPOS-00151</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86699r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-021700</version>
+      <title>The system must not allow removable media to be used as the boot loader unless approved.</title>
+      <description>&lt;VulnDiscussion&gt;Malicious users with removable boot media can gain access to a system configured to use removable media as the boot loader. If removable media is designed to be used as the boot loader, the requirement must be documented with the Information System Security Officer (ISSO).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
+      <fixtext fixref="F-78427r1_fix">Remove alternate methods of booting the system from removable media or document the configuration to boot from removable media with the ISSO.</fixtext>
+      <fix id="F-78427r1_fix"/>
+      <check system="C-72307r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system is not configured to use a boot loader on removable media.
+
+Note: GRUB 2 reads its configuration from the "/boot/grub2/grub.cfg" file on traditional BIOS-based machines and from the "/boot/efi/EFI/redhat/grub.cfg" file on UEFI machines.
+
+Check for the existence of alternate boot loader configuration files with the following command:
+
+# find / -name grub.cfg
+/boot/grub2/grub.cfg
+
+If a "grub.cfg" is found in any subdirectories other than "/boot/grub2" and "/boot/efi/EFI/redhat", ask the System Administrator if there is documentation signed by the ISSO to approve the use of removable media as a boot loader. 
+
+Check that the grub configuration file has the set root command in each menu entry with the following commands:
+
+# grep -c menuentry /boot/grub2/grub.cfg
+1
+# grep ‘set root’ /boot/grub2/grub.cfg
+set root=(hd0,1)
+
+If the system is using an alternate boot loader on removable media, and documentation does not exist approving the alternate configuration, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72077">
+    <title>SRG-OS-000095-GPOS-00049</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86701r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-021710</version>
+      <title>The telnet-server package must not be 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.
+
+Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).
+
+Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000381</ident>
+      <fixtext fixref="F-78429r1_fix">Configure the operating system to disable non-essential capabilities by removing the telnet-server package from the system with the following command:
+
+# yum remove telnet-server</fixtext>
+      <fix id="F-78429r1_fix"/>
+      <check system="C-72309r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system is configured to disable non-essential capabilities. The most secure way of ensuring a non-essential capability is disabled is to not have the capability installed.
+
+The telnet service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session.
+
+If a privileged user were to log on using this service, the privileged user password could be compromised. 
+
+Check to see if the telnet-server package is installed with the following command:
+
+# yum list installed | grep telnet-server
+
+If the telnet-server package is installed, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72079">
+    <title>SRG-OS-000038-GPOS-00016</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86703r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-030000</version>
+      <title>Auditing must be configured to produce records containing information to establish what type of events occurred, where the events occurred, the source of the events, and the outcome of the events.
+
+These audit records must also identify individual identities of group account users.</title>
+      <description>&lt;VulnDiscussion&gt;Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
+
+Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.
+
+Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.
+
+Satisfies: SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000042-GPOS-00021, SRG-OS-000254-GPOS-00095, SRG-OS-000255-GPOS-00096&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000131</ident>
+      <fixtext fixref="F-78431r1_fix">Configure the operating system to produce audit records containing information to establish when (date and time) the events occurred.
+
+Enable the auditd service with the following command:
+
+# chkconfig auditd on</fixtext>
+      <fix id="F-78431r1_fix"/>
+      <check system="C-72311r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system produces audit records containing information to establish when (date and time) the events occurred.
+
+Check to see if auditing is active by issuing the following command:
+
+# systemctl is-active auditd.service
+Active: active (running) since Tue 2015-01-27 19:41:23 EST; 22h ago
+
+If the "auditd" status is not active, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72081">
+    <title>SRG-OS-000046-GPOS-00022</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86705r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030010</version>
+      <title>The operating system must shut down upon audit processing failure, unless availability is an overriding concern. If availability is a concern, the system must alert the designated staff (System Administrator [SA] and Information System Security Officer [ISSO] at a minimum) 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.
+
+Satisfies: SRG-OS-000046-GPOS-00022, SRG-OS-000047-GPOS-00023&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000139</ident>
+      <fixtext fixref="F-78433r1_fix">Configure the operating system to shut down in the event of an audit processing failure.
+
+Add or correct the option to shut down the operating system with the following command:
+
+# auditctl -f 2
+
+If availability has been determined to be more important, and this decision is documented with the ISSO, configure the operating system to notify system administration staff and ISSO staff in the event of an audit processing failure with the following command:
+
+# auditctl -f 1
+
+Kernel log monitoring must also be configured to properly alert designated staff.
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78433r1_fix"/>
+      <check system="C-72313r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Confirm the audit configuration regarding how auditing processing failures are handled.
+
+Check to see what level "auditctl" is set to with following command: 
+
+# auditctl -l | grep /-f
+ -f 2
+
+If the value of "-f" is set to "2", the system is configured to panic (shut down) in the event of an auditing failure.
+
+If the value of "-f" is set to "1", the system is configured to only send information to the kernel log regarding the failure.
+
+If the "-f" flag is not set, this is a CAT I finding.
+
+If the "-f" flag is set to any value other than "1" or "2", this is a CAT II finding.
+
+If the "-f" flag is set to "1" but the availability concern is not documented or there is no monitoring of the kernel log, this is a CAT III finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72083">
+    <title>SRG-OS-000342-GPOS-00133</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86707r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030300</version>
+      <title>The operating system must off-load audit records onto a different system or media from the system being audited.</title>
+      <description>&lt;VulnDiscussion&gt;Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
+
+Off-loading is a common process in information systems with limited audit storage capacity.
+
+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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001851</ident>
+      <fixtext fixref="F-78435r1_fix">Configure the operating system to off-load audit records onto a different system or media from the system being audited.
+
+Set the remote server option in "/etc/audisp/audisp-remote.conf" with the IP address of the log aggregation server.</fixtext>
+      <fix id="F-78435r1_fix"/>
+      <check system="C-72315r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system off-loads audit records onto a different system or media from the system being audited.
+
+To determine the remote server that the records are being sent to, use the following command:
+
+# grep -i remote_server /etc/audisp/audisp-remote.conf
+remote_server = 10.0.21.1
+
+If a remote server is not configured, or the line is commented out, ask the System Administrator to indicate how the audit logs are off-loaded to a different system or media. 
+
+If there is no evidence that the audit logs are being off-loaded to another system or media, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72085">
+    <title>SRG-OS-000342-GPOS-00133</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86709r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030310</version>
+      <title>The operating system must encrypt the transfer of audit records off-loaded onto a different system or media from the system being audited.</title>
+      <description>&lt;VulnDiscussion&gt;Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
+
+Off-loading is a common process in information systems with limited audit storage capacity.
+
+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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001851</ident>
+      <fixtext fixref="F-78437r1_fix">Configure the operating system to encrypt the transfer of off-loaded audit records onto a different system or media from the system being audited.
+
+Uncomment the "enable_krb5" option in "/etc/audisp/audisp-remote.conf" and set it with the following line:
+
+enable_krb5 = yes</fixtext>
+      <fix id="F-78437r1_fix"/>
+      <check system="C-72317r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system encrypts audit records off-loaded onto a different system or media from the system being audited.
+
+To determine if the transfer is encrypted, use the following command:
+
+# grep -i enable_krb5 /etc/audisp/audisp-remote.conf
+enable_krb5 = yes
+
+If the value of the "enable_krb5" option is not set to "yes" or the line is commented out, ask the System Administrator to indicate how the audit logs are off-loaded to a different system or media. 
+
+If there is no evidence that the transfer of the audit logs being off-loaded to another system or media is encrypted, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72087">
+    <title>SRG-OS-000342-GPOS-00133</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86711r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030320</version>
+      <title>The audit system must take appropriate action when the audit storage volume is full.</title>
+      <description>&lt;VulnDiscussion&gt;Taking appropriate action in case of a filled audit storage volume will minimize the possibility of losing audit records.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001851</ident>
+      <fixtext fixref="F-78439r3_fix">Configure the action the operating system takes if the disk the audit records are written to becomes full.
+
+Uncomment or edit the "disk_full_action" option in "/etc/audisp/audisp-remote.conf" and set it to "syslog", "single", or "halt", such as the following line:
+
+disk_full_action = single
+
+Uncomment the "network_failure_action" option in "/etc/audisp/audisp-remote.conf" and set it to "syslog", "single", or "halt".</fixtext>
+      <fix id="F-78439r3_fix"/>
+      <check system="C-72319r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the action the operating system takes if the disk the audit records are written to becomes full.
+
+To determine the action that takes place if the disk is full on the remote server, use the following command:
+
+# grep -i disk_full_action /etc/audisp/audisp-remote.conf
+disk_full_action = single
+
+To determine the action that takes place if the network connection fails, use the following command:
+
+# grep -i network_failure_action /etc/audisp/audisp-remote.conf
+network_failure_action = stop
+
+If the value of the "network_failure_action" option is not "syslog", "single", or "halt", or the line is commented out, this is a finding.
+
+If the value of the "disk_full_action" option is not "syslog", "single", or "halt", or the line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72089">
+    <title>SRG-OS-000343-GPOS-00134</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86713r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030330</version>
+      <title>The operating system must immediately notify the System Administrator (SA) and Information System Security Officer ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity.</title>
+      <description>&lt;VulnDiscussion&gt;If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storage capacity expansion.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001855</ident>
+      <fixtext fixref="F-78441r1_fix">Configure the operating system to immediately notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.
+
+Check the system configuration to determine the partition the audit records are being written to: 
+
+# grep log_file /etc/audit/auditd.conf
+
+Determine the size of the partition that audit records are written to (with the example being "/var/log/audit/"):
+
+# df -h /var/log/audit/
+
+Set the value of the "space_left" keyword in "/etc/audit/auditd.conf" to 75 percent of the partition size.</fixtext>
+      <fix id="F-78441r1_fix"/>
+      <check system="C-72321r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system immediately notifies the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.
+
+Check the system configuration to determine the partition the audit records are being written to with the following command:
+
+# grep log_file /etc/audit/auditd.conf
+log_file = /var/log/audit/audit.log
+
+Check the size of the partition that audit records are written to (with the example being "/var/log/audit/"):
+
+# df -h /var/log/audit/
+0.9G /var/log/audit
+
+If the audit records are not being written to a partition specifically created for audit records (in this example "/var/log/audit" is a separate partition), determine the amount of space other files in the partition are currently occupying with the following command:
+
+# du -sh &lt;partition&gt;
+1.8G /var
+
+Determine what the threshold is for the system to take action when 75 percent of the repository maximum audit record storage capacity is reached:
+
+# grep -i space_left /etc/audit/auditd.conf
+space_left = 225 
+
+If the value of the "space_left" keyword is not set to 25 percent of the total partition size, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72091">
+    <title>SRG-OS-000343-GPOS-00134</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86715r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030340</version>
+      <title>The operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) via email when the threshold for the repository maximum audit record storage capacity is reached.</title>
+      <description>&lt;VulnDiscussion&gt;If security personnel are not notified immediately when the threshold for the repository maximum audit record storage capacity is reached, they are unable to expand the audit record storage capacity before records are lost.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001855</ident>
+      <fixtext fixref="F-78443r1_fix">Configure the operating system to immediately notify the SA and ISSO (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached.
+
+Uncomment or edit the "space_left_action" keyword in "/etc/audit/auditd.conf" and set it to "email". 
+ 
+space_left_action = email</fixtext>
+      <fix id="F-78443r1_fix"/>
+      <check system="C-72323r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system immediately notifies the SA and ISSO (at a minimum) via email when the allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.
+
+Check what action the operating system takes when the threshold for the repository maximum audit record storage capacity is reached with the following command:
+
+# grep -i space_left_action  /etc/audit/auditd.conf
+space_left_action = email
+
+If the value of the "space_left_action" keyword is not set to "email", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72093">
+    <title>SRG-OS-000343-GPOS-00134</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86717r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030350</version>
+      <title>The operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached.</title>
+      <description>&lt;VulnDiscussion&gt;If security personnel are not notified immediately when the threshold for the repository maximum audit record storage capacity is reached, they are unable to expand the audit record storage capacity before records are lost.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001855</ident>
+      <fixtext fixref="F-78445r3_fix">Configure the operating system to immediately notify the SA and ISSO (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached.
+
+Uncomment or edit the "action_mail_acct" keyword in "/etc/audit/auditd.conf" and set it to root and any other accounts associated with security personnel. 
+ 
+action_mail_acct = root</fixtext>
+      <fix id="F-78445r3_fix"/>
+      <check system="C-72325r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system immediately notifies the SA and ISSO (at a minimum) via email when the threshold for the repository maximum audit record storage capacity is reached.
+
+Check what account the operating system emails when the threshold for the repository maximum audit record storage capacity is reached with the following command:
+
+# grep -i action_mail_acct  /etc/audit/auditd.conf
+action_mail_acct = root
+
+If the value of the "action_mail_acct" keyword is not set to "root" and other accounts for security personnel, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72095">
+    <title>SRG-OS-000327-GPOS-00127</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86719r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030360</version>
+      <title>All privileged function executions must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002234</ident>
+      <fixtext fixref="F-78447r4_fix">Configure the operating system to audit the execution of privileged functions.
+
+To find the relevant "setuid"/"setgid" programs, run the following command for each local partition [PART]:
+
+# find [PART] -xdev -type f \( -perm -4000 -o -perm -2000 \) 2&gt;/dev/null
+
+For each "setuid"/"setgid" program on the system, which is not covered by an audit rule for a (sub) directory (such as "/usr/sbin"), add a line of the following form to "/etc/audit/audit.rules", where &lt;suid_prog_with_full_path&gt; is the full path to each "setuid"/"setgid" program in the list:
+
+-a always,exit -F &lt;suid_prog_with_full_path&gt; -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k setuid/setgid</fixtext>
+      <fix id="F-78447r4_fix"/>
+      <check system="C-72327r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system audits the execution of privileged functions.
+
+To find relevant setuid and setgid programs, use the following command once for each local partition [PART]:
+
+# find [PART] -xdev -type f \( -perm -4000 -o -perm -2000 \) 2&gt;/dev/null
+
+Run the following command to verify entries in the audit rules for all programs found with the previous command:
+
+# grep &lt;suid_prog_with_full_path&gt; -a always,exit -F &lt;suid_prog_with_full_path&gt; -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k setuid/setgid
+
+All "setuid" and "setgid" files on the system must have a corresponding audit rule, or must have an audit rule for the (sub) directory that contains the "setuid"/"setgid" file.
+
+If all "setuid"/"setgid" files on the system do not have audit rule coverage, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72097">
+    <title>SRG-OS-000064-GPOS-00033</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86721r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030370</version>
+      <title>All uses of the chown command must be audited.</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).
+
+Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78449r5_fix">Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S chown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S chown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78449r5_fix"/>
+      <check system="C-72329r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "chown" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i chown /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S chown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S chown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72099">
+    <title>SRG-OS-000064-GPOS-00033</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86723r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030380</version>
+      <title>All uses of the fchown command must be audited.</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).
+
+Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78451r5_fix">Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S fchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S fchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78451r5_fix"/>
+      <check system="C-72331r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "fchown" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i fchown /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S fchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S fchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72101">
+    <title>SRG-OS-000064-GPOS-00033</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86725r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030390</version>
+      <title>All uses of the lchown command must be audited.</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).
+
+Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78453r5_fix">Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78453r5_fix"/>
+      <check system="C-72333r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "lchown" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i lchown /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72103">
+    <title>SRG-OS-000064-GPOS-00033</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86727r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030400</version>
+      <title>All uses of the fchownat command must be audited.</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).
+
+Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000392-GPOS-00172, SRG-OS-000458-GPOS-00203, SRG-OS-000474-GPOS-00219&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78455r4_fix">Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S fchownat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S fchownat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78455r4_fix"/>
+      <check system="C-72335r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "fchownat" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i fchownat /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S fchownat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S fchownat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72105">
+    <title>SRG-OS-000458-GPOS-00203</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86729r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030410</version>
+      <title>All uses of the chmod command must be audited.</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).
+
+Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78457r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "chmod" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S chmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S chmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78457r4_fix"/>
+      <check system="C-72337r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "chmod" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following command:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i chmod /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S chmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S chmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72107">
+    <title>SRG-OS-000458-GPOS-00203</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86731r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030420</version>
+      <title>All uses of the fchmod command must be audited.</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).
+
+Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78459r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "fchmod" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S fchmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S fchmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78459r4_fix"/>
+      <check system="C-72339r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "fchmod" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following command:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i fchmod /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S fchmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S fchmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72109">
+    <title>SRG-OS-000458-GPOS-00203</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86733r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030430</version>
+      <title>All uses of the fchmodat command must be audited.</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).
+
+Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78461r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "fchmodat" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78461r4_fix"/>
+      <check system="C-72341r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "fchmodat" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following command:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i fchmodat /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72111">
+    <title>SRG-OS-000458-GPOS-00203</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86735r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030440</version>
+      <title>All uses of the setxattr command must be audited.</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).
+
+Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78463r5_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "setxattr" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S setxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S setxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78463r5_fix"/>
+      <check system="C-72343r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "setxattr" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i setxattr /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S setxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S setxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72113">
+    <title>SRG-OS-000458-GPOS-00203</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86737r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030450</version>
+      <title>All uses of the fsetxattr command must be audited.</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).
+
+Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78465r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "fsetxattr" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S fsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S fsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78465r4_fix"/>
+      <check system="C-72345r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "fsetxattr" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i fsetxattr /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S fsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S fsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72115">
+    <title>SRG-OS-000458-GPOS-00203</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86739r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030460</version>
+      <title>All uses of the lsetxattr command must be audited.</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).
+
+Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78467r6_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "lsetxattr" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S lsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S lsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78467r6_fix"/>
+      <check system="C-72347r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "lsetxattr" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i lsetxattr /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S lsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S lsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72117">
+    <title>SRG-OS-000458-GPOS-00203</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86741r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030470</version>
+      <title>All uses of the removexattr command must be audited.</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).
+
+Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78469r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "removexattr" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S removexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S removexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78469r4_fix"/>
+      <check system="C-72349r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "removexattr" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i removexattr /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S removexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S removexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72119">
+    <title>SRG-OS-000458-GPOS-00203</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86743r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030480</version>
+      <title>All uses of the fremovexattr command must be audited.</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).
+
+Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78471r3_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "fremovexattr" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78471r3_fix"/>
+      <check system="C-72351r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "fremovexattr" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i fremovexattr /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72121">
+    <title>SRG-OS-000458-GPOS-00203</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86745r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030490</version>
+      <title>All uses of the lremovexattr command must be audited.</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).
+
+Satisfies: SRG-OS-000458-GPOS-00203, SRG-OS-000392-GPOS-00172, SRG-OS-000064-GPOS-00033&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78473r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "lremovexattr" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S lremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S lremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78473r4_fix"/>
+      <check system="C-72353r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "lremovexattr" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i lremovexattr /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S lremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+-a always,exit -F arch=b64 -S lremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72123">
+    <title>SRG-OS-000064-GPOS-00033</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86747r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030500</version>
+      <title>All uses of the creat command must be audited.</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).
+
+Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78475r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "creat" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+-a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78475r4_fix"/>
+      <check system="C-72355r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "creat" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i creat /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S creat  -Fexit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+-a always,exit -F arch=b64 -S creat  -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72125">
+    <title>SRG-OS-000064-GPOS-00033</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86749r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030510</version>
+      <title>All uses of the open command must be audited.</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).
+
+Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78477r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "open" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78477r4_fix"/>
+      <check system="C-72357r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "open" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i open /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S open -Fexit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72127">
+    <title>SRG-OS-000064-GPOS-00033</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86751r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030520</version>
+      <title>All uses of the openat command must be audited.</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).
+
+Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78479r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "openat" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78479r4_fix"/>
+      <check system="C-72359r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "openat" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i openat /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S openat -Fexit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72129">
+    <title>SRG-OS-000064-GPOS-00033</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86753r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030530</version>
+      <title>All uses of the open_by_handle_at command must be audited.</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).
+
+Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78481r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "open_by_handle_at" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78481r4_fix"/>
+      <check system="C-72361r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "open_by_handle_at" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i open_by_handle_at /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S open_by_handle_at -Fexit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72131">
+    <title>SRG-OS-000064-GPOS-00033</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86755r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030540</version>
+      <title>All uses of the truncate command must be audited.</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).
+
+Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78483r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "truncate" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78483r4_fix"/>
+      <check system="C-72363r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "truncate" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i truncate /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S truncate -Fexit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72133">
+    <title>SRG-OS-000064-GPOS-00033</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86757r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030550</version>
+      <title>All uses of the ftruncate command must be audited.</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).
+
+Satisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78485r5_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "ftruncate" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78485r5_fix"/>
+      <check system="C-72365r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "ftruncate" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i ftruncate /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S ftruncate -Fexit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+-a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72135">
+    <title>SRG-OS-000392-GPOS-00172</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86759r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030560</version>
+      <title>All uses of the semanage command must be audited.</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).
+
+Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78487r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "semanage" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78487r4_fix"/>
+      <check system="C-72367r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "semanage" command occur.
+
+Check the file system rule in "/etc/audit/audit.rules" with the following command:
+
+# grep -i /usr/sbin/semanage /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/sbin/semanage -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72137">
+    <title>SRG-OS-000392-GPOS-00172</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86761r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030570</version>
+      <title>All uses of the setsebool command must be audited.</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).
+
+Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78489r5_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "setsebool" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78489r5_fix"/>
+      <check system="C-72369r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "setsebool" command occur.
+
+Check the file system rule in "/etc/audit/audit.rules" with the following command:
+
+# grep -i /usr/sbin/setsebool /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/sbin/setsebool -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72139">
+    <title>SRG-OS-000392-GPOS-00172</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86763r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030580</version>
+      <title>All uses of the chcon command must be audited.</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).
+
+Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78491r5_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "chcon" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+
+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78491r5_fix"/>
+      <check system="C-72371r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "chcon" command occur.
+
+Check the file system rule in "/etc/audit/audit.rules" with the following command:
+
+# grep -i /usr/bin/chcon /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72141">
+    <title>SRG-OS-000392-GPOS-00172</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86765r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030590</version>
+      <title>All uses of the restorecon command must be audited.</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).
+
+Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000463-GPOS-00207, SRG-OS-000465-GPOS-00209&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78493r5_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "restorecon" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+
+-a always,exit -F path=/usr/sbin/restorecon -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k -F  privileged-priv_change
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78493r5_fix"/>
+      <check system="C-72373r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "restorecon" command occur.
+
+Check the file system rule in "/etc/audit/audit.rules" with the following command:
+
+# grep -i /usr/sbin/restorecon /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/sbin/restorecon -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72143">
+    <title>SRG-OS-000392-GPOS-00172</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86767r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030600</version>
+      <title>The operating system must generate audit records for all successful/unsuccessful account access count events.</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).
+
+Satisfies: SRG-OS-000392-GPOS-00172, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78495r4_fix">Configure the operating system to generate audit records when successful/unsuccessful account access count events occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-w /var/log/tallylog -p wa -k logins
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78495r4_fix"/>
+      <check system="C-72375r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful account access count events occur. 
+
+Check the file system rule in "/etc/audit/audit.rules" with the following commands: 
+
+# grep -i /var/log/tallylog /etc/audit/audit.rules
+
+-w /var/log/tallylog -p wa -k logins
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72145">
+    <title>SRG-OS-000392-GPOS-00172</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86769r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030610</version>
+      <title>The operating system must generate audit records for all unsuccessful account access events.</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).
+
+Satisfies: SRG-OS-000392-GPOS-00172, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78497r3_fix">Configure the operating system to generate audit records when unsuccessful account access events occur. 
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-w /var/run/faillock/ -p wa -k logins
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78497r3_fix"/>
+      <check system="C-72377r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when unsuccessful account access events occur. 
+
+Check the file system rule in "/etc/audit/audit.rules" with the following commands: 
+
+# grep -i /var/run/faillock /etc/audit/audit.rules
+
+-w /var/run/faillock -p wa -k logins
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72147">
+    <title>SRG-OS-000392-GPOS-00172</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86771r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030620</version>
+      <title>The operating system must generate audit records for all successful account access events.</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).
+
+Satisfies: SRG-OS-000392-GPOS-00172, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000126</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78499r3_fix">Configure the operating system to generate audit records when successful account access events occur. 
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-w /var/log/lastlog -p wa -k logins
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78499r3_fix"/>
+      <check system="C-72379r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful account access events occur. 
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands: 
+
+# grep -i /var/log/lastlog /etc/audit/audit.rules
+
+-w /var/log/lastlog -p wa -k logins 
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72149">
+    <title>SRG-OS-000042-GPOS-00020</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86773r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030630</version>
+      <title>All uses of the passwd command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000042-GPOS-00020, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78501r5_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "passwd" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-passwd
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78501r5_fix"/>
+      <check system="C-72381r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "passwd" command occur.
+
+Check the file system rule in "/etc/audit/audit.rules" with the following command:
+
+# grep -i /usr/bin/passwd /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-passwd
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72151">
+    <title>SRG-OS-000042-GPOS-00020</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86775r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030640</version>
+      <title>All uses of the unix_chkpwd command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000042-GPOS-00020, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78503r6_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "unix_chkpwd" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+
+-a always,exit -F path=/sbin/unix_chkpwd -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-passwd
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78503r6_fix"/>
+      <check system="C-72383r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "unix_chkpwd" command occur.
+
+Check the file system rule in "/etc/audit/audit.rules" with the following command:
+
+# grep -i /sbin/unix_chkpwd /etc/audit/audit.rules
+
+-a always,exit -F path=/sbin/unix_chkpwd -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-passwd
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72153">
+    <title>SRG-OS-000042-GPOS-00020</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86777r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030650</version>
+      <title>All uses of the gpasswd command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000042-GPOS-00020, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78505r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "gpasswd" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-passwd
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78505r4_fix"/>
+      <check system="C-72385r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "gpasswd" command occur.
+
+Check the file system rule in "/etc/audit/audit.rules" with the following command:
+
+# grep -i /usr/bin/gpasswd /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-passwd
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72155">
+    <title>SRG-OS-000042-GPOS-00020</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86779r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030660</version>
+      <title>All uses of the chage command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000042-GPOS-00020, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78507r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "chage" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+
+-a always,exit -F path=/usr/bin/chage -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-passwd
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78507r4_fix"/>
+      <check system="C-72387r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "chage" command occur.
+
+Check the file system rule in "/etc/audit/audit.rules" with the following command:
+
+# grep -i /usr/bin/chage /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/bin/chage -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-passwd
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72157">
+    <title>SRG-OS-000042-GPOS-00020</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86781r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030670</version>
+      <title>All uses of the userhelper command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged password commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000042-GPOS-00020, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78509r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "userhelper" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+
+-a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-passwd
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78509r4_fix"/>
+      <check system="C-72389r5_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "userhelper" command occur.
+
+Check the file system rule in "/etc/audit/audit.rules" with the following command:
+
+# grep -i /usr/sbin/userhelper /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/sbin/userhelper -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-passwd
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72159">
+    <title>SRG-OS-000037-GPOS-00015</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86783r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030680</version>
+      <title>All uses of the su command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000130</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78511r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "su" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-a always,exit -F path=/bin/su -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change 
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78511r4_fix"/>
+      <check system="C-72391r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "su" command occur.
+
+Check for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep -i /bin/su /etc/audit/audit.rules
+
+-a always,exit -F path=/bin/su -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72161">
+    <title>SRG-OS-000037-GPOS-00015</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86785r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030690</version>
+      <title>All uses of the sudo command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000130</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78513r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "sudo" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change 
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78513r4_fix"/>
+      <check system="C-72393r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "sudo" command occur.
+
+Check for the following system calls being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep -i /usr/bin/sudo /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72163">
+    <title>SRG-OS-000037-GPOS-00015</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86787r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030700</version>
+      <title>All uses of the sudoers command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000130</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78517r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "sudoer" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+
+-w /etc/sudoers -p wa -k privileged-actions
+
+-w /etc/sudoers.d -p wa -k privileged-actions
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78517r4_fix"/>
+      <check system="C-72397r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "sudoer" command occur.
+
+Check for modification of the following files being audited by performing the following commands to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep /etc/sudoers /etc/audit/audit.rules
+
+-w /etc/sudoers -p wa -k privileged-actions
+
+# grep /etc/sudoers.d /etc/audit/audit.rules
+
+-w /etc/sudoers.d -p wa -k privileged-actions
+
+If the commands do not return output that does not match the examples, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72165">
+    <title>SRG-OS-000037-GPOS-00015</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86789r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030710</version>
+      <title>All uses of the newgrp command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000130</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78519r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "newgrp" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78519r4_fix"/>
+      <check system="C-72399r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "newgrp" command occur.
+
+Check for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep -i /usr/bin/newgrp /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72167">
+    <title>SRG-OS-000037-GPOS-00015</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86791r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030720</version>
+      <title>All uses of the chsh command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000130</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78521r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "chsh" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78521r4_fix"/>
+      <check system="C-72401r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "chsh" command occur.
+
+Check for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep -i /usr/bin/chsh /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72169">
+    <title>SRG-OS-000037-GPOS-00015</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86793r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030730</version>
+      <title>All uses of the sudoedit command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000130</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78523r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "sudoedit" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-a always,exit -F path=/bin/sudoedit -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78523r4_fix"/>
+      <check system="C-72403r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "sudoedit" command occur.
+
+Check for the following system calls being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep -i /usr/bin/sudoedit /etc/audit/audit.rules
+
+-a always,exit -F path=/bin/sudoedit -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-priv_change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72171">
+    <title>SRG-OS-000042-GPOS-00020</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86795r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030740</version>
+      <title>All uses of the mount command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged mount commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78525r5_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "mount" command occur.
+
+Add or update the following rules in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S mount -F auid&gt;=1000 -F auid!=4294967295 -k privileged-mount
+
+-a always,exit -F arch=b64 -S mount -F auid&gt;=1000 -F auid!=4294967295 -k privileged-mount
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78525r5_fix"/>
+      <check system="C-72405r6_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "mount" command occur.
+
+Check for the following system calls being audited by performing the following series of commands to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep -i /bin/mount /etc/audit/audit.rules
+
+-a always,exit -F arch=b32 -S mount -F auid&gt;=1000 -F auid!=4294967295 -k privileged-mount
+
+-a always,exit -F arch=b64 -S mount -F auid&gt;=1000 -F auid!=4294967295 -k privileged-mount
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72173">
+    <title>SRG-OS-000042-GPOS-00020</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86797r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030750</version>
+      <title>All uses of the umount command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged mount commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78527r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "umount" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-a always,exit -F path=/bin/umount -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-mount
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78527r4_fix"/>
+      <check system="C-72407r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "umount" command occur.
+
+Check for the following system calls being audited by performing the following series of commands to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep -i /bin/umount /etc/audit/audit.rules
+
+-a always,exit -F path=/bin/umount -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-mount  
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72175">
+    <title>SRG-OS-000042-GPOS-00020</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86799r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030760</version>
+      <title>All uses of the postdrop command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged postfix commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78529r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "postdrop" command occur.
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-postfix
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78529r4_fix"/>
+      <check system="C-72409r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "postdrop" command occur.
+
+Check for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep -i /usr/sbin/postdrop /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/sbin/postdrop -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-postfix
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72177">
+    <title>SRG-OS-000042-GPOS-00020</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86801r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030770</version>
+      <title>All uses of the postqueue command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged postfix commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78531r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "postqueue" command occur. 
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-postfix
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78531r4_fix"/>
+      <check system="C-72411r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "postqueue" command occur. 
+
+Check for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep -i /usr/sbin/postqueue /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/sbin/postqueue -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-postfix
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72179">
+    <title>SRG-OS-000042-GPOS-00020</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86803r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030780</version>
+      <title>All uses of the ssh-keysign command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged ssh commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000042-GPOS-00020, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78533r3_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "ssh-keysign" command occur. 
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-ssh
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78533r3_fix"/>
+      <check system="C-72413r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "ssh-keysign" command occur. 
+
+Check for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep -i /usr/libexec/openssh/ssh-keysign /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/libexec/openssh/ssh-keysign -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-ssh
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72181">
+    <title>SRG-OS-000042-GPOS-00020</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86805r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030790</version>
+      <title>All uses of the pt_chown command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000042-GPOS-00020, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78535r3_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "pt_chown" command occur. 
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-a always,exit -F path=/usr/libexec/pt_chown -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged_terminal
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78535r3_fix"/>
+      <check system="C-72415r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "pt_chown" command occur. 
+
+Check for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep -i /usr/libexec/pt_chown /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/libexec/pt_chown -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged_terminal
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72183">
+    <title>SRG-OS-000042-GPOS-00020</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86807r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030800</version>
+      <title>All uses of the crontab command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
+
+At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
+
+Satisfies: SRG-OS-000042-GPOS-00020, 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000135</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78537r3_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "crontab" command occur. 
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-cron
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78537r3_fix"/>
+      <check system="C-72417r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "crontab" command occur. 
+
+Check for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": 
+
+# grep -i /usr/bin/crontab /etc/audit/audit.rules
+
+-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-cron
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72185">
+    <title>SRG-OS-000471-GPOS-00215</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86809r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030810</version>
+      <title>All uses of the pam_timestamp_check command must be audited.</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.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78539r3_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "pam_timestamp_check" command occur. 
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules": 
+
+-a always,exit -F path=/sbin/pam_timestamp_check -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged-pam
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78539r3_fix"/>
+      <check system="C-72419r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "pam_timestamp_check" command occur. 
+
+Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+
+# grep -i /sbin/pam_timestamp_check /etc/audit/audit.rules
+
+-a always,exit -F path=/sbin/pam_timestamp_check -F perm=x -F auid&gt;=1000 -F auid!=4294967295  -k privileged-pam  
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72187">
+    <title>SRG-OS-000471-GPOS-00216</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86811r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030820</version>
+      <title>All uses of the init_module command must be audited.</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).
+
+Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78541r4_fix">Configure the operating system generates audit records when successful/unsuccessful attempts to use the "init_module" command occur. 
+
+Add or update the following rules in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture): 
+
+-a always,exit -F arch=b32 -S init_module -k module-change
+
+-a always,exit -F arch=b64 -S init_module -k module-change
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78541r4_fix"/>
+      <check system="C-72421r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "init_module" command occur. 
+
+Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present.
+
+# grep -i init_module /etc/audit/audit.rules
+
+If the command does not return the following output (appropriate to the architecture), this is a finding. 
+
+-a always,exit -F arch=b32 -S init_module -k module-change
+
+-a always,exit -F arch=b64 -S init_module -k module-change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72189">
+    <title>SRG-OS-000471-GPOS-00216</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86813r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030830</version>
+      <title>All uses of the delete_module command must be audited.</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).
+
+Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78543r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "delete_module" command occur. 
+
+Add or update the following rules in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture): 
+
+-a always,exit -F arch=b32 -S delete_module -k module-change
+
+-a always,exit -F arch=b64 -S delete_module -k module-change
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78543r4_fix"/>
+      <check system="C-72423r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "delete_module" command occur. 
+
+Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present.
+
+# grep -i delete_module /etc/audit/audit.rules
+
+If the command does not return the following output (appropriate to the architecture), this is a finding. 
+
+-a always,exit -F arch=b32 -S delete_module -k module-change
+
+-a always,exit -F arch=b64 -S delete_module -k module-change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72191">
+    <title>SRG-OS-000471-GPOS-00216</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86815r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030840</version>
+      <title>All uses of the insmod command must be audited.</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).
+
+Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78545r5_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "insmod" command occur. 
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture): 
+
+-w /sbin/insmod -p x -F auid!=4294967295 -k module-change
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78545r5_fix"/>
+      <check system="C-72425r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "insmod" command occur. 
+
+Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+
+# grep -i insmod /etc/audit/audit.rules
+
+If the command does not return the following output (appropriate to the architecture), this is a finding. 
+
+-w /sbin/insmod -p x -F auid!=4294967295 -k module-change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72193">
+    <title>SRG-OS-000471-GPOS-00216</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86817r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030850</version>
+      <title>All uses of the rmmod command must be audited.</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).
+
+Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78547r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "rmmod" command occur. 
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture): 
+
+-w /sbin/rmmod-p x -F auid!=4294967295 -k module-change
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78547r4_fix"/>
+      <check system="C-72427r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "rmmod" command occur. 
+
+Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+
+# grep -i rmmod /etc/audit/audit.rules
+
+If the command does not return the following output (appropriate to the architecture), this is a finding. 
+
+-w /sbin/rmmod -p x -F auid!=4294967295 -k module-change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72195">
+    <title>SRG-OS-000471-GPOS-00216</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86819r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030860</version>
+      <title>All uses of the modprobe command must be audited.</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).
+
+Satisfies: SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <fixtext fixref="F-78549r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "modprobe" command occur. 
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture): 
+
+-w /sbin/modprobe -p x -F auid!=4294967295 -k module-change
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78549r4_fix"/>
+      <check system="C-72429r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "modprobe" command occur. 
+
+Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the line appropriate for the system architecture must be present.
+
+# grep -i modprobe /etc/audit/audit.rules
+
+If the command does not return the following output (appropriate to the architecture), this is a finding. 
+
+-w /sbin/modprobe -p x -F auid!=4294967295 -k module-change
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72197">
+    <title>SRG-OS-000004-GPOS-00004</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86821r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030870</version>
+      <title>The operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd.</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).
+
+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-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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000018</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001403</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002130</ident>
+      <fixtext fixref="F-78551r4_fix">Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd".
+
+Add or update the following rule "/etc/audit/rules.d/audit.rules":
+
+-w /etc/passwd -p wa -k identity
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78551r4_fix"/>
+      <check system="C-72431r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd".
+
+Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+
+# grep /etc/passwd /etc/audit/audit.rules
+
+-w /etc/passwd -p wa -k audit_rules_usergroup_modification
+
+If the command does not return a line, or the line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72199">
+    <title>SRG-OS-000466-GPOS-00210</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86823r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030880</version>
+      <title>All uses of the rename command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
+
+Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78553r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "rename" command occur.
+
+Add the following rules in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S rename -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+-a always,exit -F arch=b64 -S rename -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78553r4_fix"/>
+      <check system="C-72433r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "rename" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i rename /etc/audit/audit.rules
+-a always,exit -F arch=b32 -S rename -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+-a always,exit -F arch=b64 -S rename -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72201">
+    <title>SRG-OS-000466-GPOS-00210</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86825r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030890</version>
+      <title>All uses of the renameat command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
+
+Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78555r5_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "renameat" command occur.
+
+Add the following rules in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S renameat  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+-a always,exit -F arch=b64 -S renameat  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78555r5_fix"/>
+      <check system="C-72435r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "renameat" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i renameat  /etc/audit/audit.rules
+-a always,exit -F arch=b32 -S renameat  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+-a always,exit -F arch=b64 -S renameat  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72203">
+    <title>SRG-OS-000466-GPOS-00210</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86827r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030900</version>
+      <title>All uses of the rmdir command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
+
+Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78557r5_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "rmdir" command occur.
+
+Add the following rules in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S rmdir  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+-a always,exit -F arch=b64 -S rmdir  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78557r5_fix"/>
+      <check system="C-72437r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "rmdir" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i rmdir /etc/audit/audit.rules
+-a always,exit -F arch=b32 -S rmdir  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+-a always,exit -F arch=b64 -S rmdir  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72205">
+    <title>SRG-OS-000466-GPOS-00210</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86829r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030910</version>
+      <title>All uses of the unlink command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
+
+Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78559r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "unlink" command occur.
+
+Add the following rules in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S unlink -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+-a always,exit -F arch=b64 -S unlink  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78559r4_fix"/>
+      <check system="C-72439r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "unlink" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i unlink/etc/audit/audit.rules
+-a always,exit -F arch=b32 -S unlink -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+-a always,exit -F arch=b64 -S unlink  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72207">
+    <title>SRG-OS-000466-GPOS-00210</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86831r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030920</version>
+      <title>All uses of the unlinkat command must be audited.</title>
+      <description>&lt;VulnDiscussion&gt;If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.
+
+Satisfies: SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00210, SRG-OS-000468-GPOS-00212, SRG-OS-000392-GPOS-00172&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002884</ident>
+      <fixtext fixref="F-78561r4_fix">Configure the operating system to generate audit records when successful/unsuccessful attempts to use the "unlinkat" command occur.
+
+Add the following rules in "/etc/audit/rules.d/audit.rules" (removing those that do not match the CPU architecture):
+
+-a always,exit -F arch=b32 -S unlinkat -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+-a always,exit -F arch=b64 -S unlinkat  -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-78561r4_fix"/>
+      <check system="C-72441r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system generates audit records when successful/unsuccessful attempts to use the "unlinkat" command occur.
+
+Check the file system rules in "/etc/audit/audit.rules" with the following commands:
+
+Note: The output lines of the command are duplicated to cover both 32-bit and 64-bit architectures. Only the lines appropriate for the system architecture must be present.
+
+# grep -i unlinkat/etc/audit/audit.rules
+-a always,exit -F arch=b32 -S unlinkat -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+-a always,exit -F arch=b64 -S unlinkat -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k delete
+
+If the command does not return any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72209">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86833r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-031000</version>
+      <title>The system must send rsyslog output to a log aggregation server.</title>
+      <description>&lt;VulnDiscussion&gt;Sending rsyslog output to another system ensures that the logs cannot be removed or modified in the event that the system is compromised or has a hardware failure.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78563r1_fix">Modify the "/etc/rsyslog.conf" file to contain a configuration line to send all "rsyslog" output to a log aggregation system:
+
+*.* @@&lt;log aggregation system name&gt;</fixtext>
+      <fix id="F-78563r1_fix"/>
+      <check system="C-72443r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify "rsyslog" is configured to send all messages to a log aggregation server.
+
+Check the configuration of "rsyslog" with the following command:
+
+Note: If another logging package is used, substitute the utility configuration file for "/etc/rsyslog.conf".
+
+# grep @ /etc/rsyslog.conf
+*.* @@logagg.site.mil
+
+If there are no lines in the "/etc/rsyslog.conf" file that contain the "@" or "@@" symbol(s), and the lines with the correct symbol(s) to send output to another system do not cover all "rsyslog" output, ask the System Administrator to indicate how the audit logs are off-loaded to a different system or media. 
+
+If there is no evidence that the audit logs are being sent to another system, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72211">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86835r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-031010</version>
+      <title>The rsyslog daemon must not accept log messages from other servers unless the server is being used for log aggregation.</title>
+      <description>&lt;VulnDiscussion&gt;Unintentionally running a rsyslog server accepting remote messages puts the system at increased risk. Malicious rsyslog messages sent to the server could exploit vulnerabilities in the server software itself, could introduce misleading information in to the system's logs, or could fill the system's storage leading to a Denial of Service.
+If the system is intended to be a log aggregation server its use must be documented with the ISSO.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
+      <fixtext fixref="F-78565r1_fix">Modify the "/etc/rsyslog.conf" file to remove the "ModLoad imtcp" configuration line, or document the system as being used for log aggregation.</fixtext>
+      <fix id="F-78565r1_fix"/>
+      <check system="C-72445r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that the system is not accepting "rsyslog" messages from other systems unless it is documented as a log aggregation server.
+
+Check the configuration of "rsyslog" with the following command:
+
+# grep imtcp /etc/rsyslog.conf
+ModLoad imtcp
+
+If the "imtcp" module is being loaded in the "/etc/rsyslog.conf" file, ask to see the documentation for the system being used for log aggregation.
+
+If the documentation does not exist, or does not specify the server as a log aggregation system, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72213">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86837r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-032000</version>
+      <title>The system must use a DoD-approved virus scan program.</title>
+      <description>&lt;VulnDiscussion&gt;Virus scanning software can be used to protect a system from penetration from computer viruses and to limit their spread through intermediate systems.  
+
+The virus scanning software should be configured to perform scans dynamically on accessed files. If this capability is not available, the system must be configured to scan, at a minimum, all altered files on the system on a daily basis.
+
+If the system processes inbound SMTP mail, the virus scanner must be configured to scan all received mail.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001668</ident>
+      <fixtext fixref="F-78567r1_fix">Install an approved DoD antivirus solution on the system.</fixtext>
+      <fix id="F-78567r1_fix"/>
+      <check system="C-72447r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system is using a DoD-approved virus scan program.
+
+Check for the presence of "McAfee VirusScan Enterprise for Linux" with the following command:
+
+# systemctl status nails
+nails - service for McAfee VirusScan Enterprise for Linux 
+&gt;  Loaded: loaded /opt/NAI/package/McAfeeVSEForLinux/McAfeeVSEForLinux-2.0.2.&lt;build_number&gt;; enabled)
+&gt;  Active: active (running) since Mon 2015-09-27 04:11:22 UTC;21 min ago
+
+If the "nails" service is not active, check for the presence of "clamav" on the system with the following command:
+
+# systemctl status clamav-daemon.socket
+ systemctl status clamav-daemon.socket
+  clamav-daemon.socket - Socket for Clam AntiVirus userspace daemon
+     Loaded: loaded (/lib/systemd/system/clamav-daemon.socket; enabled)
+     Active: active (running) since Mon 2015-01-12 09:32:59 UTC; 7min ago
+
+If neither of these applications are loaded and active, ask the System Administrator if there is an antivirus package installed and active on the system. 
+
+If no antivirus scan program is active on the system, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72215">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86839r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-032010</version>
+      <title>The system must update the DoD-approved virus scan program every seven days or more frequently.</title>
+      <description>&lt;VulnDiscussion&gt;Virus scanning software can be used to protect a system from penetration from computer viruses and to limit their spread through intermediate systems.  
+
+The virus scanning software should be configured to check for software and virus definition updates with a frequency no longer than seven days. If a manual process is required to update the virus scan software or definitions, it must be documented with the Information System Security Officer (ISSO).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001668</ident>
+      <fixtext fixref="F-78569r1_fix">Update the approved DoD virus scan software and virus definition files.</fixtext>
+      <fix id="F-78569r1_fix"/>
+      <check system="C-72449r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system is using a DoD-approved virus scan program and the virus definition file is less than seven days old.
+
+Check for the presence of "McAfee VirusScan Enterprise for Linux" with the following command:
+
+# systemctl status nails
+nails - service for McAfee VirusScan Enterprise for Linux 
+&gt;  Loaded: loaded /opt/NAI/package/McAfeeVSEForLinux/McAfeeVSEForLinux-2.0.2.&lt;build_number&gt;; enabled)
+&gt;  Active: active (running) since Mon 2015-09-27 04:11:22 UTC;21 min ago
+
+If the "nails" service is not active, check for the presence of "clamav" on the system with the following command:
+
+# systemctl status clamav-daemon.socket
+systemctl status clamav-daemon.socket
+  clamav-daemon.socket - Socket for Clam AntiVirus userspace daemon
+     Loaded: loaded (/lib/systemd/system/clamav-daemon.socket; enabled)
+     Active: active (running) since Mon 2015-01-12 09:32:59 UTC; 7min ago
+
+If "McAfee VirusScan Enterprise for Linux" is active on the system, check the dates of the virus definition files with the following command:
+
+# ls -al /opt/NAI/LinuxShield/engine/dat/*.dat
+&lt;need output&gt;
+
+If the virus definition files have dates older than seven days from the current date, this is a finding.
+
+If "clamav" is active on the system, check the dates of the virus database with the following commands:
+
+# grep -I databasedirectory /etc/clamav.conf
+DatabaseDirectory /var/lib/clamav
+
+# ls -al /var/lib/clamav/*.cvd
+-rwxr-xr-x  1 root root      149156 Mar  5  2011 daily.cvd
+
+If the database file has a date older than seven days from the current date, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72217">
+    <title>SRG-OS-000027-GPOS-00008</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86841r1_rule" severity="low" weight="10.0">
+      <version>RHEL-07-040000</version>
+      <title>The operating system must limit the number of concurrent sessions to 10 for all accounts and/or account types.</title>
+      <description>&lt;VulnDiscussion&gt;Operating system management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the number of allowed users and sessions per user is helpful in reducing the risks related to DoS attacks.
+
+This requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions should be defined based on mission needs and the operational environment for each system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000054</ident>
+      <fixtext fixref="F-78571r1_fix">Configure the operating system to limit the number of concurrent sessions to "10" for all accounts and/or account types.
+
+Add the following line to the top of the /etc/security/limits.conf:
+
+* hard maxlogins 10</fixtext>
+      <fix id="F-78571r1_fix"/>
+      <check system="C-72451r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system limits the number of concurrent sessions to "10" for all accounts and/or account types by issuing the following command:
+
+# grep "maxlogins" /etc/security/limits.conf
+* hard maxlogins 10
+
+This can be set as a global domain (with the * wildcard) but may be set differently for multiple domains.
+
+If the "maxlogins" item is missing or the value is not set to "10" or less for all domains that have the "maxlogins" item assigned, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72219">
+    <title>SRG-OS-000096-GPOS-00050</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86843r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040100</version>
+      <title>The host must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management Component Local Service Assessment (PPSM CLSA) and vulnerability assessments.</title>
+      <description>&lt;VulnDiscussion&gt;In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.
+
+Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component.
+
+To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.
+
+Satisfies: SRG-OS-000096-GPOS-00050, SRG-OS-000297-GPOS-00115&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000382</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002314</ident>
+      <fixtext fixref="F-78573r1_fix">Update the host's firewall settings and/or running services to comply with the PPSM CLSA for the site or program and the PPSM CAL.</fixtext>
+      <fix id="F-78573r1_fix"/>
+      <check system="C-72453r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Inspect the firewall configuration and running services to verify that it is configured to prohibit or restrict the use of functions, ports, protocols, and/or services that are unnecessary or prohibited.
+
+Check which services are currently active with the following command:
+
+# firewall-cmd --list-all
+public (default, active)
+  interfaces: enp0s3
+  sources: 
+  services: dhcpv6-client dns http https ldaps rpc-bind ssh
+  ports: 
+  masquerade: no
+  forward-ports: 
+  icmp-blocks: 
+  rich rules: 
+
+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 additional ports, protocols, or services that are not in the PPSM CLSA, or there are ports, protocols, or services that are prohibited by the PPSM Category Assurance List (CAL), this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72221">
+    <title>SRG-OS-000033-GPOS-00014</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86845r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040110</version>
+      <title>A FIPS 140-2 approved cryptographic algorithm must be used for SSH communications.</title>
+      <description>&lt;VulnDiscussion&gt;Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.
+
+Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
+
+FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system.
+
+Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000120-GPOS-00061, SRG-OS-000125-GPOS-00065, SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000068</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000803</ident>
+      <fixtext fixref="F-78575r3_fix">Configure SSH to use FIPS 140-2 approved cryptographic algorithms.
+
+Add the following line (or modify the line to have the required value) to the "/etc/ssh/sshd_config" file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor).
+
+Ciphers aes128-ctr,aes192-ctr,aes256-ctr
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78575r3_fix"/>
+      <check system="C-72455r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system uses mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.
+
+Note: If RHEL-07-021350 is a finding, this is automatically a finding as the system cannot implement FIPS 140-2-approved cryptographic algorithms and hashes.
+
+The location of the "sshd_config" file may vary if a different daemon is in use.
+
+Inspect the "Ciphers" configuration with the following command:
+
+# grep -i ciphers /etc/ssh/sshd_config
+Ciphers aes128-ctr,aes192-ctr,aes256-ctr
+
+If any ciphers other than "aes128-ctr", "aes192-ctr", or "aes256-ctr" are listed, the "Ciphers" keyword is missing, or the retuned line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72223">
+    <title>SRG-OS-000163-GPOS-00072</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86847r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040160</version>
+      <title>All network connections associated with a communication session must be terminated at the end of the session or after 10 minutes of inactivity from the user at a command prompt, except to fulfill documented and validated mission requirements.</title>
+      <description>&lt;VulnDiscussion&gt;Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element. 
+
+Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001133</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002361</ident>
+      <fixtext fixref="F-78577r3_fix">Configure the operating system to terminate all network connections associated with a communications session at the end of the session or after a period of inactivity.
+
+Add the following line to "/etc/profile" (or modify the line to have the required value):
+
+TMOUT=600
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78577r3_fix"/>
+      <check system="C-72457r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system terminates all network connections associated with a communications session at the end of the session or based on inactivity.
+
+Check the value of the system inactivity timeout with the following command:
+
+# grep -i tmout /etc/bashrc 
+TMOUT=600
+
+If "TMOUT" is not set to "600" or less in "/etc/bashrc", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72225">
+    <title>SRG-OS-000023-GPOS-00006</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86849r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040170</version>
+      <title>The Standard Mandatory DoD Notice and Consent Banner must be displayed immediately prior to, or as part of, remote access logon prompts.</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."
+
+Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007 , 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000048</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000050</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001384</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001385</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001386</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001387</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001388</ident>
+      <fixtext fixref="F-78579r2_fix">Configure the operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via the ssh.
+
+Edit the "/etc/ssh/sshd_config" file to uncomment the banner keyword and configure it to point to a file that will contain the logon banner (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor). An example configuration line is:
+
+banner=/etc/issue
+
+Either create the file containing the banner or replace the text in the file with the Standard Mandatory DoD Notice and Consent Banner. The DoD required text is:
+
+"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."
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78579r2_fix"/>
+      <check system="C-72459r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify any publicly accessible connection to the operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.
+
+Check for the location of the banner file being used with the following command:
+
+# grep -i banner /etc/ssh/sshd_config
+
+banner=/etc/issue
+
+This command will return the banner keyword and the name of the file that contains the ssh banner (in this case "/etc/issue").
+
+If the line is commented out, this is a finding.
+
+View the file specified by the banner keyword to check that it matches the text of 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."
+
+If the system does not display a graphical logon banner or the banner does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding.
+
+If the text in the file does not match the Standard Mandatory DoD Notice and Consent Banner, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72227">
+    <title>SRG-OS-000250-GPOS-00093</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86851r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040180</version>
+      <title>The operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) authentication communications.</title>
+      <description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
+
+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the key used to generate the hash.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001453</ident>
+      <fixtext fixref="F-78581r1_fix">Configure the operating system to implement cryptography to protect the integrity of LDAP authentication sessions.
+
+Set the USELDAPAUTH=yes in "/etc/sysconfig/authconfig".
+
+Set "ssl start_tls" in "/etc/pam_ldap.conf".</fixtext>
+      <fix id="F-78581r1_fix"/>
+      <check system="C-72461r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system implements cryptography to protect the integrity of remote LDAP authentication sessions.
+
+To determine if LDAP is being used for authentication, use the following command:
+
+# grep -i useldapauth /etc/sysconfig/authconfig
+USELDAPAUTH=yes
+
+If USELDAPAUTH=yes, then LDAP is being used. To see if LDAP is configured to use TLS, use the following command:
+
+# grep -i ssl /etc/pam_ldap.conf
+ssl start_tls
+
+If the "ssl" option is not "start_tls", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72229">
+    <title>SRG-OS-000250-GPOS-00093</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86853r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040190</version>
+      <title>The operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications.</title>
+      <description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
+
+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the key used to generate the hash.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001453</ident>
+      <fixtext fixref="F-78583r1_fix">Configure the operating system to implement cryptography to protect the integrity of LDAP remote access sessions.
+
+Set the "tls_cacertdir" option in "/etc/pam_ldap.conf" to point to the directory that will contain the X.509 certificates for peer authentication.
+
+Set the "tls_cacertfile" option in "/etc/pam_ldap.conf" to point to the path for the X.509 certificates used for peer authentication.</fixtext>
+      <fix id="F-78583r1_fix"/>
+      <check system="C-72463r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system implements cryptography to protect the integrity of remote LDAP access sessions.
+
+To determine if LDAP is being used for authentication, use the following command:
+
+# grep -i useldapauth /etc/sysconfig/authconfig
+USELDAPAUTH=yes
+
+If USELDAPAUTH=yes, then LDAP is being used. 
+
+Check for the directory containing X.509 certificates for peer authentication with the following command:
+
+# grep -i cacertdir /etc/pam_ldap.conf
+tls_cacertdir /etc/openldap/certs
+
+Verify the directory set with the "tls_cacertdir" option exists.
+
+If the directory does not exist or the option is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72231">
+    <title>SRG-OS-000250-GPOS-00093</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86855r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040200</version>
+      <title>The operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications.</title>
+      <description>&lt;VulnDiscussion&gt;Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
+
+Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the key used to generate the hash.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001453</ident>
+      <fixtext fixref="F-78585r1_fix">Configure the operating system to implement cryptography to protect the integrity of LDAP remote access sessions.
+
+Set the "tls_cacertfile" option in "/etc/pam_ldap.conf" to point to the path for the X.509 certificates used for peer authentication.</fixtext>
+      <fix id="F-78585r1_fix"/>
+      <check system="C-72465r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system implements cryptography to protect the integrity of remote ldap access sessions.
+
+To determine if LDAP is being used for authentication, use the following command:
+
+# grep -i useldapauth /etc/sysconfig/authconfig
+USELDAPAUTH=yes
+
+If USELDAPAUTH=yes, then LDAP is being used.
+
+Check that the path to the X.509 certificate for peer authentication with the following command:
+
+# grep -i cacertfile /etc/pam_ldap.conf
+tls_cacertfile /etc/openldap/ldap-cacert.pem
+
+Verify the "tls_cacertfile" option points to a file that contains the trusted CA certificate.
+
+If this file does not exist, or the option is commented out or missing, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72233">
+    <title>SRG-OS-000423-GPOS-00187</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86857r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040300</version>
+      <title>All networked systems 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, logical means (cryptography) do not have to be employed, and vice versa.
+
+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002418</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002420</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002421</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002422</ident>
+      <fixtext fixref="F-78587r1_fix">Install SSH packages onto the host with the following commands:
+
+# yum install openssh-clients.x86_64
+# yum install openssh-server.x86_64
+
+Note: 32-bit versions will require different packages.</fixtext>
+      <fix id="F-78587r1_fix"/>
+      <check system="C-72467r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Check to see if sshd is installed with the following command:
+
+# yum list installed ssh
+libssh2.x86_64                           1.4.3-8.el7               @anaconda/7.1
+openssh.x86_64                           6.6.1p1-11.el7            @anaconda/7.1
+openssh-clients.x86_64                   6.6.1p1-11.el7            @anaconda/7.1
+openssh-server.x86_64                    6.6.1p1-11.el7            @anaconda/7.1
+
+If the "SSH server" package is not installed, this is a finding.
+
+If the "SSH client" package is not installed, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72235">
+    <title>SRG-OS-000423-GPOS-00187</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86859r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040310</version>
+      <title>All networked systems must use SSH for confidentiality and integrity of transmitted and received information as well as information during preparation for transmission.</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-000423-GPOS-00188, SRG-OS-000423-GPOS-00189, SRG-OS-000423-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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002418</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002420</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002421</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002422</ident>
+      <fixtext fixref="F-78589r1_fix">Configure the SSH service to automatically start after reboot with the following command:
+
+# systemctl enable sshd ln -s '/usr/lib/systemd/system/sshd.service' '/etc/systemd/system/multi-user.target.wants/sshd.service'</fixtext>
+      <fix id="F-78589r1_fix"/>
+      <check system="C-72469r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify SSH is loaded and active with the following command:
+
+# systemctl status sshd
+ sshd.service - OpenSSH server daemon
+   Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
+   Active: active (running) since Tue 2015-11-17 15:17:22 EST; 4 weeks 0 days ago
+ Main PID: 1348 (sshd)
+   CGroup: /system.slice/sshd.service
+           ??1348 /usr/sbin/sshd -D
+
+If "sshd" does not show a status of "active" and "running", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72237">
+    <title>SRG-OS-000163-GPOS-00072</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86861r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040320</version>
+      <title>All network connections associated with SSH traffic must terminate at the end of the session or after 10 minutes of inactivity, except to fulfill documented and validated mission requirements.</title>
+      <description>&lt;VulnDiscussion&gt;Terminating an idle SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle SSH session will also free up resources committed by the managed network element.
+
+Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.
+
+Satisfies: SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001133</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002361</ident>
+      <fixtext fixref="F-78591r2_fix">Configure the operating system to automatically terminate a user session after inactivity time-outs have expired or at shutdown.
+
+Add the following line (or modify the line to have the required value) to the "/etc/ssh/sshd_config" file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
+
+ClientAliveInterval 600
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78591r2_fix"/>
+      <check system="C-72471r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system automatically terminates a user session after inactivity time-outs have expired.
+
+Check for the value of the "ClientAlive" keyword with the following command:
+
+# grep -i clientalive /etc/ssh/sshd_config
+
+ClientAliveInterval 600
+
+If "ClientAliveInterval" is not set to "600" in "/etc/ ssh/sshd_config", and a lower value is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72239">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86863r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040330</version>
+      <title>The SSH daemon must not allow authentication using RSA rhosts authentication.</title>
+      <description>&lt;VulnDiscussion&gt;Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78593r3_fix">Configure the SSH daemon to not allow authentication using RSA rhosts authentication.
+
+Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes":
+
+RhostsRSAAuthentication yes
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78593r3_fix"/>
+      <check system="C-72473r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the SSH daemon does not allow authentication using RSA rhosts authentication.
+
+To determine how the SSH daemon's "RhostsRSAAuthentication" option is set, run the following command:
+
+# grep RhostsRSAAuthentication /etc/ssh/sshd_config
+
+RhostsRSAAuthentication yes
+
+If the value is returned as "no", the returned line is commented out, or no output is returned, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72241">
+    <title>SRG-OS-000163-GPOS-00072</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86865r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040340</version>
+      <title>All network connections associated with SSH traffic must terminate after a period of inactivity.</title>
+      <description>&lt;VulnDiscussion&gt;Terminating an idle SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle SSH session will also free up resources committed by the managed network element.
+
+Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that the operating system terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.
+
+Satisfies: SRG-OS-000163-GPOS-00072, SRG-OS-000279-GPOS-00109&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001133</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002361</ident>
+      <fixtext fixref="F-78595r3_fix">Configure the operating system to automatically terminate a user session after inactivity time-outs have expired or at shutdown.
+
+Add the following line (or modify the line to have the required value) to the "/etc/ssh/sshd_config" file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
+
+ClientAliveCountMax 0
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78595r3_fix"/>
+      <check system="C-72475r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system automatically terminates a user session after inactivity time-outs have expired.
+
+Check for the value of the "ClientAliveCountMax" keyword with the following command:
+
+# grep -i clientalivecount /etc/ssh/sshd_config
+ClientAliveCountMax 0
+
+If "ClientAliveCountMax" is not set to "0" in "/etc/ ssh/sshd_config", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72243">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86867r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040350</version>
+      <title>The SSH daemon must not allow authentication using rhosts authentication.</title>
+      <description>&lt;VulnDiscussion&gt;Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78597r2_fix">Configure the SSH daemon to not allow authentication using known hosts authentication.
+
+Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes":
+
+IgnoreRhosts yes</fixtext>
+      <fix id="F-78597r2_fix"/>
+      <check system="C-72477r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the SSH daemon does not allow authentication using known hosts authentication.
+
+To determine how the SSH daemon's "IgnoreRhosts" option is set, run the following command:
+
+# grep -i IgnoreRhosts /etc/ssh/sshd_config
+
+IgnoreRhosts yes
+
+If the value is returned as "no", the returned line is commented out, or no output is returned, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72245">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86869r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040360</version>
+      <title>The system must display the date and time of the last successful account logon upon an SSH logon.</title>
+      <description>&lt;VulnDiscussion&gt;Providing users with feedback on when account accesses via SSH last occurred facilitates user recognition and reporting of unauthorized account use.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78599r2_fix">Configure SSH to provide users with feedback on when account accesses last occurred by setting the required configuration options in "/etc/pam.d/sshd" or in the "sshd_config" file used by the system ("/etc/ssh/sshd_config" will be used in the example) (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor).
+
+Add the following line to the top of "/etc/pam.d/sshd":
+
+session     required      pam_lastlog.so showfailed
+
+Or modify the "PrintLastLog" line in "/etc/ssh/sshd_config" to match the following:
+
+PrintLastLog yes
+
+The SSH service must be restarted for changes to "sshd_config" to take effect.</fixtext>
+      <fix id="F-78599r2_fix"/>
+      <check system="C-72479r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify SSH provides users with feedback on when account accesses last occurred.
+
+Check that "PrintLastLog" keyword in the sshd daemon configuration file is used and set to "yes" with the following command:
+
+# grep -i printlastlog /etc/ssh/sshd_config
+PrintLastLog yes
+
+If the "PrintLastLog" keyword is set to "no", is missing, or is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72247">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86871r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040370</version>
+      <title>The system must not permit direct logons to the root account using remote access via SSH.</title>
+      <description>&lt;VulnDiscussion&gt;Even though the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging on directly as root. In addition, logging on with a user-specific account provides individual accountability of actions performed on the system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78601r2_fix">Configure SSH to stop users from logging on remotely as the root user.
+
+Edit the appropriate  "/etc/ssh/sshd_config" file to uncomment or add the line for the "PermitRootLogin" keyword and set its value to "no" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
+
+PermitRootLogin no
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78601r2_fix"/>
+      <check system="C-72481r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify remote access using SSH prevents users from logging on directly as root.
+
+Check that SSH prevents users from logging on directly as root with the following command:
+
+# grep -i permitrootlogin /etc/ssh/sshd_config
+PermitRootLogin no
+
+If the "PermitRootLogin" keyword is set to "yes", is missing, or is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72249">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86873r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040380</version>
+      <title>The SSH daemon must not allow authentication using known hosts authentication.</title>
+      <description>&lt;VulnDiscussion&gt;Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78603r2_fix">Configure the SSH daemon to not allow authentication using known hosts authentication.
+
+Add the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes":
+
+IgnoreUserKnownHosts yes
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78603r2_fix"/>
+      <check system="C-72483r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the SSH daemon does not allow authentication using known hosts authentication.
+
+To determine how the SSH daemon's "IgnoreUserKnownHosts" option is set, run the following command:
+
+# grep -i IgnoreUserKnownHosts /etc/ssh/sshd_config
+
+IgnoreUserKnownHosts yes
+
+If the value is returned as "no", the returned line is commented out, or no output is returned, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72251">
+    <title>SRG-OS-000074-GPOS-00042</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86875r2_rule" severity="high" weight="10.0">
+      <version>RHEL-07-040390</version>
+      <title>The SSH daemon must be configured to only use the SSHv2 protocol.</title>
+      <description>&lt;VulnDiscussion&gt;SSHv1 is an insecure implementation of the SSH protocol and has many well-known vulnerability exploits. Exploits of the SSH daemon could provide immediate root access to the system.
+
+Satisfies: SRG-OS-000074-GPOS-00042, SRG-OS-000480-GPOS-00227&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000197</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78605r2_fix">Remove all Protocol lines that reference version "1" in "/etc/ssh/sshd_config" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor). The "Protocol" line must be as follows:
+
+Protocol 2
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78605r2_fix"/>
+      <check system="C-72485r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the SSH daemon is configured to only use the SSHv2 protocol.
+
+Check that the SSH daemon is configured to only use the SSHv2 protocol with the following command:
+
+# grep -i protocol /etc/ssh/sshd_config
+Protocol 2
+#Protocol 1,2
+
+If any protocol line other than "Protocol 2" is uncommented, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72253">
+    <title>SRG-OS-000250-GPOS-00093</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86877r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040400</version>
+      <title>The SSH daemon must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms.</title>
+      <description>&lt;VulnDiscussion&gt;DoD information systems are required to use FIPS 140-2 approved cryptographic hash functions. The only SSHv2 hash algorithm meeting this requirement is SHA.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001453</ident>
+      <fixtext fixref="F-78607r2_fix">Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "MACs" keyword and set its value to "hmac-sha2-256" and/or "hmac-sha2-512" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
+
+MACs hmac-sha2-256,hmac-sha2-512
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78607r2_fix"/>
+      <check system="C-72487r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the SSH daemon is configured to only use MACs employing FIPS 140-2-approved ciphers.
+
+Note: If RHEL-07-021350 is a finding, this is automatically a finding as the system cannot implement FIPS 140-2-approved cryptographic algorithms and hashes.
+
+Check that the SSH daemon is configured to only use MACs employing FIPS 140-2-approved ciphers with the following command:
+
+# grep -i macs /etc/ssh/sshd_config
+MACs hmac-sha2-256,hmac-sha2-512
+
+If any ciphers other than "hmac-sha2-256" or "hmac-sha2-512" are listed or the retuned line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72255">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86879r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040410</version>
+      <title>The SSH public host key files must have mode 0644 or less permissive.</title>
+      <description>&lt;VulnDiscussion&gt;If a public host key file is modified by an unauthorized user, the SSH service may 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78609r1_fix">Note: SSH public key files may be found in other directories on the system depending on the installation. 
+
+Change the mode of public host key files under "/etc/ssh" to "0644" with the following command:
+
+# chmod 0644 /etc/ssh/*.key.pub</fixtext>
+      <fix id="F-78609r1_fix"/>
+      <check system="C-72489r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the SSH public host key files have mode "0644" or less permissive.
+
+Note: SSH public key files may be found in other directories on the system depending on the installation.
+
+The following command will find all SSH public key files on the system:
+
+# find /etc/ssh -name '*.pub' -exec ls -lL {} \;
+
+-rw-r--r--  1 root  wheel  618 Nov 28 06:43 ssh_host_dsa_key.pub
+-rw-r--r--  1 root  wheel  347 Nov 28 06:43 ssh_host_key.pub
+-rw-r--r--  1 root  wheel  238 Nov 28 06:43 ssh_host_rsa_key.pub
+
+If any file has a mode more permissive than "0644", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72257">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86881r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040420</version>
+      <title>The SSH private host key files must have mode 0600 or less permissive.</title>
+      <description>&lt;VulnDiscussion&gt;If an unauthorized user obtains the private SSH host key file, the host could be impersonated.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78611r3_fix">Configure the mode of SSH private host key files under "/etc/ssh" to "0600" with the following command:
+
+# chmod 0600 /etc/ssh/ssh_host*key</fixtext>
+      <fix id="F-78611r3_fix"/>
+      <check system="C-72491r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the SSH private host key files have mode "0600" or less permissive.
+
+The following command will find all SSH private key files on the system:
+
+# find / -name '*ssh_host*key'
+
+Check the mode of the private host key files under "/etc/ssh" file with the following command:
+
+# ls -lL /etc/ssh/*key
+-rw-------  1 root  wheel  668 Nov 28 06:43 ssh_host_dsa_key
+-rw-------  1 root  wheel  582 Nov 28 06:43 ssh_host_key
+-rw-------  1 root  wheel  887 Nov 28 06:43 ssh_host_rsa_key
+
+If any file has a mode more permissive than "0600", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72259">
+    <title>SRG-OS-000364-GPOS-00151</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86883r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040430</version>
+      <title>The SSH daemon must not permit Generic Security Service Application Program Interface (GSSAPI) authentication unless needed.</title>
+      <description>&lt;VulnDiscussion&gt;GSSAPI authentication is used to provide additional authentication mechanisms to applications. Allowing GSSAPI authentication through SSH exposes the system’s GSSAPI to remote hosts, increasing the attack surface of the system. GSSAPI authentication must be disabled unless needed.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
+      <fixtext fixref="F-78613r2_fix">Uncomment the "GSSAPIAuthentication" keyword in "/etc/ssh/sshd_config" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) and set the value to "no": 
+
+GSSAPIAuthentication no
+
+The SSH service must be restarted for changes to take effect.
+
+If GSSAPI authentication is required, it must be documented, to include the location of the configuration file, with the ISSO.</fixtext>
+      <fix id="F-78613r2_fix"/>
+      <check system="C-72493r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the SSH daemon does not permit GSSAPI authentication unless approved.
+
+Check that the SSH daemon does not permit GSSAPI authentication with the following command:
+
+# grep -i gssapiauth /etc/ssh/sshd_config
+GSSAPIAuthentication no
+
+If the "GSSAPIAuthentication" keyword is missing, is set to "yes" and is not documented with the Information System Security Officer (ISSO), or the returned line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72261">
+    <title>SRG-OS-000364-GPOS-00151</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86885r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040440</version>
+      <title>The SSH daemon must not permit Kerberos authentication unless needed.</title>
+      <description>&lt;VulnDiscussion&gt;Kerberos authentication for SSH is often implemented using Generic Security Service Application Program Interface (GSSAPI). If Kerberos is enabled through SSH, the SSH daemon provides a means of access to the system's Kerberos implementation. Vulnerabilities in the system's Kerberos implementation may then be subject to exploitation. To reduce the attack surface of the system, the Kerberos authentication mechanism within SSH must be disabled for systems not using this capability.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
+      <fixtext fixref="F-78615r2_fix">Uncomment the "KerberosAuthentication" keyword in "/etc/ssh/sshd_config" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) and set the value to "no":
+
+KerberosAuthentication no
+
+The SSH service must be restarted for changes to take effect.
+
+If Kerberos authentication is required, it must be documented, to include the location of the configuration file, with the ISSO.</fixtext>
+      <fix id="F-78615r2_fix"/>
+      <check system="C-72495r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the SSH daemon does not permit Kerberos to authenticate passwords unless approved.
+
+Check that the SSH daemon does not permit Kerberos to authenticate passwords with the following command:
+
+# grep -i kerberosauth /etc/ssh/sshd_config
+KerberosAuthentication no
+
+If the "KerberosAuthentication" keyword is missing, or is set to "yes" and is not documented with the Information System Security Officer (ISSO), or the returned line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72263">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86887r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040450</version>
+      <title>The SSH daemon must perform strict mode checking of home directory configuration files.</title>
+      <description>&lt;VulnDiscussion&gt;If other users have access to modify user-specific SSH configuration files, they may be able to log on to the system as another user.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78617r4_fix">Uncomment the "StrictModes" keyword in "/etc/ssh/sshd_config" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) and set the value to "yes":
+
+StrictModes yes
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78617r4_fix"/>
+      <check system="C-72497r6_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the SSH daemon performs strict mode checking of home directory configuration files.
+
+The location of the "sshd_config" file may vary if a different daemon is in use.
+
+Inspect the "sshd_config" file with the following command:
+
+# grep -i strictmodes /etc/ssh/sshd_config
+
+StrictModes yes
+
+If "StrictModes" is set to "no", is missing, or the returned line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72265">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86889r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040460</version>
+      <title>The SSH daemon must use privilege separation.</title>
+      <description>&lt;VulnDiscussion&gt;SSH daemon privilege separation causes the SSH process to drop root privileges when not needed, which would decrease the impact of software vulnerabilities in the unprivileged section.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78619r2_fix">Uncomment the "UsePrivilegeSeparation" keyword in "/etc/ssh/sshd_config" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) and set the value to "sandbox" or "yes":
+
+UsePrivilegeSeparation sandbox
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78619r2_fix"/>
+      <check system="C-72499r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the SSH daemon performs privilege separation.
+
+Check that the SSH daemon performs privilege separation with the following command:
+
+# grep -i usepriv /etc/ssh/sshd_config
+
+UsePrivilegeSeparation sandbox
+
+If the "UsePrivilegeSeparation" keyword is set to "no", is missing, or the retuned line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72267">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86891r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040470</version>
+      <title>The SSH daemon must not allow compression or must only allow compression after successful authentication.</title>
+      <description>&lt;VulnDiscussion&gt;If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the system from an unauthenticated connection, potentially with root privileges.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78621r2_fix">Uncomment the "Compression" keyword in "/etc/ssh/sshd_config" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor) on the system and set the value to "delayed" or "no":
+
+Compression no
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78621r2_fix"/>
+      <check system="C-72501r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the SSH daemon performs compression after a user successfully authenticates.
+
+Check that the SSH daemon performs compression after a user successfully authenticates with the following command:
+
+# grep -i compression /etc/ssh/sshd_config
+Compression delayed
+
+If the "Compression" keyword is set to "yes", is missing, or the retuned line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72269">
+    <title>SRG-OS-000355-GPOS-00143</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86893r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040500</version>
+      <title>The operating system must, for networked systems, synchronize clocks with a server that is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, 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).
+
+Satisfies: SRG-OS-000355-GPOS-00143, SRG-OS-000356-GPOS-00144&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001891</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002046</ident>
+      <fixtext fixref="F-78623r3_fix">Edit the "/etc/ntp.conf" file and add or update an entry to define "maxpoll" to "10" as follows:
+
+maxpoll 10
+
+If NTP was running and "maxpoll" was updated, the NTP service must be restarted:
+
+# systemctl restart ntpd
+
+If NTP was not running, it must be started:
+
+# systemctl start ntpd</fixtext>
+      <fix id="F-78623r3_fix"/>
+      <check system="C-72503r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Check to see if NTP is running in continuous mode.
+
+# ps -ef | grep ntp
+
+If NTP is not running, this is a finding.
+
+If the process is found, then check the "ntp.conf" file for the "maxpoll" option setting:
+
+# grep maxpoll /etc/ntp.conf
+
+maxpoll 17
+
+If the option is set to "17" or is not set, this is a finding.
+
+If the file does not exist, check the "/etc/cron.daily" subdirectory for a crontab file controlling the execution of the "ntpdate" command.
+
+# grep –l ntpdate /etc/cron.daily
+
+# ls -al /etc/cron.* | grep aide
+ntp
+
+If a crontab file does not exist in the "/etc/cron.daily" that executes the "ntpdate" file, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72271">
+    <title>SRG-OS-000420-GPOS-00186</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86895r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040510</version>
+      <title>The operating system must protect against or limit the effects of Denial of Service (DoS) attacks by validating the operating system is implementing rate-limiting measures on impacted network interfaces.</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.
+
+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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-002385</ident>
+      <fixtext fixref="F-78625r1_fix">Create a direct firewall rule to protect against DoS attacks with the following command:
+
+Note: The command is to add a rule to the public zone.
+
+# firewall-cmd --direct --add-rule ipv4 filter IN_public_allow 0 -p tcp -m limit --limit 25/minute --limit-burst 100  -j ACCEPT</fixtext>
+      <fix id="F-78625r1_fix"/>
+      <check system="C-72505r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system protects against or limits the effects of DoS attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces.
+
+Check the firewall configuration with the following command:
+
+Note: The command is to query rules for the public zone.
+
+# firewall-cmd --direct --get-rule ipv4 filter IN_public_allow
+rule ipv4 filter IN_public_allow 0 -p tcp -m limit --limit 25/minute --limit-burst 100  -j ACCEPT
+
+If a rule with both the limit and limit-burst arguments parameters does not exist, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72273">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86897r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040520</version>
+      <title>The operating system must enable an application firewall, if available.</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.
+
+Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000480-GPOS-00231, SRG-OS-000480-GPOS-00232&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78627r1_fix">Ensure the operating system's application firewall is enabled.
+
+Install the "firewalld" package, if it is not on the system, with the following command:
+
+# yum install firewalld
+
+Start the firewall via "systemctl" with the following command:
+
+# systemctl start firewalld</fixtext>
+      <fix id="F-78627r1_fix"/>
+      <check system="C-72507r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system enabled an application firewall.
+
+Check to see if "firewalld" is installed with the following command:
+
+# yum list installed firewalld
+firewalld-0.3.9-11.el7.noarch.rpm
+
+If the "firewalld" package is not installed, ask the System Administrator if another firewall application (such as iptables) is installed. 
+
+If an application firewall is not installed, this is a finding. 
+
+Check to see if the firewall is loaded and active with the following command:
+
+# systemctl status firewalld
+firewalld.service - firewalld - dynamic firewall daemon
+
+   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
+   Active: active (running) since Tue 2014-06-17 11:14:49 CEST; 5 days ago
+
+If "firewalld" does not show a status of "loaded" and "active", this is a finding. 
+
+Check the state of the firewall:
+
+# firewall-cmd --state 
+running
+
+If "firewalld" does not show a state of "running", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72275">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86899r1_rule" severity="low" weight="10.0">
+      <version>RHEL-07-040530</version>
+      <title>The system must display the date and time of the last successful account logon upon logon.</title>
+      <description>&lt;VulnDiscussion&gt;Providing users with feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78629r1_fix">Configure the operating system to provide users with feedback on when account accesses last occurred by setting the required configuration options in "/etc/pam.d/postlogin-ac". 
+
+Add the following line to the top of "/etc/pam.d/postlogin-ac":
+
+session     required      pam_lastlog.so showfailed</fixtext>
+      <fix id="F-78629r1_fix"/>
+      <check system="C-72509r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify users are provided with feedback on when account accesses last occurred.
+
+Check that "pam_lastlog" is used and not silent with the following command:
+
+# grep pam_lastlog /etc/pam.d/postlogin-ac
+
+session     required      pam_lastlog.so showfailed silent
+
+If "pam_lastlog" is missing from "/etc/pam.d/postlogin-ac" file, or the silent option is present on the line check for the "PrintLastLog" keyword in the sshd daemon configuration file, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72277">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86901r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-040540</version>
+      <title>There must be no .shosts files on the system.</title>
+      <description>&lt;VulnDiscussion&gt;The .shosts files are used to configure host-based authentication for individual users or the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78631r1_fix">Remove any found ".shosts" files from the system.
+
+# rm /[path]/[to]/[file]/.shosts</fixtext>
+      <fix id="F-78631r1_fix"/>
+      <check system="C-72511r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify there are no ".shosts" files on the system.
+
+Check the system for the existence of these files with the following command:
+
+# find / -name '*.shosts'
+
+If any ".shosts" files are found on the system, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72279">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86903r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-040550</version>
+      <title>There must be no shosts.equiv files on the system.</title>
+      <description>&lt;VulnDiscussion&gt;The shosts.equiv files are used to configure host-based authentication for the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78633r1_fix">Remove any found "shosts.equiv" files from the system.
+
+# rm /[path]/[to]/[file]/shosts.equiv</fixtext>
+      <fix id="F-78633r1_fix"/>
+      <check system="C-72513r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify there are no "shosts.equiv" files on the system.
+
+Check the system for the existence of these files with the following command:
+
+# find / -name shosts.equiv
+
+If any "shosts.equiv" files are found on the system, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72281">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86905r1_rule" severity="low" weight="10.0">
+      <version>RHEL-07-040600</version>
+      <title>For systems using DNS resolution, at least two name servers must be configured.</title>
+      <description>&lt;VulnDiscussion&gt;To provide availability for name resolution services, multiple redundant name servers are mandated. A failure in name resolution could lead to the failure of security functions requiring name resolution, which may include time synchronization, centralized authentication, and remote system logging.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78635r1_fix">Configure the operating system to use two or more name servers for DNS resolution.
+
+Edit the "/etc/resolv.conf" file to uncomment or add the two or more "nameserver" option lines with the IP address of local authoritative name servers. If local host resolution is being performed, the "/etc/resolv.conf" file must be empty. An empty "/etc/resolv.conf" file can be created as follows:
+
+# echo -n &gt; /etc/resolv.conf
+
+And then make the file immutable with the following command:
+
+# chattr +i /etc/resolv.conf
+
+If the "/etc/resolv.conf" file must be mutable, the required configuration must be documented with the Information System Security Officer (ISSO) and the file must be verified by the system file integrity tool.</fixtext>
+      <fix id="F-78635r1_fix"/>
+      <check system="C-72515r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Determine whether the system is using local or DNS name resolution with the following command:
+
+# grep hosts /etc/nsswitch.conf
+hosts:   files dns
+
+If the DNS entry is missing from the host’s line in the "/etc/nsswitch.conf" file, the "/etc/resolv.conf" file must be empty.
+
+Verify the "/etc/resolv.conf" file is empty with the following command:
+
+# ls -al /etc/resolv.conf
+-rw-r--r--  1 root root        0 Aug 19 08:31 resolv.conf
+
+If local host authentication is being used and the "/etc/resolv.conf" file is not empty, this is a finding.
+
+If the DNS entry is found on the host’s line of the "/etc/nsswitch.conf" file, verify the operating system is configured to use two or more name servers for DNS resolution.
+
+Determine the name servers used by the system with the following command:
+
+# grep nameserver /etc/resolv.conf
+nameserver 192.168.1.2
+nameserver 192.168.1.3
+
+If less than two lines are returned that are not commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72283">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86907r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040610</version>
+      <title>The system must not forward Internet Protocol version 4 (IPv4) source-routed packets.</title>
+      <description>&lt;VulnDiscussion&gt;Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78637r1_fix">Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" (or modify the line to have the required value):
+
+net.ipv4.conf.all.accept_source_route = 0</fixtext>
+      <fix id="F-78637r1_fix"/>
+      <check system="C-72517r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system does not accept IPv4 source-routed packets.
+
+Check the value of the accept source route variable with the following command:
+
+# /sbin/sysctl -a | grep  net.ipv4.conf.all.accept_source_route
+net.ipv4.conf.all.accept_source_route=0
+
+If the returned line does not have a value of "0", a line is not returned, or the returned line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72285">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86909r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040620</version>
+      <title>The system must not forward Internet Protocol version 4 (IPv4) source-routed packets by default.</title>
+      <description>&lt;VulnDiscussion&gt;Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78639r1_fix">Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" (or modify the line to have the required value):
+
+net.ipv4.conf.default.accept_source_route = 0</fixtext>
+      <fix id="F-78639r1_fix"/>
+      <check system="C-72519r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system does not accept IPv4 source-routed packets by default.
+
+Check the value of the accept source route variable with the following command:
+
+# /sbin/sysctl -a | grep  net.ipv4.conf.default.accept_source_route
+net.ipv4.conf.default.accept_source_route=0
+
+If the returned line does not have a value of "0", a line is not returned, or the returned line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72287">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86911r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040630</version>
+      <title>The system must not respond to Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) echoes sent to a broadcast address.</title>
+      <description>&lt;VulnDiscussion&gt;Responding to broadcast (ICMP) echoes facilitates network mapping and provides a vector for amplification 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78641r1_fix">Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" (or modify the line to have the required value):
+
+net.ipv4.icmp_echo_ignore_broadcasts=1</fixtext>
+      <fix id="F-78641r1_fix"/>
+      <check system="C-72521r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system does not respond to IPv4 ICMP echoes sent to a broadcast address.
+
+Check the value of the "icmp_echo_ignore_broadcasts" variable with the following command:
+
+# /sbin/sysctl -a | grep  net.ipv4.icmp_echo_ignore_broadcasts
+net.ipv4.icmp_echo_ignore_broadcasts=1
+
+If the returned line does not have a value of "1", a line is not returned, or the retuned line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72289">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86913r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040640</version>
+      <title>The system must prevent Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages from being accepted.</title>
+      <description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78643r2_fix">Set the system to not accept IPv4 ICMP redirect messages by adding the following line to "/etc/sysctl.conf" (or modify the line to have the required value):
+
+net.ipv4.conf.default.accept_redirects = 0</fixtext>
+      <fix id="F-78643r2_fix"/>
+      <check system="C-72523r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system will not accept IPv4 ICMP redirect messages.
+
+Check the value of the default "accept_redirects" variables with the following command:
+
+# /sbin/sysctl -a | grep  'net.ipv4.conf.default.accept_redirects'
+net.ipv4.conf.default.accept_redirects=0
+
+If the returned line does not have a value of "0", or a line is not returned, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72291">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86915r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040650</version>
+      <title>The system must not allow interfaces to perform Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects by default.</title>
+      <description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78645r2_fix">Configure the system to not allow interfaces to perform IPv4 ICMP redirects by default. 
+
+Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" (or modify the line to have the required value):
+
+net.ipv4.conf.default.send_redirects=0</fixtext>
+      <fix id="F-78645r2_fix"/>
+      <check system="C-72525r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system does not allow interfaces to perform IPv4 ICMP redirects by default.
+
+Check the value of the "default send_redirects" variables with the following command:
+
+# grep  'net.ipv4.conf.default.send_redirects' /etc/sysctl.conf
+net.ipv4.conf.default.send_redirects=0
+
+If the returned line does not have a value of "0", or a line is not returned, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72293">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86917r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040660</version>
+      <title>The system must not send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects.</title>
+      <description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78647r2_fix">Configure the system to not allow interfaces to perform IPv4 ICMP redirects. 
+
+Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" (or modify the line to have the required value):
+
+net.ipv4.conf.all.send_redirects=0</fixtext>
+      <fix id="F-78647r2_fix"/>
+      <check system="C-72527r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system does not send IPv4 ICMP redirect messages.
+
+Check the value of the "all send_redirects" variables with the following command:
+
+# grep  'net.ipv4.conf.all.send_redirects' /etc/sysctl.conf
+
+net.ipv4.conf.all.send_redirects=0
+
+If the returned line does not have a value of "0", or a line is not returned, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72295">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86919r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040670</version>
+      <title>Network interfaces must not be in promiscuous mode.</title>
+      <description>&lt;VulnDiscussion&gt;Network interfaces in promiscuous mode allow for the capture of all network traffic visible to the system. If unauthorized individuals can access these applications, it may allow then to collect information such as logon IDs, passwords, and key exchanges between systems.
+
+If the system is being used to perform a network troubleshooting function, the use of these tools must be documented with the Information System Security Officer (ISSO) and restricted to only authorized personnel.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78649r1_fix">Configure network interfaces to turn off promiscuous mode unless approved by the ISSO and documented.
+
+Set the promiscuous mode of an interface to off with the following command:
+
+#ip link set dev &lt;devicename&gt; multicast off promisc off</fixtext>
+      <fix id="F-78649r1_fix"/>
+      <check system="C-72529r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify network interfaces are not in promiscuous mode unless approved by the ISSO and documented.
+
+Check for the status with the following command:
+
+# ip link | grep -i promisc
+
+If network interfaces are found on the system in promiscuous mode and their use has not been approved by the ISSO and documented, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72297">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86921r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040680</version>
+      <title>The system must be configured to prevent unrestricted mail relaying.</title>
+      <description>&lt;VulnDiscussion&gt;If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending spam or other unauthorized activity.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78651r2_fix">If "postfix" is installed, modify the "/etc/postfix/main.cf" file to restrict client connections to the local network with the following command:
+
+# postconf -e 'smtpd_client_restrictions = permit_mynetworks,reject'</fixtext>
+      <fix id="F-78651r2_fix"/>
+      <check system="C-72531r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system is configured to prevent unrestricted mail relaying.
+
+Determine if "postfix" is installed with the following commands:
+
+# yum list installed postfix
+postfix-2.6.6-6.el7.x86_64.rpm 
+
+If postfix is not installed, this is Not Applicable.
+
+If postfix is installed, determine if it is configured to reject connections from unknown or untrusted networks with the following command:
+
+# postconf -n smtpd_client_restrictions
+smtpd_client_restrictions = permit_mynetworks, reject
+
+If the "smtpd_client_restrictions" parameter contains any entries other than "permit_mynetworks" and "reject", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72299">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86923r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-040690</version>
+      <title>A File Transfer Protocol (FTP) server package must not be installed unless needed.</title>
+      <description>&lt;VulnDiscussion&gt;The FTP service provides an unencrypted remote access that does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to log on using this service, the privileged user password could be compromised. SSH or other encrypted file transfer methods must be used in place of this service.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78653r1_fix">Document the "lftpd" package with the ISSO as an operational requirement or remove it from the system with the following command:
+
+# yum remove lftpd</fixtext>
+      <fix id="F-78653r1_fix"/>
+      <check system="C-72533r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify a lightweight FTP server has not been installed on the system.
+
+Check to see if a lightweight FTP server has been installed with the following commands:
+
+# yum list installed lftpd
+ lftp-4.4.8-7.el7.x86_64.rpm
+
+If "lftpd" is installed and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72301">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86925r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-040700</version>
+      <title>The Trivial File Transfer Protocol (TFTP) server package must not be installed if not required for operational support.</title>
+      <description>&lt;VulnDiscussion&gt;If TFTP is required for operational support (such as the transmission of router configurations) its use must be documented with the Information System Security Officer (ISSO), restricted to only authorized personnel, and have access control rules established.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000318</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000368</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001812</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001813</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001814</ident>
+      <fixtext fixref="F-78655r1_fix">Remove the TFTP package from the system with the following command:
+
+# yum remove tftp</fixtext>
+      <fix id="F-78655r1_fix"/>
+      <check system="C-72535r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify a TFTP server has not been installed on the system.
+
+Check to see if a TFTP server has been installed with the following command:
+
+# yum list installed tftp-server
+tftp-server-0.49-9.el7.x86_64.rpm
+
+If TFTP is installed and the requirement for TFTP is not documented with the ISSO, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72303">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86927r2_rule" severity="high" weight="10.0">
+      <version>RHEL-07-040710</version>
+      <title>Remote X connections for interactive users must be encrypted.</title>
+      <description>&lt;VulnDiscussion&gt;Open X displays allow an attacker to capture keystrokes and execute commands remotely.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78657r4_fix">Configure SSH to encrypt connections for interactive users.
+
+Edit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "X11Forwarding" keyword and set its value to "yes" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor):
+
+X11Fowarding yes
+
+The SSH service must be restarted for changes to take effect.</fixtext>
+      <fix id="F-78657r4_fix"/>
+      <check system="C-72537r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify remote X connections for interactive users are encrypted.
+
+Check that remote X connections are encrypted with the following command:
+
+# grep -i x11forwarding /etc/ssh/sshd_config
+X11Fowarding yes
+
+If the "X11Forwarding" keyword is set to "no", is missing, or is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72305">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86929r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040720</version>
+      <title>If the Trivial File Transfer Protocol (TFTP) server is required, the TFTP daemon must be configured to operate in secure mode.</title>
+      <description>&lt;VulnDiscussion&gt;Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78659r1_fix">Configure the TFTP daemon to operate in secure mode by adding the following line to "/etc/xinetd.d/tftp" (or modify the line to have the required value):
+
+server_args = -s /var/lib/tftpboot</fixtext>
+      <fix id="F-78659r1_fix"/>
+      <check system="C-72539r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the TFTP daemon is configured to operate in secure mode.
+
+Check to see if a TFTP server has been installed with the following commands:
+
+# yum list installed | grep tftp
+tftp-0.49-9.el7.x86_64.rpm
+
+If a TFTP server is not installed, this is Not Applicable.
+
+If a TFTP server is installed, check for the server arguments with the following command: 
+
+# grep server_arge /etc/xinetd.d/tftp
+server_args = -s /var/lib/tftpboot
+
+If the "server_args" line does not have a "-s" option and a subdirectory is not assigned, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72307">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86931r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040730</version>
+      <title>An X Windows display manager must not be installed unless approved.</title>
+      <description>&lt;VulnDiscussion&gt;Internet services that are not required for system or application processes must not be active to decrease the attack surface of the system. X Windows has a long history of security vulnerabilities and will not be used unless approved and documented.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78661r1_fix">Document the requirement for an X Windows server with the ISSO or remove the related packages with the following commands:
+
+#yum groupremove "X Window System"
+
+#yum remove xorg-x11-server-common</fixtext>
+      <fix id="F-78661r1_fix"/>
+      <check system="C-72541r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that if the system has X Windows System installed, it is authorized.
+
+Check for the X11 package with the following command:
+
+# yum group list installed "X Window System"
+
+Ask the System Administrator if use of the X Windows System is an operational requirement.
+
+If the use of X Windows on the system is not documented with the Information System Security Officer (ISSO), this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72309">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86933r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040740</version>
+      <title>The system must not be performing packet forwarding unless the system is a router.</title>
+      <description>&lt;VulnDiscussion&gt;Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78663r1_fix">Set the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" (or modify the line to have the required value):
+
+net.ipv4.ip_forward = 0</fixtext>
+      <fix id="F-78663r1_fix"/>
+      <check system="C-72543r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system is not performing packet forwarding, unless the system is a router.
+
+Check to see if IP forwarding is enabled using the following command:
+
+# /sbin/sysctl -a | grep  net.ipv4.ip_forward
+net.ipv4.ip_forward=0
+
+If IP forwarding value is "1" and the system is hosting any application, database, or web servers, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72311">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86935r3_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040750</version>
+      <title>The Network File System (NFS) must be configured to use RPCSEC_GSS.</title>
+      <description>&lt;VulnDiscussion&gt;When an NFS server is configured to use RPCSEC_SYS, a selected userid and groupid are used to handle requests from the remote user. The userid and groupid could mistakenly or maliciously be set incorrectly. The RPCSEC_GSS method of authentication uses certificates on the server and client systems to more securely authenticate the remote mount request.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78665r2_fix">Update the "/etc/fstab" file so the option "sec" is defined for each NFS mounted file system and the "sec" option does not have the "sys" setting. 
+
+Ensure the "sec" option is defined as "krb5:krb5i:krb5p".</fixtext>
+      <fix id="F-78665r2_fix"/>
+      <check system="C-72545r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify "AUTH_GSS" is being used to authenticate NFS mounts.
+
+To check if the system is importing an NFS file system, look for any entries in the "/etc/fstab" file that have a file system type of "nfs" with the following command:
+
+# cat /etc/fstab | grep nfs
+192.168.21.5:/mnt/export /data1 nfs4 rw,sync ,soft,sec=krb5:krb5i:krb5p
+
+If the system is mounting file systems via NFS and has the sec option without the "krb5:krb5i:krb5p" settings, the "sec" option has the "sys" setting, or the "sec" option is missing, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72313">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86937r1_rule" severity="high" weight="10.0">
+      <version>RHEL-07-040800</version>
+      <title>SNMP community strings must be changed from the default.</title>
+      <description>&lt;VulnDiscussion&gt;Whether active or not, default Simple Network Management Protocol (SNMP) community strings must be changed to maintain security. If the service is running with the default authenticators, anyone can gather data about the system and the network and use the information to potentially compromise the integrity of the system or network(s). It is highly recommended that SNMP version 3 user authentication and message encryption be used in place of the version 2 community strings.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78667r1_fix">If the "/etc/snmp/snmpd.conf" file exists, modify any lines that contain a community string value of "public" or "private" to another string value.</fixtext>
+      <fix id="F-78667r1_fix"/>
+      <check system="C-72547r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that a system using SNMP is not using default community strings.
+
+Check to see if the "/etc/snmp/snmpd.conf" file exists with the following command:
+
+# ls -al /etc/snmp/snmpd.conf
+ -rw-------   1 root root      52640 Mar 12 11:08 snmpd.conf
+
+If the file does not exist, this is Not Applicable.
+
+If the file does exist, check for the default community strings with the following commands:
+
+# grep public /etc/snmp/snmpd.conf
+# grep private /etc/snmp/snmpd.conf
+
+If either of these commands returns any output, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72315">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86939r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040810</version>
+      <title>The system access control program must be configured to grant or deny system access to specific hosts and services.</title>
+      <description>&lt;VulnDiscussion&gt;If the systems access control program is not configured with appropriate rules for allowing and denying access to system network resources, services may be accessible to unauthorized hosts.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78669r1_fix">If "firewalld" is installed and active on the system, configure rules for allowing specific services and hosts. 
+
+If "tcpwrappers" is installed, configure the "/etc/hosts.allow" and "/etc/hosts.deny" to allow or deny access to specific hosts.</fixtext>
+      <fix id="F-78669r1_fix"/>
+      <check system="C-72549r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>If the "firewalld" package is not installed, ask the System Administrator (SA) if another firewall application (such as iptables) is installed. If an application firewall is not installed, this is a finding. 
+
+Verify the system's access control program is configured to grant or deny system access to specific hosts.
+
+Check to see if "firewalld" is active with the following command:
+
+# systemctl status firewalld
+firewalld.service - firewalld - dynamic firewall daemon
+   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
+   Active: active (running) since Sun 2014-04-20 14:06:46 BST; 30s ago
+
+If "firewalld" is active, check to see if it is configured to grant or deny access to specific hosts or services with the following commands:
+
+# firewall-cmd --get-default-zone
+public
+
+# firewall-cmd --list-all --zone=public
+public (default, active)
+  interfaces: eth0
+  sources:
+  services: mdns ssh
+  ports:
+  masquerade: no
+  forward-ports:
+  icmp-blocks:
+  rich rules:
+ rule family="ipv4" source address="92.188.21.1/24" accept
+ rule family="ipv4" source address="211.17.142.46/32" accept
+
+If "firewalld" is not active, determine whether "tcpwrappers" is being used by checking whether the "hosts.allow" and "hosts.deny" files are empty with the following commands:
+
+# ls -al /etc/hosts.allow
+rw-r----- 1 root root 9 Aug  2 23:13 /etc/hosts.allow
+ 
+# ls -al /etc/hosts.deny
+-rw-r----- 1 root root  9 Apr  9  2007 /etc/hosts.deny
+
+If "firewalld" and "tcpwrappers" are not installed, configured, and active, ask the SA if another access control program (such as iptables) is installed and active. Ask the SA to show that the running configuration grants or denies access to specific hosts or services.
+
+If "firewalld" is active and is not configured to grant access to specific hosts and "tcpwrappers" is not configured to grant or deny access to specific hosts, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72317">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86941r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040820</version>
+      <title>The system must not have unauthorized IP tunnels configured.</title>
+      <description>&lt;VulnDiscussion&gt;IP tunneling mechanisms can be used to bypass network filtering. If tunneling is required, it must be documented with the Information System Security Officer (ISSO).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78671r1_fix">Remove all unapproved tunnels from the system, or document them with the ISSO.</fixtext>
+      <fix id="F-78671r1_fix"/>
+      <check system="C-72551r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system does not have unauthorized IP tunnels configured.
+
+Check to see if "libreswan" is installed with the following command:
+
+# yum list installed libreswan
+openswan-2.6.32-27.el6.x86_64
+
+If "libreswan" is installed, check to see if the "IPsec" service is active with the following command:
+
+# systemctl status ipsec
+ipsec.service - Internet Key Exchange (IKE) Protocol Daemon for IPsec
+   Loaded: loaded (/usr/lib/systemd/system/ipsec.service; disabled)
+   Active: inactive (dead)
+
+If the "IPsec" service is active, check to see if any tunnels are configured in "/etc/ipsec.conf" and "/etc/ipsec.d/" with the following commands:
+
+# grep -i conn /etc/ipsec.conf
+conn mytunnel
+
+# grep -i conn /etc/ipsec.d/*.conf
+conn mytunnel
+
+If there are indications that a "conn" parameter is configured for a tunnel, ask the System Administrator if the tunnel is documented with the ISSO. If "libreswan" is installed, "IPsec" is active, and an undocumented tunnel is active, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72319">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-86943r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040830</version>
+      <title>The system must not forward IPv6 source-routed packets.</title>
+      <description>&lt;VulnDiscussion&gt;Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv6 forwarding is enabled and the system is functioning as a router.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-78673r1_fix">Set the system to the required kernel parameter, if IPv6 is enabled, by adding the following line to "/etc/sysctl.conf" (or modify the line to have the required value):
+
+net.ipv6.conf.all.accept_source_route = 0</fixtext>
+      <fix id="F-78673r1_fix"/>
+      <check system="C-72553r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system does not accept IPv6 source-routed packets.
+
+Note: If IPv6 is not enabled, the key will not exist, and this is not a finding.
+
+Check the value of the accept source route variable with the following command:
+
+# /sbin/sysctl -a | grep  net.ipv6.conf.all.accept_source_route
+net.ipv6.conf.all.accept_source_route=0
+
+If the returned lines do not have a value of "0", or a line is not returned, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72417">
+    <title>SRG-OS-000375-GPOS-00160</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87041r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-041001</version>
+      <title>The operating system must have the required packages for multifactor authentication installed.</title>
+      <description>&lt;VulnDiscussion&gt;Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
+
+Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
+
+A privileged account is defined as an information system account with authorizations of a privileged user.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+
+This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management).
+
+Requires further clarification from NIST.
+
+Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000375-GPOS-00161, SRG-OS-000375-GPOS-00162&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001948</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001953</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001954</ident>
+      <fixtext fixref="F-78769r3_fix">Configure the operating system to implement multifactor authentication by installing the required packages.
+
+Install the "esc", "pam_pkcs11", "authconfig", and "authconfig-gtk" packages on the system with the following command:
+
+# yum install esc pam_pkcs11 authconfig-gtk</fixtext>
+      <fix id="F-78769r3_fix"/>
+      <check system="C-72617r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system has the packages required for multifactor authentication installed.
+
+Check for the presence of the packages required to support multifactor authentication with the following commands:
+
+# yum list installed esc
+esc-1.1.0-26.el7.noarch.rpm
+
+# yum list installed pam_pkcs11
+pam_pkcs11-0.6.2-14.el7.noarch.rpm
+
+# yum list installed authconfig-gtk
+authconfig-gtk-6.1.12-19.el7.noarch.rpm
+
+If the "esc", "pam_pkcs11", and "authconfig-gtk" packages are not installed, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72427">
+    <title>SRG-OS-000375-GPOS-00160</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87051r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-041002</version>
+      <title>The operating system must implement multifactor authentication for access to privileged accounts via pluggable authentication modules (PAM).</title>
+      <description>&lt;VulnDiscussion&gt;Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
+
+Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
+
+A privileged account is defined as an information system account with authorizations of a privileged user.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+
+This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management).
+
+Requires further clarification from NIST.
+
+Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000375-GPOS-00161, SRG-OS-000375-GPOS-00162&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001948</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001953</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001954</ident>
+      <fixtext fixref="F-78779r2_fix">Configure the operating system to implement multifactor authentication for remote access to privileged accounts via pluggable authentication modules (PAM).
+
+Modify all of the services lines in /etc/sssd/sssd.conf to include pam.</fixtext>
+      <fix id="F-78779r2_fix"/>
+      <check system="C-72627r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system implements multifactor authentication for remote access to privileged accounts via pluggable authentication modules (PAM).
+
+Check the "/etc/sssd/sssd.conf" file for the authentication services that are being used with the following command:
+
+# grep services /etc/sssd/sssd.conf
+
+services = nss, pam
+
+If the "pam" service is not present, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72433">
+    <title>SRG-OS-000375-GPOS-00160</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87057r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-041003</version>
+      <title>The operating system must implement certificate status checking for PKI authentication.</title>
+      <description>&lt;VulnDiscussion&gt;Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
+
+Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
+
+A privileged account is defined as an information system account with authorizations of a privileged user.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+
+This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management).
+
+Requires further clarification from NIST.
+
+Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000375-GPOS-00161, SRG-OS-000375-GPOS-00162&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001948</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001953</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001954</ident>
+      <fixtext fixref="F-78785r3_fix">Configure the operating system to do certificate status checking for PKI authentication.
+
+Modify all of the "cert_policy" lines in "/etc/pam_pkcs11/pam_pkcs11.conf" to include "ocsp_on".</fixtext>
+      <fix id="F-78785r3_fix"/>
+      <check system="C-72633r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system implements certificate status checking for PKI authentication.
+
+Check to see if Online Certificate Status Protocol (OCSP) is enabled on the system with the following command:
+
+# grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf
+
+cert_policy =ca, ocsp_on, signature;
+cert_policy =ca, ocsp_on, signature;
+cert_policy =ca, ocsp_on, signature;
+
+There should be at least three lines returned. All lines must match the example output; specifically that "oscp_on" must be included in the "cert_policy" line.
+
+If "oscp_on" is present in all "cert_policy" lines, this is not a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-72435">
+    <title>SRG-OS-000375-GPOS-00160</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87059r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-041004</version>
+      <title>The operating system must implement smart card logons for multifactor authentication for access to privileged accounts.</title>
+      <description>&lt;VulnDiscussion&gt;Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.
+
+Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.
+
+A privileged account is defined as an information system account with authorizations of a privileged user.
+
+Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
+
+This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management).
+
+Requires further clarification from NIST.
+
+Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000375-GPOS-00161, SRG-OS-000375-GPOS-00162&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001948</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001953</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001954</ident>
+      <fixtext fixref="F-78787r2_fix">Configure the operating system to implement smart card logon for multifactor authentication to uniquely identify privileged users.
+
+Enable smart card logons with the following commands:
+
+#authconfig --enablesmartcard --smartcardaction=1 --update
+# authconfig --enablerequiresmartcard --update</fixtext>
+      <fix id="F-78787r2_fix"/>
+      <check system="C-72635r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system requires smart card logons for multifactor authentication to uniquely identify privileged users.
+
+Check to see if smartcard authentication is enforced on the system with the following command:
+
+# authconfig --test | grep -i smartcard
+
+The entry for use only smartcard for logon may be enabled, and the smartcard module and smartcard removal actions must not be blank.
+
+If smartcard authentication is disabled or the smartcard and smartcard removal actions are blank, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-73155">
+    <title>SRG-OS-000029-GPOS-00010</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87807r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010081</version>
+      <title>The operating system must set the lock delay setting  for all connection types.</title>
+      <description>&lt;VulnDiscussion&gt;A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
+
+The session lock is implemented at the point where session activity can be determined and/or controlled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000057</ident>
+      <fixtext fixref="F-79601r2_fix">Configure the operating system to prevent a user from overriding a screensaver lock after a 15-minute period of inactivity for graphical user interfaces.
+
+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: 
+
+Note: The example below is using the database "local" for the system, so if the system is using another database in "/etc/dconf/profile/user", the file should be created under the appropriate subdirectory.
+
+# touch /etc/dconf/db/local.d/locks/session
+
+Add the setting to lock the screensaver lock delay:
+
+/org/gnome/desktop/screensaver/lock-delay</fixtext>
+      <fix id="F-79601r2_fix"/>
+      <check system="C-73279r4_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system prevents a user from overriding a screensaver lock after a 15-minute period of inactivity for graphical user interfaces. 
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable. The screen program must be installed to lock sessions on the console.
+
+Determine which profile the system database is using with the following command:
+# grep system-db /etc/dconf/profile/user
+
+system-db:local
+
+Check for the lock delay setting with the following command:
+
+Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used.
+
+# grep -i lock-delay /etc/dconf/db/local.d/locks/*
+
+/org/gnome/desktop/screensaver/lock-delay
+
+If the command does not return a result, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-73157">
+    <title>SRG-OS-000029-GPOS-00010</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87809r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010082</version>
+      <title>The operating system must set the session idle delay setting for all connection types.</title>
+      <description>&lt;VulnDiscussion&gt;A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity, operating systems need to be able to identify when a user's session has idled and take action to initiate the session lock.
+
+The session lock is implemented at the point where session activity can be determined and/or controlled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000057</ident>
+      <fixtext fixref="F-79603r1_fix">Configure the operating system to prevent a user from overriding a session lock after a 15-minute period of inactivity for graphical user interfaces.
+
+Create a database to contain the system-wide screensaver settings (if it does not already exist) with the following command: 
+
+Note: The example below is using the database "local" for the system, so if the system is using another database in /etc/dconf/profile/user, the file should be created under the appropriate subdirectory.
+
+# touch /etc/dconf/db/local.d/locks/session
+
+Add the setting to lock the session idle delay:
+
+/org/gnome/desktop/session/idle-delay</fixtext>
+      <fix id="F-79603r1_fix"/>
+      <check system="C-73281r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system prevents a user from overriding session idle delay after a 15-minute period of inactivity for graphical user interfaces. The screen program must be installed to lock sessions on the console.
+
+Note: If the system does not have GNOME installed, this requirement is Not Applicable. 
+
+Determine which profile the system database is using with the following command:
+# grep system-db /etc/dconf/profile/user
+
+system-db:local
+
+Check for the session idle delay setting with the following command:
+
+Note: The example below is using the database "local" for the system, so the path is "/etc/dconf/db/local.d". This path must be modified if a database other than "local" is being used.
+
+# grep -i idle-delay /etc/dconf/db/local.d/locks/*
+
+/org/gnome/desktop/session/idle-delay
+
+If the command does not return a result, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-73159">
+    <title>SRG-OS-000069-GPOS-00037</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87811r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-010119</version>
+      <title>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 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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000192</ident>
+      <fixtext fixref="F-79605r1_fix">Configure the operating system to use "pwquality" to enforce password complexity rules.
+
+Add the following line to "/etc/pam.d/passwd" (or modify the line to have the required value):
+
+password    required    pam_pwquality.so retry=3</fixtext>
+      <fix id="F-79605r1_fix"/>
+      <check system="C-73283r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system uses "pwquality" to enforce the password complexity rules. 
+
+Check for the use of "pwquality" with the following command:
+
+# grep pwquality /etc/pam.d/passwd
+
+password    required    pam_pwquality.so retry=3
+
+If the command does not return a line containing the value "pam_pwquality.so", this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-73161">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87813r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-021021</version>
+      <title>File systems that are being imported via Network File System (NFS) must be mounted to prevent binary files from being executed.</title>
+      <description>&lt;VulnDiscussion&gt;The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-79607r1_fix">Configure the "/etc/fstab" to use the "noexec" option on file systems that are being exported via NFS.</fixtext>
+      <fix id="F-79607r1_fix"/>
+      <check system="C-73285r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify file systems that are being NFS exported are mounted with the "noexec" option.
+
+Find the file system(s) that contain the directories being exported with the following command:
+
+# more /etc/fstab | grep nfs
+
+UUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d    /store           nfs           rw,noexec                                                    0 0
+
+If a file system found in "/etc/fstab" refers to NFS and it does not have the "noexec" option set, and use of NFS exported binaries is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-73163">
+    <title>SRG-OS-000342-GPOS-00133</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87815r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030321</version>
+      <title>The audit system must take appropriate action when there is an error sending audit records to a remote system.</title>
+      <description>&lt;VulnDiscussion&gt;Taking appropriate action when there is an error sending audit records to a remote system will minimize the possibility of losing audit records.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001851</ident>
+      <fixtext fixref="F-79609r1_fix">Configure the action the operating system takes if there is an error sending audit records to a remote system.
+
+Uncomment the "network_failure_action" option in "/etc/audisp/audisp-remote.conf" and set it to "syslog", "single", or "halt".
+
+network_failure_action = single</fixtext>
+      <fix id="F-79609r1_fix"/>
+      <check system="C-73287r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the action the operating system takes if there is an error sending audit records to a remote system.
+
+Check the action that takes place if there is an error sending audit records to a remote system with the following command:
+
+# grep -i network_failure_action /etc/audisp/audisp-remote.conf
+network_failure_action = stop
+
+If the value of the "network_failure_action" option is not "syslog", "single", or "halt", or the line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-73165">
+    <title>SRG-OS-000004-GPOS-00004</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87817r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030871</version>
+      <title>The operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000018</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001403</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002130</ident>
+      <fixtext fixref="F-79611r3_fix">Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group".
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+
+-w /etc/group -p wa -k identity
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-79611r3_fix"/>
+      <check system="C-73289r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group".
+
+Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+
+# grep /etc/group /etc/audit/audit.rules
+
+-w /etc/group -p wa -k audit_rules_usergroup_modification
+
+If the command does not return a line, or the line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-73167">
+    <title>SRG-OS-000004-GPOS-00004</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87819r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030872</version>
+      <title>The operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000018</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001403</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002130</ident>
+      <fixtext fixref="F-79613r3_fix">Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow".
+
+Add or update the following rule in "/etc/audit/rules.d/audit.rules":
+
+-w /etc/gshadow -p wa -k identity
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-79613r3_fix"/>
+      <check system="C-73291r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow".
+
+Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+
+# grep /etc/gshadow /etc/audit/audit.rules
+
+-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
+
+If the command does not return a line, or the line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-73171">
+    <title>SRG-OS-000004-GPOS-00004</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87823r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030873</version>
+      <title>The operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000018</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001403</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002130</ident>
+      <fixtext fixref="F-79617r4_fix">Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.
+
+Add or update the following file system rule in "/etc/audit/rules.d/audit.rules":
+
+-w /etc/shadow -p wa -k identity
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-79617r4_fix"/>
+      <check system="C-73295r3_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.
+
+Check the auditing rules in "/etc/audit/audit.rules" with the following command:
+
+# grep /etc/shadow /etc/audit/audit.rules
+
+-w /etc/shadow -p wa -k audit_rules_usergroup_modification
+
+If the command does not return a line, or the line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-73173">
+    <title>SRG-OS-000004-GPOS-00004</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87825r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-030874</version>
+      <title>The operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd.</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 Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000018</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-000172</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001403</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002130</ident>
+      <fixtext fixref="F-79619r4_fix">Configure the operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd.
+
+Add or update the following file system rule in "/etc/audit/rules.d/audit.rules":
+
+-w /etc/opasswd -p wa -k identity
+
+The audit daemon must be restarted for the changes to take effect.</fixtext>
+      <fix id="F-79619r4_fix"/>
+      <check system="C-73297r2_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd.
+
+Check the auditing rules in "/etc/audit/rules.d/audit.rules" with the following command:
+
+# grep /etc/opasswd /etc/audit/rules.d/audit.rules
+
+-w /etc/opasswd -p wa -k audit_rules_usergroup_modification
+
+If the command does not return a line, or the line is commented out, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-73175">
+    <title>SRG-OS-000480-GPOS-00227</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87827r2_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-040641</version>
+      <title>The system must ignore Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages.</title>
+      <description>&lt;VulnDiscussion&gt;ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-000366</ident>
+      <fixtext fixref="F-79621r2_fix">Set the system to ignore IPv4 ICMP redirect messages by adding the following line to "/etc/sysctl.conf" (or modify the line to have the required value):
+
+net.ipv4.conf.all.accept_redirects = 0</fixtext>
+      <fix id="F-79621r2_fix"/>
+      <check system="C-73299r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify the system ignores IPv4 ICMP redirect messages.
+
+Check the value of the "accept_redirects" variables with the following command:
+
+# /sbin/sysctl -a | grep  'net.ipv4.conf.all.accept_redirects'
+
+net.ipv4.conf.all.accept_redirects=0
+
+If both of the returned lines do not have a value of "0", or a line is not returned, this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+  <Group id="V-73177">
+    <title>SRG-OS-000424-GPOS-00188</title>
+    <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+    <Rule id="SV-87829r1_rule" severity="medium" weight="10.0">
+      <version>RHEL-07-041010</version>
+      <title>Wireless network adapters must be disabled.</title>
+      <description>&lt;VulnDiscussion&gt;The use of wireless networking can introduce many different attack vectors into the organization's network. Common attack vectors such as malicious association and ad hoc networks will allow an attacker to spoof a wireless access point (AP), allowing validated systems to connect to the malicious AP and enabling the attacker to monitor and record network traffic. These malicious APs can also serve to create a man-in-the-middle attack or be used to create a denial of service to valid network resources.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+      <reference>
+        <dc:title>DPMS Target Red Hat 7</dc:title>
+        <dc:publisher>DISA</dc:publisher>
+        <dc:type>DPMS Target</dc:type>
+        <dc:subject>Red Hat 7</dc:subject>
+        <dc:identifier>2777</dc:identifier>
+      </reference>
+      <ident system="http://iase.disa.mil/cci">CCI-001443</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-001444</ident>
+      <ident system="http://iase.disa.mil/cci">CCI-002418</ident>
+      <fixtext fixref="F-79623r1_fix">Configure the system to disable all wireless network interfaces with the following command:
+
+#nmcli radio wifi off</fixtext>
+      <fix id="F-79623r1_fix"/>
+      <check system="C-73301r1_chk">
+        <check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml"/>
+        <check-content>Verify that there are no wireless interfaces configured on the system.
+
+This is N/A for systems that do not have wireless network adapters.
+
+Check for the presence of active wireless interfaces with the following command:
+
+# nmcli device
+DEVICE TYPE STATE
+eth0 ethernet connected
+wlp3s0 wifi disconnected
+lo loopback unmanaged
+
+If a wireless interface is configured and its use on the system is not documented with the Information System Security Officer (ISSO), this is a finding.</check-content>
+      </check>
+    </Rule>
+  </Group>
+</Benchmark>
diff --git a/doc/metadata/rhel7/RHEL-07-010031.rst b/doc/metadata/rhel7/RHEL-07-010031.rst
deleted file mode 100644
index 7a00ac23..00000000
--- a/doc/metadata/rhel7/RHEL-07-010031.rst
+++ /dev/null
@@ -1,9 +0,0 @@
----
-id: RHEL-07-010031
-status: implemented
-tag: graphical
----
-
-This STIG control is implemented by:
-
-* :ref:`stig-RHEL-07-010030`
diff --git a/doc/metadata/rhel7/RHEL-07-010070.rst b/doc/metadata/rhel7/RHEL-07-010070.rst
deleted file mode 100644
index e25f0d16..00000000
--- a/doc/metadata/rhel7/RHEL-07-010070.rst
+++ /dev/null
@@ -1,15 +0,0 @@
----
-id: RHEL-07-010070
-status: implemented
-tag: graphical
----
-
-The session inactivity timeout is set to 900 seconds to meet the STIG
-requirements. After this time, users must re-enter their credentials to regain
-access to the system.
-
-Deployers can adjust this timeout by setting an Ansible variable:
-
-.. code-block:: yaml
-
-    security_lock_session_inactive_delay: 900
diff --git a/doc/metadata/rhel7/RHEL-07-010071.rst b/doc/metadata/rhel7/RHEL-07-010071.rst
deleted file mode 100644
index 40f85b5e..00000000
--- a/doc/metadata/rhel7/RHEL-07-010071.rst
+++ /dev/null
@@ -1,15 +0,0 @@
----
-id: RHEL-07-010071
-status: implemented
-tag: graphical
----
-
-The STIG does not allow regular users to override the system-wide settings for
-graphical session locks. These settings are locked out by default.
-
-Deployers can opt out of overriding user settings for session locks by setting
-the following Ansible variable:
-
-.. code-block:: yaml
-
-    security_lock_session_override_user: no
diff --git a/doc/metadata/rhel7/RHEL-07-010373.rst b/doc/metadata/rhel7/RHEL-07-010373.rst
deleted file mode 100644
index c4953da9..00000000
--- a/doc/metadata/rhel7/RHEL-07-010373.rst
+++ /dev/null
@@ -1,9 +0,0 @@
----
-id: RHEL-07-010373
-status: opt-in - Red Hat Only
-tag: auth
----
-
-This STIG control is implemented by:
-
-* :ref:`stig-RHEL-07-010371`
diff --git a/doc/metadata/rhel7/RHEL-07-010400.rst b/doc/metadata/rhel7/RHEL-07-010400.rst
deleted file mode 100644
index 0e8c4118..00000000
--- a/doc/metadata/rhel7/RHEL-07-010400.rst
+++ /dev/null
@@ -1,14 +0,0 @@
----
-id: RHEL-07-010400
-status: implemented
-tag: auth
----
-
-The ``memcache_timeout`` setting is set to ``86400`` (86400 seconds = 1 day)
-within the ``[nss]`` section of ``/etc/sssd/sssd.conf``. Deployers can choose a
-different timeout for cached nss authenticators by setting the following
-Ansible variable:
-
-.. code-block:: yaml
-
-    security_nss_cached_authenticator_timeout: 86400
diff --git a/doc/metadata/rhel7/RHEL-07-010401.rst b/doc/metadata/rhel7/RHEL-07-010401.rst
deleted file mode 100644
index bc696fbf..00000000
--- a/doc/metadata/rhel7/RHEL-07-010401.rst
+++ /dev/null
@@ -1,14 +0,0 @@
----
-id: RHEL-07-010401
-status: implemented
-tag: auth
----
-
-The ``offline_credentials_expiration`` configuration is set to ``1`` in
-``/etc/sssd/sssd.conf``, which causes credentials to expire after one day.
-Deployers can adjust this expiration time by setting the following Ansible
-variable:
-
-.. code-block:: yaml
-
-    security_pam_offline_credentials_expiration_days: 1
diff --git a/doc/metadata/rhel7/RHEL-07-010440.rst b/doc/metadata/rhel7/RHEL-07-010440.rst
deleted file mode 100644
index 2cd64428..00000000
--- a/doc/metadata/rhel7/RHEL-07-010440.rst
+++ /dev/null
@@ -1,8 +0,0 @@
----
-id: RHEL-07-010440
-status: implemented
-tag: sshd
----
-
-The tasks for :ref:`stig-RHEL-07-010270` disable logins for accounts with empty
-passwords. No other action is needed for this STIG requirement.
diff --git a/doc/metadata/rhel7/RHEL-07-010470.rst b/doc/metadata/rhel7/RHEL-07-010470.rst
deleted file mode 100644
index e41ea284..00000000
--- a/doc/metadata/rhel7/RHEL-07-010470.rst
+++ /dev/null
@@ -1,10 +0,0 @@
----
-id: RHEL-07-010470
-status: opt-in
-tag: misc
----
-
-The tasks in the security role for RHEL-07-010460 will also apply changes to
-systems that use UEFI. For more details, refer to the following documentation:
-
-* :ref:`stig-RHEL-07-010460`
diff --git a/doc/metadata/rhel7/RHEL-07-010490.rst b/doc/metadata/rhel7/RHEL-07-010490.rst
deleted file mode 100644
index b889eb14..00000000
--- a/doc/metadata/rhel7/RHEL-07-010490.rst
+++ /dev/null
@@ -1,10 +0,0 @@
----
-id: RHEL-07-010490
-status: exception - manual intervention
-tag: auth
----
-
-Deployers are strongly urged to review the list of user accounts on each server
-regularly. Evaluation of user accounts must be done on a case-by-case basis and
-the tasks in the security role are unable to determine which user accounts are
-valid. Deployers must complete this work manually.
diff --git a/doc/metadata/rhel7/RHEL-07-020170.rst b/doc/metadata/rhel7/RHEL-07-020170.rst
deleted file mode 100644
index 70251fcc..00000000
--- a/doc/metadata/rhel7/RHEL-07-020170.rst
+++ /dev/null
@@ -1,9 +0,0 @@
----
-id: RHEL-07-020170
-status: exception - manual intervention
-tag: misc
----
-
-Deployers should consider the best encryption strategy for their needs and add
-that to the initial provisioning process. The tasks in the security role do not
-apply encryption to disks or individual files.
diff --git a/doc/metadata/rhel7/RHEL-07-020870.rst b/doc/metadata/rhel7/RHEL-07-020870.rst
deleted file mode 100644
index 8af8a844..00000000
--- a/doc/metadata/rhel7/RHEL-07-020870.rst
+++ /dev/null
@@ -1,8 +0,0 @@
----
-id: RHEL-07-020870
-status: exception - manual intervention
-tag: misc
----
-
-Deployers should manually inspect initialization files in each user's home
-directory and verify that all ``PATH`` lines use absolute paths.
diff --git a/doc/metadata/rhel7/RHEL-07-040020.rst b/doc/metadata/rhel7/RHEL-07-040020.rst
deleted file mode 100644
index de55c597..00000000
--- a/doc/metadata/rhel7/RHEL-07-040020.rst
+++ /dev/null
@@ -1,10 +0,0 @@
----
-id: RHEL-07-040020
-status: exception - manual intervention
-tag: misc
----
-
-Deployers should review their logging configuration to ensure it meets the
-requirements of the STIG. All operating systems supported by the role already
-log the ``auth``, ``authpriv``, and ``daemon`` facilities at the correct levels
-by default.
diff --git a/doc/metadata/rhel7/RHEL-07-040030.rst b/doc/metadata/rhel7/RHEL-07-040030.rst
deleted file mode 100644
index 8effdb52..00000000
--- a/doc/metadata/rhel7/RHEL-07-040030.rst
+++ /dev/null
@@ -1,13 +0,0 @@
----
-id: RHEL-07-040030
-status: verification only
-tag: auth
----
-
-The tasks in the security role examine the ``/etc/pam_pkcs11/pam_pkcs11.conf``
-file (if it exists) to ensure that ``ocsp_on`` is included in all three
-``cert_policy`` directives. If ``oscp_on`` is not found three times in the
-file, a message is printed in the Ansible output.
-
-This change is only needed on systems which use PKI-based authentication (using
-certificates).
diff --git a/doc/metadata/rhel7/RHEL-07-040040.rst b/doc/metadata/rhel7/RHEL-07-040040.rst
deleted file mode 100644
index f50c0ab9..00000000
--- a/doc/metadata/rhel7/RHEL-07-040040.rst
+++ /dev/null
@@ -1,12 +0,0 @@
----
-id: RHEL-07-040040
-status: verification only
-tag: auth
----
-
-The tasks in the security role check for ``cackey`` or ``coolkey`` as
-acceptable values for ``use_pkcs11_module`` in
-``/etc/pam_pkcs11/pam_pkcs11.conf``. If neither are found, a message is printed
-in the Ansible output.
-
-This change only applies to systems that use PKI-based authentication.
diff --git a/doc/metadata/rhel7/RHEL-07-040050.rst b/doc/metadata/rhel7/RHEL-07-040050.rst
deleted file mode 100644
index f3d87671..00000000
--- a/doc/metadata/rhel7/RHEL-07-040050.rst
+++ /dev/null
@@ -1,11 +0,0 @@
----
-id: RHEL-07-040050
-status: exception - manual intervention
-tag: file_perms
----
-
-This control requires that ``/etc/pam_pkcs11/subject_mapping`` exists on the
-system. It is only required on systems that use PKI-based authentication.
-
-Deployers should perform this step manually based on the needs of their
-authentication configuration.
diff --git a/doc/metadata/rhel7/RHEL-07-040060.rst b/doc/metadata/rhel7/RHEL-07-040060.rst
deleted file mode 100644
index 554d2c32..00000000
--- a/doc/metadata/rhel7/RHEL-07-040060.rst
+++ /dev/null
@@ -1,9 +0,0 @@
----
-id: RHEL-07-040060
-status: implemented
-tag: file_perms
----
-
-The tasks in this role set the mode on ``/etc/pam_pkcs11/cn_map`` to ``0644``.
-If the file permissions are more restrictive than ``0644`` on the system, they
-are not changed.
diff --git a/doc/metadata/rhel7/RHEL-07-040070.rst b/doc/metadata/rhel7/RHEL-07-040070.rst
deleted file mode 100644
index d51db937..00000000
--- a/doc/metadata/rhel7/RHEL-07-040070.rst
+++ /dev/null
@@ -1,8 +0,0 @@
----
-id: RHEL-07-040070
-status: implemented
-tag: file_perms
----
-
-The default owner for ``/etc/pam_pkcs11/cn_map`` is ``root``. The role ensures
-that this default is maintained if the file exists.
diff --git a/doc/metadata/rhel7/RHEL-07-040080.rst b/doc/metadata/rhel7/RHEL-07-040080.rst
deleted file mode 100644
index 687ee3f6..00000000
--- a/doc/metadata/rhel7/RHEL-07-040080.rst
+++ /dev/null
@@ -1,8 +0,0 @@
----
-id: RHEL-07-040080
-status: implemented
-tag: file_perms
----
-
-The default group owner for ``/etc/pam_pkcs11/cn_map`` is ``root``. The role
-ensures that this default is maintained if the file exists.
diff --git a/doc/metadata/rhel7/RHEL-07-040230.rst b/doc/metadata/rhel7/RHEL-07-040230.rst
deleted file mode 100644
index 8d300424..00000000
--- a/doc/metadata/rhel7/RHEL-07-040230.rst
+++ /dev/null
@@ -1,17 +0,0 @@
----
-id: RHEL-07-040230
-status: exception - manual intervention
-tag: misc
----
-
-This control applies only to systems that run PKI services, such as the
-`FreeIPA <https://www.freeipa.org/page/Main_Page>`_ project or the
-`Red Hat Identity Management <https://access.redhat.com/products/identity-management>`_
-product. Deployers should carefully review the requirements for this control
-before making any changes.
-
-.. warning::
-
-    Changing revocation settings might cause certain systems or users to lose
-    access to critical servers. Always test these configuration changes in a
-    non-production environment first.
diff --git a/doc/metadata/rhel7/RHEL-07-040333.rst b/doc/metadata/rhel7/RHEL-07-040333.rst
deleted file mode 100644
index f7d53218..00000000
--- a/doc/metadata/rhel7/RHEL-07-040333.rst
+++ /dev/null
@@ -1,7 +0,0 @@
----
-id: RHEL-07-040333
-status: implemented
-tag: sshd
----
-
-This STIG is already applied by the changes for :ref:`stig-RHEL-07-040332`.
diff --git a/doc/metadata/rhel7/RHEL-07-040490.rst b/doc/metadata/rhel7/RHEL-07-040490.rst
deleted file mode 100644
index ac946396..00000000
--- a/doc/metadata/rhel7/RHEL-07-040490.rst
+++ /dev/null
@@ -1,14 +0,0 @@
----
-id: RHEL-07-040490
-status: implemented
-tag: packages
----
-
-If a TFTP server package is installed (``tftpd`` on Ubuntu and ``tftp-server``
-on CentOS and Red Hat Enterprise Linux), the package is removed.
-
-Deployers can opt out of this change by setting the following Ansible variable:
-
-.. code-block:: yaml
-
-    security_rhel7_remove_tftp_server: no
diff --git a/doc/metadata/rhel7/RHEL-07-040810.rst b/doc/metadata/rhel7/RHEL-07-040810.rst
deleted file mode 100644
index c4bf4c82..00000000
--- a/doc/metadata/rhel7/RHEL-07-040810.rst
+++ /dev/null
@@ -1,10 +0,0 @@
----
-id: RHEL-07-040810
-status: opt-in
-tag: misc
----
-
-The ``firewalld`` service is optionally enabled in the tasks for another STIG
-control:
-
-* :ref:`stig-RHEL-07-040290`
diff --git a/doc/metadata/rhel7/RHEL-07-010010.rst b/doc/metadata/rhel7/V-71849.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-010010.rst
rename to doc/metadata/rhel7/V-71849.rst
index 3cea70f8..4ebc58f5 100644
--- a/doc/metadata/rhel7/RHEL-07-010010.rst
+++ b/doc/metadata/rhel7/V-71849.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010010
+id: V-71849
 status: opt-in
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010020.rst b/doc/metadata/rhel7/V-71855.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-010020.rst
rename to doc/metadata/rhel7/V-71855.rst
index 20bf16c3..0fc331cc 100644
--- a/doc/metadata/rhel7/RHEL-07-010020.rst
+++ b/doc/metadata/rhel7/V-71855.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010020
+id: V-71855
 status: implemented
 tag: packages
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010030.rst b/doc/metadata/rhel7/V-71859.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-010030.rst
rename to doc/metadata/rhel7/V-71859.rst
index fb184164..d1d6fc7b 100644
--- a/doc/metadata/rhel7/RHEL-07-010030.rst
+++ b/doc/metadata/rhel7/V-71859.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010030
+id: V-71859
 status: implemented
 tag: graphical
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010040.rst b/doc/metadata/rhel7/V-71861.rst
similarity index 68%
rename from doc/metadata/rhel7/RHEL-07-010040.rst
rename to doc/metadata/rhel7/V-71861.rst
index e13dee24..8aee5f10 100644
--- a/doc/metadata/rhel7/RHEL-07-010040.rst
+++ b/doc/metadata/rhel7/V-71861.rst
@@ -1,9 +1,9 @@
 ---
-id: RHEL-07-010040
+id: V-71861
 status: implemented
 tag: sshd
 ---
 
 This control is implemented by the tasks for another control:
 
-* :ref:`stig-RHEL-07-040170`
+* :ref:`stig-V-72225`
diff --git a/doc/metadata/rhel7/V-71863.rst b/doc/metadata/rhel7/V-71863.rst
new file mode 100644
index 00000000..70d01204
--- /dev/null
+++ b/doc/metadata/rhel7/V-71863.rst
@@ -0,0 +1,9 @@
+---
+id: V-71863
+status: implemented
+tag: misc
+---
+
+The STIG requires a standardized login banner for all command line user logins.
+The security role deploys a default banner from ``files/login_banner.txt`` to
+``/etc/issue`` on the system.
diff --git a/doc/metadata/rhel7/RHEL-07-010060.rst b/doc/metadata/rhel7/V-71891.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-010060.rst
rename to doc/metadata/rhel7/V-71891.rst
index fcab7b86..d8dc9d25 100644
--- a/doc/metadata/rhel7/RHEL-07-010060.rst
+++ b/doc/metadata/rhel7/V-71891.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010060
+id: V-71891
 status: implemented
 tag: graphical
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010073.rst b/doc/metadata/rhel7/V-71893.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-010073.rst
rename to doc/metadata/rhel7/V-71893.rst
index bfbf3583..7a854aec 100644
--- a/doc/metadata/rhel7/RHEL-07-010073.rst
+++ b/doc/metadata/rhel7/V-71893.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010073
+id: V-71893
 status: implemented
 tag: graphical
 ---
diff --git a/doc/metadata/rhel7/V-71895.rst b/doc/metadata/rhel7/V-71895.rst
new file mode 100644
index 00000000..81a49318
--- /dev/null
+++ b/doc/metadata/rhel7/V-71895.rst
@@ -0,0 +1,10 @@
+---
+id: V-71895
+status: implemented
+tag: file_perms
+---
+
+This control is implemented by the tasks for another control. Refer to the
+documentation for more details on the change and how to opt out:
+
+* :ref:`stig-V-71893`
diff --git a/doc/metadata/rhel7/RHEL-07-010072.rst b/doc/metadata/rhel7/V-71897.rst
similarity index 84%
rename from doc/metadata/rhel7/RHEL-07-010072.rst
rename to doc/metadata/rhel7/V-71897.rst
index 09860367..e302ee99 100644
--- a/doc/metadata/rhel7/RHEL-07-010072.rst
+++ b/doc/metadata/rhel7/V-71897.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010072
+id: V-71897
 status: implemented
 tag: packages
 ---
diff --git a/doc/metadata/rhel7/V-71899.rst b/doc/metadata/rhel7/V-71899.rst
new file mode 100644
index 00000000..674166dd
--- /dev/null
+++ b/doc/metadata/rhel7/V-71899.rst
@@ -0,0 +1,10 @@
+---
+id: V-71899
+status: implemented
+tag: file_perms
+---
+
+This control is implemented by the tasks for another control. Refer to the
+documentation for more details on the change and how to opt out:
+
+* :ref:`stig-V-71893`
diff --git a/doc/metadata/rhel7/RHEL-07-010074.rst b/doc/metadata/rhel7/V-71901.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-010074.rst
rename to doc/metadata/rhel7/V-71901.rst
index e79aa772..39cb3c56 100644
--- a/doc/metadata/rhel7/RHEL-07-010074.rst
+++ b/doc/metadata/rhel7/V-71901.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010074
+id: V-71901
 status: implemented
 tag: graphical
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010090.rst b/doc/metadata/rhel7/V-71903.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-010090.rst
rename to doc/metadata/rhel7/V-71903.rst
index b2389dea..b02da8a9 100644
--- a/doc/metadata/rhel7/RHEL-07-010090.rst
+++ b/doc/metadata/rhel7/V-71903.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010090
+id: V-71903
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010100.rst b/doc/metadata/rhel7/V-71905.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-010100.rst
rename to doc/metadata/rhel7/V-71905.rst
index 791410db..a1d9d0f3 100644
--- a/doc/metadata/rhel7/RHEL-07-010100.rst
+++ b/doc/metadata/rhel7/V-71905.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010100
+id: V-71905
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010110.rst b/doc/metadata/rhel7/V-71907.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-010110.rst
rename to doc/metadata/rhel7/V-71907.rst
index 03f48bf4..e5dec7f0 100644
--- a/doc/metadata/rhel7/RHEL-07-010110.rst
+++ b/doc/metadata/rhel7/V-71907.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010110
+id: V-71907
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010120.rst b/doc/metadata/rhel7/V-71909.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-010120.rst
rename to doc/metadata/rhel7/V-71909.rst
index 8fdd678b..ca2d3509 100644
--- a/doc/metadata/rhel7/RHEL-07-010120.rst
+++ b/doc/metadata/rhel7/V-71909.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010120
+id: V-71909
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010130.rst b/doc/metadata/rhel7/V-71911.rst
similarity index 98%
rename from doc/metadata/rhel7/RHEL-07-010130.rst
rename to doc/metadata/rhel7/V-71911.rst
index 14cb8e6d..7ee48ed2 100644
--- a/doc/metadata/rhel7/RHEL-07-010130.rst
+++ b/doc/metadata/rhel7/V-71911.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010130
+id: V-71911
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010140.rst b/doc/metadata/rhel7/V-71913.rst
similarity index 98%
rename from doc/metadata/rhel7/RHEL-07-010140.rst
rename to doc/metadata/rhel7/V-71913.rst
index cd699b57..f139562c 100644
--- a/doc/metadata/rhel7/RHEL-07-010140.rst
+++ b/doc/metadata/rhel7/V-71913.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010140
+id: V-71913
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010150.rst b/doc/metadata/rhel7/V-71915.rst
similarity index 98%
rename from doc/metadata/rhel7/RHEL-07-010150.rst
rename to doc/metadata/rhel7/V-71915.rst
index b178bc52..57d60d5a 100644
--- a/doc/metadata/rhel7/RHEL-07-010150.rst
+++ b/doc/metadata/rhel7/V-71915.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010150
+id: V-71915
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010160.rst b/doc/metadata/rhel7/V-71917.rst
similarity index 98%
rename from doc/metadata/rhel7/RHEL-07-010160.rst
rename to doc/metadata/rhel7/V-71917.rst
index 4f3f290d..af0bb97b 100644
--- a/doc/metadata/rhel7/RHEL-07-010160.rst
+++ b/doc/metadata/rhel7/V-71917.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010160
+id: V-71917
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010170.rst b/doc/metadata/rhel7/V-71919.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-010170.rst
rename to doc/metadata/rhel7/V-71919.rst
index 79240eab..6399a7df 100644
--- a/doc/metadata/rhel7/RHEL-07-010170.rst
+++ b/doc/metadata/rhel7/V-71919.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010170
+id: V-71919
 status: implemented
 tag: implemented
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010180.rst b/doc/metadata/rhel7/V-71921.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-010180.rst
rename to doc/metadata/rhel7/V-71921.rst
index c274d69c..790ae0a3 100644
--- a/doc/metadata/rhel7/RHEL-07-010180.rst
+++ b/doc/metadata/rhel7/V-71921.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010180
+id: V-71921
 status: implemented
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010190.rst b/doc/metadata/rhel7/V-71923.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-010190.rst
rename to doc/metadata/rhel7/V-71923.rst
index 665d98ed..8698b1c3 100644
--- a/doc/metadata/rhel7/RHEL-07-010190.rst
+++ b/doc/metadata/rhel7/V-71923.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010190
+id: V-71923
 status: implemented - red hat only
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010200.rst b/doc/metadata/rhel7/V-71925.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-010200.rst
rename to doc/metadata/rhel7/V-71925.rst
index 7b12d8c9..63771e3c 100644
--- a/doc/metadata/rhel7/RHEL-07-010200.rst
+++ b/doc/metadata/rhel7/V-71925.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010200
+id: V-71925
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010210.rst b/doc/metadata/rhel7/V-71927.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-010210.rst
rename to doc/metadata/rhel7/V-71927.rst
index f6434158..93b563c7 100644
--- a/doc/metadata/rhel7/RHEL-07-010210.rst
+++ b/doc/metadata/rhel7/V-71927.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010210
+id: V-71927
 status: implemented
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010220.rst b/doc/metadata/rhel7/V-71929.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-010220.rst
rename to doc/metadata/rhel7/V-71929.rst
index 9408db58..c3280a0e 100644
--- a/doc/metadata/rhel7/RHEL-07-010220.rst
+++ b/doc/metadata/rhel7/V-71929.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010220
+id: V-71929
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010230.rst b/doc/metadata/rhel7/V-71931.rst
similarity index 91%
rename from doc/metadata/rhel7/RHEL-07-010230.rst
rename to doc/metadata/rhel7/V-71931.rst
index 9dc442a5..4b91df29 100644
--- a/doc/metadata/rhel7/RHEL-07-010230.rst
+++ b/doc/metadata/rhel7/V-71931.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010230
+id: V-71931
 status: implemented
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010240.rst b/doc/metadata/rhel7/V-71933.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-010240.rst
rename to doc/metadata/rhel7/V-71933.rst
index 41cc9036..39e384cb 100644
--- a/doc/metadata/rhel7/RHEL-07-010240.rst
+++ b/doc/metadata/rhel7/V-71933.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010240
+id: V-71933
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010250.rst b/doc/metadata/rhel7/V-71935.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-010250.rst
rename to doc/metadata/rhel7/V-71935.rst
index 4cbcf90d..df2a3d13 100644
--- a/doc/metadata/rhel7/RHEL-07-010250.rst
+++ b/doc/metadata/rhel7/V-71935.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010250
+id: V-71935
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010260.rst b/doc/metadata/rhel7/V-71937.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-010260.rst
rename to doc/metadata/rhel7/V-71937.rst
index 53778eda..54ddead3 100644
--- a/doc/metadata/rhel7/RHEL-07-010260.rst
+++ b/doc/metadata/rhel7/V-71937.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010260
+id: V-71937
 status: implemented
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010270.rst b/doc/metadata/rhel7/V-71939.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-010270.rst
rename to doc/metadata/rhel7/V-71939.rst
index 6d038fc7..b10b1255 100644
--- a/doc/metadata/rhel7/RHEL-07-010270.rst
+++ b/doc/metadata/rhel7/V-71939.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010270
+id: V-71939
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010280.rst b/doc/metadata/rhel7/V-71941.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-010280.rst
rename to doc/metadata/rhel7/V-71941.rst
index e8482f2f..0a783cf5 100644
--- a/doc/metadata/rhel7/RHEL-07-010280.rst
+++ b/doc/metadata/rhel7/V-71941.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010280
+id: V-71941
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010372.rst b/doc/metadata/rhel7/V-71943.rst
similarity index 64%
rename from doc/metadata/rhel7/RHEL-07-010372.rst
rename to doc/metadata/rhel7/V-71943.rst
index 6b93c717..b4faff8a 100644
--- a/doc/metadata/rhel7/RHEL-07-010372.rst
+++ b/doc/metadata/rhel7/V-71943.rst
@@ -1,9 +1,9 @@
 ---
-id: RHEL-07-010372
+id: V-71943
 status: opt-in - Red Hat Only
 tag: auth
 ---
 
 This STIG control is implemented by:
 
-* :ref:`stig-RHEL-07-010371`
+* :ref:`stig-V-71945`
diff --git a/doc/metadata/rhel7/RHEL-07-010371.rst b/doc/metadata/rhel7/V-71945.rst
similarity index 98%
rename from doc/metadata/rhel7/RHEL-07-010371.rst
rename to doc/metadata/rhel7/V-71945.rst
index 485f1a34..e053a7f9 100644
--- a/doc/metadata/rhel7/RHEL-07-010371.rst
+++ b/doc/metadata/rhel7/V-71945.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010371
+id: V-71945
 status: opt-in - Red Hat Only
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010380.rst b/doc/metadata/rhel7/V-71947.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-010380.rst
rename to doc/metadata/rhel7/V-71947.rst
index 0bfbbde1..bda50cf5 100644
--- a/doc/metadata/rhel7/RHEL-07-010380.rst
+++ b/doc/metadata/rhel7/V-71947.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010380
+id: V-71947
 status: exception - manual intervention
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010381.rst b/doc/metadata/rhel7/V-71949.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-010381.rst
rename to doc/metadata/rhel7/V-71949.rst
index 89660d97..ea4d82a6 100644
--- a/doc/metadata/rhel7/RHEL-07-010381.rst
+++ b/doc/metadata/rhel7/V-71949.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010381
+id: V-71949
 status: exception - manual intervention
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010420.rst b/doc/metadata/rhel7/V-71951.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-010420.rst
rename to doc/metadata/rhel7/V-71951.rst
index a4fb5052..37ef24d1 100644
--- a/doc/metadata/rhel7/RHEL-07-010420.rst
+++ b/doc/metadata/rhel7/V-71951.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010420
+id: V-71951
 status: implemented
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010430.rst b/doc/metadata/rhel7/V-71953.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-010430.rst
rename to doc/metadata/rhel7/V-71953.rst
index ee6d1382..62e6df7e 100644
--- a/doc/metadata/rhel7/RHEL-07-010430.rst
+++ b/doc/metadata/rhel7/V-71953.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010430
+id: V-71953
 status: implemented
 tag: graphical
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010431.rst b/doc/metadata/rhel7/V-71955.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-010431.rst
rename to doc/metadata/rhel7/V-71955.rst
index 03896edb..e6a694c8 100644
--- a/doc/metadata/rhel7/RHEL-07-010431.rst
+++ b/doc/metadata/rhel7/V-71955.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010431
+id: V-71955
 status: implemented
 tag: graphical
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010441.rst b/doc/metadata/rhel7/V-71957.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-010441.rst
rename to doc/metadata/rhel7/V-71957.rst
index 1a9dd73f..be95d9a6 100644
--- a/doc/metadata/rhel7/RHEL-07-010441.rst
+++ b/doc/metadata/rhel7/V-71957.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010441
+id: V-71957
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010442.rst b/doc/metadata/rhel7/V-71959.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-010442.rst
rename to doc/metadata/rhel7/V-71959.rst
index 18b0f359..65e58ad6 100644
--- a/doc/metadata/rhel7/RHEL-07-010442.rst
+++ b/doc/metadata/rhel7/V-71959.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010442
+id: V-71959
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010460.rst b/doc/metadata/rhel7/V-71961.rst
similarity index 98%
rename from doc/metadata/rhel7/RHEL-07-010460.rst
rename to doc/metadata/rhel7/V-71961.rst
index 5c8af522..a49522e0 100644
--- a/doc/metadata/rhel7/RHEL-07-010460.rst
+++ b/doc/metadata/rhel7/V-71961.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010460
+id: V-71961
 status: opt-in
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/V-71963.rst b/doc/metadata/rhel7/V-71963.rst
new file mode 100644
index 00000000..06061782
--- /dev/null
+++ b/doc/metadata/rhel7/V-71963.rst
@@ -0,0 +1,10 @@
+---
+id: V-71963
+status: opt-in
+tag: misc
+---
+
+The tasks in the security role for V-71961 will also apply changes to
+systems that use UEFI. For more details, refer to the following documentation:
+
+* :ref:`stig-V-71961`
diff --git a/doc/metadata/rhel7/RHEL-07-010500.rst b/doc/metadata/rhel7/V-71965.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-010500.rst
rename to doc/metadata/rhel7/V-71965.rst
index dfb6dd6f..7943e079 100644
--- a/doc/metadata/rhel7/RHEL-07-010500.rst
+++ b/doc/metadata/rhel7/V-71965.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-010500
+id: V-71965
 status: exception - manual intervention
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020000.rst b/doc/metadata/rhel7/V-71967.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-020000.rst
rename to doc/metadata/rhel7/V-71967.rst
index 221956cf..ec5410c3 100644
--- a/doc/metadata/rhel7/RHEL-07-020000.rst
+++ b/doc/metadata/rhel7/V-71967.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020000
+id: V-71967
 status: implemented
 tag: packages
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020010.rst b/doc/metadata/rhel7/V-71969.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-020010.rst
rename to doc/metadata/rhel7/V-71969.rst
index bb83d0d4..46c54643 100644
--- a/doc/metadata/rhel7/RHEL-07-020010.rst
+++ b/doc/metadata/rhel7/V-71969.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020010
+id: V-71969
 status: implemented
 tag: packages
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020090.rst b/doc/metadata/rhel7/V-71971.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-020090.rst
rename to doc/metadata/rhel7/V-71971.rst
index a69c8342..6cd03017 100644
--- a/doc/metadata/rhel7/RHEL-07-020090.rst
+++ b/doc/metadata/rhel7/V-71971.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020090
+id: V-71971
 status: exception - manual intervention
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020130.rst b/doc/metadata/rhel7/V-71973.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-020130.rst
rename to doc/metadata/rhel7/V-71973.rst
index 23b77d64..78ae265e 100644
--- a/doc/metadata/rhel7/RHEL-07-020130.rst
+++ b/doc/metadata/rhel7/V-71973.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020130
+id: V-71973
 status: opt-in
 tag: aide
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020140.rst b/doc/metadata/rhel7/V-71975.rst
similarity index 87%
rename from doc/metadata/rhel7/RHEL-07-020140.rst
rename to doc/metadata/rhel7/V-71975.rst
index 2ea69d09..997d5e36 100644
--- a/doc/metadata/rhel7/RHEL-07-020140.rst
+++ b/doc/metadata/rhel7/V-71975.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020140
+id: V-71975
 status: implemented
 tag: aide
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020150.rst b/doc/metadata/rhel7/V-71977.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-020150.rst
rename to doc/metadata/rhel7/V-71977.rst
index d6d3b89a..9d272408 100644
--- a/doc/metadata/rhel7/RHEL-07-020150.rst
+++ b/doc/metadata/rhel7/V-71977.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020150
+id: V-71977
 status: implemented
 tag: packages
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020151.rst b/doc/metadata/rhel7/V-71979.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-020151.rst
rename to doc/metadata/rhel7/V-71979.rst
index 0c2a9241..0f6145d2 100644
--- a/doc/metadata/rhel7/RHEL-07-020151.rst
+++ b/doc/metadata/rhel7/V-71979.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020151
+id: V-71979
 status: implemented
 tag: packages
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020152.rst b/doc/metadata/rhel7/V-71981.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-020152.rst
rename to doc/metadata/rhel7/V-71981.rst
index 4fa7c750..878cb1bc 100644
--- a/doc/metadata/rhel7/RHEL-07-020152.rst
+++ b/doc/metadata/rhel7/V-71981.rst
@@ -1,6 +1,6 @@
 ---
-id: RHEL-07-020152
-status: implemented
+id: V-71981
+status: opt in
 tag: packages
 ---
 
diff --git a/doc/metadata/rhel7/RHEL-07-020160.rst b/doc/metadata/rhel7/V-71983.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-020160.rst
rename to doc/metadata/rhel7/V-71983.rst
index 8e4a9072..72a7b676 100644
--- a/doc/metadata/rhel7/RHEL-07-020160.rst
+++ b/doc/metadata/rhel7/V-71983.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020160
+id: V-71983
 status: opt-in
 tag: kernel
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020161.rst b/doc/metadata/rhel7/V-71985.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-020161.rst
rename to doc/metadata/rhel7/V-71985.rst
index 79a1f8a9..71b10dcf 100644
--- a/doc/metadata/rhel7/RHEL-07-020161.rst
+++ b/doc/metadata/rhel7/V-71985.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020161
+id: V-71985
 status: implemented
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020200.rst b/doc/metadata/rhel7/V-71987.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-020200.rst
rename to doc/metadata/rhel7/V-71987.rst
index eb6cbc0f..4a9f78db 100644
--- a/doc/metadata/rhel7/RHEL-07-020200.rst
+++ b/doc/metadata/rhel7/V-71987.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020200
+id: V-71987
 status: opt-in
 tag: packages
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020210.rst b/doc/metadata/rhel7/V-71989.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-020210.rst
rename to doc/metadata/rhel7/V-71989.rst
index 5510cc77..80206488 100644
--- a/doc/metadata/rhel7/RHEL-07-020210.rst
+++ b/doc/metadata/rhel7/V-71989.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020210
+id: V-71989
 status: implemented
 tag: lsm
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020211.rst b/doc/metadata/rhel7/V-71991.rst
similarity index 85%
rename from doc/metadata/rhel7/RHEL-07-020211.rst
rename to doc/metadata/rhel7/V-71991.rst
index 0661e499..04b9fdd0 100644
--- a/doc/metadata/rhel7/RHEL-07-020211.rst
+++ b/doc/metadata/rhel7/V-71991.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020211
+id: V-71991
 status: implemented
 tag: misc
 ---
@@ -9,4 +9,4 @@ AppArmor only has one set of policies, so this change has no effect on Ubuntu
 systems running AppArmor.
 
 For more information on this change and how to opt out, refer to
-:ref:`stig-RHEL-07-020210`.
+:ref:`stig-V-71989`.
diff --git a/doc/metadata/rhel7/RHEL-07-020220.rst b/doc/metadata/rhel7/V-71993.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-020220.rst
rename to doc/metadata/rhel7/V-71993.rst
index 572fc3c2..72cdbf78 100644
--- a/doc/metadata/rhel7/RHEL-07-020220.rst
+++ b/doc/metadata/rhel7/V-71993.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020220
+id: V-71993
 status: implemented
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020230.rst b/doc/metadata/rhel7/V-71995.rst
similarity index 98%
rename from doc/metadata/rhel7/RHEL-07-020230.rst
rename to doc/metadata/rhel7/V-71995.rst
index c5b7aaf7..19becf76 100644
--- a/doc/metadata/rhel7/RHEL-07-020230.rst
+++ b/doc/metadata/rhel7/V-71995.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020230
+id: V-71995
 status: opt-in - Ubuntu only
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020240.rst b/doc/metadata/rhel7/V-71997.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-020240.rst
rename to doc/metadata/rhel7/V-71997.rst
index 9406b584..67ac822f 100644
--- a/doc/metadata/rhel7/RHEL-07-020240.rst
+++ b/doc/metadata/rhel7/V-71997.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020240
+id: V-71997
 status: exception - manual intervention
 tag: packages
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020250.rst b/doc/metadata/rhel7/V-71999.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-020250.rst
rename to doc/metadata/rhel7/V-71999.rst
index 5f35b329..7c6c6a1e 100644
--- a/doc/metadata/rhel7/RHEL-07-020250.rst
+++ b/doc/metadata/rhel7/V-71999.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020250
+id: V-71999
 status: opt-in
 tag: packages
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020290.rst b/doc/metadata/rhel7/V-72001.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-020290.rst
rename to doc/metadata/rhel7/V-72001.rst
index eb39f549..34d8d449 100644
--- a/doc/metadata/rhel7/RHEL-07-020290.rst
+++ b/doc/metadata/rhel7/V-72001.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020290
+id: V-72001
 status: exception - manual intervention
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020300.rst b/doc/metadata/rhel7/V-72003.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-020300.rst
rename to doc/metadata/rhel7/V-72003.rst
index 343c7199..5c7a42f3 100644
--- a/doc/metadata/rhel7/RHEL-07-020300.rst
+++ b/doc/metadata/rhel7/V-72003.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020300
+id: V-72003
 status: implemented
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020310.rst b/doc/metadata/rhel7/V-72005.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-020310.rst
rename to doc/metadata/rhel7/V-72005.rst
index ea150403..eeaf55ed 100644
--- a/doc/metadata/rhel7/RHEL-07-020310.rst
+++ b/doc/metadata/rhel7/V-72005.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020310
+id: V-72005
 status: implemented
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020360.rst b/doc/metadata/rhel7/V-72007.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-020360.rst
rename to doc/metadata/rhel7/V-72007.rst
index 69d0cd40..f1b2e848 100644
--- a/doc/metadata/rhel7/RHEL-07-020360.rst
+++ b/doc/metadata/rhel7/V-72007.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020360
+id: V-72007
 status: opt-in
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020370.rst b/doc/metadata/rhel7/V-72009.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-020370.rst
rename to doc/metadata/rhel7/V-72009.rst
index 1d25b19f..15b2e699 100644
--- a/doc/metadata/rhel7/RHEL-07-020370.rst
+++ b/doc/metadata/rhel7/V-72009.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020370
+id: V-72009
 status: opt-in
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020620.rst b/doc/metadata/rhel7/V-72011.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-020620.rst
rename to doc/metadata/rhel7/V-72011.rst
index 3e2b6656..987742ea 100644
--- a/doc/metadata/rhel7/RHEL-07-020620.rst
+++ b/doc/metadata/rhel7/V-72011.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020620
+id: V-72011
 status: implemented
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020630.rst b/doc/metadata/rhel7/V-72013.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-020630.rst
rename to doc/metadata/rhel7/V-72013.rst
index 90b3774c..8adcf084 100644
--- a/doc/metadata/rhel7/RHEL-07-020630.rst
+++ b/doc/metadata/rhel7/V-72013.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020630
+id: V-72013
 status: implemented
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020640.rst b/doc/metadata/rhel7/V-72015.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-020640.rst
rename to doc/metadata/rhel7/V-72015.rst
index b3328dac..40046b8d 100644
--- a/doc/metadata/rhel7/RHEL-07-020640.rst
+++ b/doc/metadata/rhel7/V-72015.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020640
+id: V-72015
 status: implemented
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020650.rst b/doc/metadata/rhel7/V-72017.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-020650.rst
rename to doc/metadata/rhel7/V-72017.rst
index 04dfd5d2..a2b808de 100644
--- a/doc/metadata/rhel7/RHEL-07-020650.rst
+++ b/doc/metadata/rhel7/V-72017.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020650
+id: V-72017
 status: opt-in
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020660.rst b/doc/metadata/rhel7/V-72019.rst
similarity index 79%
rename from doc/metadata/rhel7/RHEL-07-020660.rst
rename to doc/metadata/rhel7/V-72019.rst
index 89e275bf..ed5f260e 100644
--- a/doc/metadata/rhel7/RHEL-07-020660.rst
+++ b/doc/metadata/rhel7/V-72019.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020660
+id: V-72019
 status: opt-in
 tag: file_perms
 ---
@@ -7,4 +7,4 @@ tag: file_perms
 This control is implemented by the tasks for another control. Refer to the
 documentation for more details on the change and how to opt out:
 
-* :ref:`stig-RHEL-07-020650`
+* :ref:`stig-V-72017`
diff --git a/doc/metadata/rhel7/RHEL-07-020670.rst b/doc/metadata/rhel7/V-72021.rst
similarity index 79%
rename from doc/metadata/rhel7/RHEL-07-020670.rst
rename to doc/metadata/rhel7/V-72021.rst
index 2aaed5ea..a81deb94 100644
--- a/doc/metadata/rhel7/RHEL-07-020670.rst
+++ b/doc/metadata/rhel7/V-72021.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020670
+id: V-72021
 status: opt-in
 tag: file_perms
 ---
@@ -7,4 +7,4 @@ tag: file_perms
 This control is implemented by the tasks for another control. Refer to the
 documentation for more details on the change and how to opt out:
 
-* :ref:`stig-RHEL-07-020650`
+* :ref:`stig-V-72017`
diff --git a/doc/metadata/rhel7/RHEL-07-020700.rst b/doc/metadata/rhel7/V-72023.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-020700.rst
rename to doc/metadata/rhel7/V-72023.rst
index 86769d4d..6f20fe95 100644
--- a/doc/metadata/rhel7/RHEL-07-020700.rst
+++ b/doc/metadata/rhel7/V-72023.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020700
+id: V-72023
 status: exception - manual intervention
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020680.rst b/doc/metadata/rhel7/V-72025.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-020680.rst
rename to doc/metadata/rhel7/V-72025.rst
index 93ddeebd..732dd8f0 100644
--- a/doc/metadata/rhel7/RHEL-07-020680.rst
+++ b/doc/metadata/rhel7/V-72025.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020680
+id: V-72025
 status: exception - manual intervention
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020690.rst b/doc/metadata/rhel7/V-72027.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-020690.rst
rename to doc/metadata/rhel7/V-72027.rst
index bee110ec..c9d596e8 100644
--- a/doc/metadata/rhel7/RHEL-07-020690.rst
+++ b/doc/metadata/rhel7/V-72027.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020690
+id: V-72027
 status: exception - manual intervention
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020850.rst b/doc/metadata/rhel7/V-72029.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-020850.rst
rename to doc/metadata/rhel7/V-72029.rst
index ea1480cf..0e0b4821 100644
--- a/doc/metadata/rhel7/RHEL-07-020850.rst
+++ b/doc/metadata/rhel7/V-72029.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020850
+id: V-72029
 status: exception - manual intervention
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020860.rst b/doc/metadata/rhel7/V-72031.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-020860.rst
rename to doc/metadata/rhel7/V-72031.rst
index 7d1ee93e..70aa5629 100644
--- a/doc/metadata/rhel7/RHEL-07-020860.rst
+++ b/doc/metadata/rhel7/V-72031.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020860
+id: V-72031
 status: exception - manual intervention
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020840.rst b/doc/metadata/rhel7/V-72033.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-020840.rst
rename to doc/metadata/rhel7/V-72033.rst
index 0b71a0b7..21fe68ed 100644
--- a/doc/metadata/rhel7/RHEL-07-020840.rst
+++ b/doc/metadata/rhel7/V-72033.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020840
+id: V-72033
 status: exception - manual intervention
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/V-72035.rst b/doc/metadata/rhel7/V-72035.rst
new file mode 100644
index 00000000..88dd3287
--- /dev/null
+++ b/doc/metadata/rhel7/V-72035.rst
@@ -0,0 +1,10 @@
+---
+id: V-72035
+status: exception - manual intervention
+tag: misc
+---
+
+Although the STIG requires that all initialization files must contain
+executable search paths that resolve to the user's home directory, this change
+be disruptive for most users. The tasks in the security role do not make any
+changes to user initialization files.
diff --git a/doc/metadata/rhel7/RHEL-07-020880.rst b/doc/metadata/rhel7/V-72037.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-020880.rst
rename to doc/metadata/rhel7/V-72037.rst
index 20cb2e9d..f5e43670 100644
--- a/doc/metadata/rhel7/RHEL-07-020880.rst
+++ b/doc/metadata/rhel7/V-72037.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020880
+id: V-72037
 status: exception - manual intervention
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-020940.rst b/doc/metadata/rhel7/V-72039.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-020940.rst
rename to doc/metadata/rhel7/V-72039.rst
index 57c17c27..fe78bdf8 100644
--- a/doc/metadata/rhel7/RHEL-07-020940.rst
+++ b/doc/metadata/rhel7/V-72039.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-020940
+id: V-72039
 status: implemented - red hat only
 tag: lsm
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021010.rst b/doc/metadata/rhel7/V-72041.rst
similarity index 90%
rename from doc/metadata/rhel7/RHEL-07-021010.rst
rename to doc/metadata/rhel7/V-72041.rst
index 36828e7a..d67059df 100644
--- a/doc/metadata/rhel7/RHEL-07-021010.rst
+++ b/doc/metadata/rhel7/V-72041.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021010
+id: V-72041
 status: exception - manual intervention
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021011.rst b/doc/metadata/rhel7/V-72043.rst
similarity index 90%
rename from doc/metadata/rhel7/RHEL-07-021011.rst
rename to doc/metadata/rhel7/V-72043.rst
index 8f00ab66..bd957fff 100644
--- a/doc/metadata/rhel7/RHEL-07-021011.rst
+++ b/doc/metadata/rhel7/V-72043.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021011
+id: V-72043
 status: exception - manual intervention
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021012.rst b/doc/metadata/rhel7/V-72045.rst
similarity index 89%
rename from doc/metadata/rhel7/RHEL-07-021012.rst
rename to doc/metadata/rhel7/V-72045.rst
index 2379a6bc..09c8f705 100644
--- a/doc/metadata/rhel7/RHEL-07-021012.rst
+++ b/doc/metadata/rhel7/V-72045.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021012
+id: V-72045
 status: exception - manual intervention
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021050.rst b/doc/metadata/rhel7/V-72047.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-021050.rst
rename to doc/metadata/rhel7/V-72047.rst
index d0a7cc9a..18b4ace4 100644
--- a/doc/metadata/rhel7/RHEL-07-021050.rst
+++ b/doc/metadata/rhel7/V-72047.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021050
+id: V-72047
 status: implemented
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021060.rst b/doc/metadata/rhel7/V-72049.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-021060.rst
rename to doc/metadata/rhel7/V-72049.rst
index 65b265cb..746152ff 100644
--- a/doc/metadata/rhel7/RHEL-07-021060.rst
+++ b/doc/metadata/rhel7/V-72049.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021060
+id: V-72049
 status: exception - manual intervention
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021160.rst b/doc/metadata/rhel7/V-72051.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-021160.rst
rename to doc/metadata/rhel7/V-72051.rst
index f2082584..f9c65e10 100644
--- a/doc/metadata/rhel7/RHEL-07-021160.rst
+++ b/doc/metadata/rhel7/V-72051.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021160
+id: V-72051
 status: exception - manual intervention
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021190.rst b/doc/metadata/rhel7/V-72053.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-021190.rst
rename to doc/metadata/rhel7/V-72053.rst
index 421175cf..d57a9ce5 100644
--- a/doc/metadata/rhel7/RHEL-07-021190.rst
+++ b/doc/metadata/rhel7/V-72053.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021190
+id: V-72053
 status: implemented
 tag: file_perms
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021200.rst b/doc/metadata/rhel7/V-72055.rst
similarity index 82%
rename from doc/metadata/rhel7/RHEL-07-021200.rst
rename to doc/metadata/rhel7/V-72055.rst
index ae9535cd..6422996c 100644
--- a/doc/metadata/rhel7/RHEL-07-021200.rst
+++ b/doc/metadata/rhel7/V-72055.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021200
+id: V-72055
 status: not implemented
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021230.rst b/doc/metadata/rhel7/V-72057.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-021230.rst
rename to doc/metadata/rhel7/V-72057.rst
index e9e6e424..911fa838 100644
--- a/doc/metadata/rhel7/RHEL-07-021230.rst
+++ b/doc/metadata/rhel7/V-72057.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021230
+id: V-72057
 status: implemented
 tag: kernel
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021240.rst b/doc/metadata/rhel7/V-72059.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-021240.rst
rename to doc/metadata/rhel7/V-72059.rst
index a92c72c0..2ca45c16 100644
--- a/doc/metadata/rhel7/RHEL-07-021240.rst
+++ b/doc/metadata/rhel7/V-72059.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021240
+id: V-72059
 status: exception - initial provisioning
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021250.rst b/doc/metadata/rhel7/V-72061.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-021250.rst
rename to doc/metadata/rhel7/V-72061.rst
index c90492ac..667a5bfa 100644
--- a/doc/metadata/rhel7/RHEL-07-021250.rst
+++ b/doc/metadata/rhel7/V-72061.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021250
+id: V-72061
 status: exception - initial provisioning
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021260.rst b/doc/metadata/rhel7/V-72063.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-021260.rst
rename to doc/metadata/rhel7/V-72063.rst
index 423e5879..92888168 100644
--- a/doc/metadata/rhel7/RHEL-07-021260.rst
+++ b/doc/metadata/rhel7/V-72063.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021260
+id: V-72063
 status: exception - initial provisioning
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021270.rst b/doc/metadata/rhel7/V-72065.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-021270.rst
rename to doc/metadata/rhel7/V-72065.rst
index 2d5c7937..5cc437d4 100644
--- a/doc/metadata/rhel7/RHEL-07-021270.rst
+++ b/doc/metadata/rhel7/V-72065.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021270
+id: V-72065
 status: exception - initial provisioning
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021280.rst b/doc/metadata/rhel7/V-72067.rst
similarity index 98%
rename from doc/metadata/rhel7/RHEL-07-021280.rst
rename to doc/metadata/rhel7/V-72067.rst
index a3a4939f..03d5dc7e 100644
--- a/doc/metadata/rhel7/RHEL-07-021280.rst
+++ b/doc/metadata/rhel7/V-72067.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021280
+id: V-72067
 status: implemented - red hat only
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021600.rst b/doc/metadata/rhel7/V-72069.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-021600.rst
rename to doc/metadata/rhel7/V-72069.rst
index 8bcdaf10..b72fb762 100644
--- a/doc/metadata/rhel7/RHEL-07-021600.rst
+++ b/doc/metadata/rhel7/V-72069.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021600
+id: V-72069
 status: implemented
 tag: aide
 ---
@@ -11,4 +11,4 @@ by default. No configuration changes are applied on these systems.
 However, Ubuntu lacks the rules that include ACL and extended attribute checks.
 The tasks in the security role will add a small configuration block at the end
 of the AIDE configuration file to meet the requirements of this STIG, as well
-as RHEL-07-021610.
+as V-72071.
diff --git a/doc/metadata/rhel7/RHEL-07-021610.rst b/doc/metadata/rhel7/V-72071.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-021610.rst
rename to doc/metadata/rhel7/V-72071.rst
index 42951d52..38c26425 100644
--- a/doc/metadata/rhel7/RHEL-07-021610.rst
+++ b/doc/metadata/rhel7/V-72071.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021610
+id: V-72071
 status: implemented
 tag: aide
 ---
@@ -11,4 +11,4 @@ by default. No configuration changes are applied on these systems.
 However, Ubuntu lacks the rules that include ACL and extended attribute checks.
 The tasks in the security role will add a small configuration block at the end
 of the AIDE configuration file to meet the requirements of this STIG, as well
-as RHEL-07-021600.
+as V-72069.
diff --git a/doc/metadata/rhel7/RHEL-07-021620.rst b/doc/metadata/rhel7/V-72073.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-021620.rst
rename to doc/metadata/rhel7/V-72073.rst
index f1eed1b8..ff99eac1 100644
--- a/doc/metadata/rhel7/RHEL-07-021620.rst
+++ b/doc/metadata/rhel7/V-72073.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021620
+id: V-72073
 status: implemented
 tag: aide
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021760.rst b/doc/metadata/rhel7/V-72075.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-021760.rst
rename to doc/metadata/rhel7/V-72075.rst
index 94490e33..0c994301 100644
--- a/doc/metadata/rhel7/RHEL-07-021760.rst
+++ b/doc/metadata/rhel7/V-72075.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021760
+id: V-72075
 status: exception - initial provisioning
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-021910.rst b/doc/metadata/rhel7/V-72077.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-021910.rst
rename to doc/metadata/rhel7/V-72077.rst
index 10f9fcce..839669a5 100644
--- a/doc/metadata/rhel7/RHEL-07-021910.rst
+++ b/doc/metadata/rhel7/V-72077.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-021910
+id: V-72077
 status: implemented
 tag: packages
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030010.rst b/doc/metadata/rhel7/V-72079.rst
similarity index 88%
rename from doc/metadata/rhel7/RHEL-07-030010.rst
rename to doc/metadata/rhel7/V-72079.rst
index 27973ff3..9964f7ed 100644
--- a/doc/metadata/rhel7/RHEL-07-030010.rst
+++ b/doc/metadata/rhel7/V-72079.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030010
+id: V-72079
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030090.rst b/doc/metadata/rhel7/V-72081.rst
similarity index 98%
rename from doc/metadata/rhel7/RHEL-07-030090.rst
rename to doc/metadata/rhel7/V-72081.rst
index ed3753b7..c4bb041a 100644
--- a/doc/metadata/rhel7/RHEL-07-030090.rst
+++ b/doc/metadata/rhel7/V-72081.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030090
+id: V-72081
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030330.rst b/doc/metadata/rhel7/V-72083.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030330.rst
rename to doc/metadata/rhel7/V-72083.rst
index 801ec177..cbb1309a 100644
--- a/doc/metadata/rhel7/RHEL-07-030330.rst
+++ b/doc/metadata/rhel7/V-72083.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030330
+id: V-72083
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030331.rst b/doc/metadata/rhel7/V-72085.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-030331.rst
rename to doc/metadata/rhel7/V-72085.rst
index 5ccea1fd..38a1f8cc 100644
--- a/doc/metadata/rhel7/RHEL-07-030331.rst
+++ b/doc/metadata/rhel7/V-72085.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030331
+id: V-72085
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030340.rst b/doc/metadata/rhel7/V-72087.rst
similarity index 98%
rename from doc/metadata/rhel7/RHEL-07-030340.rst
rename to doc/metadata/rhel7/V-72087.rst
index 5c71a77a..14c4628b 100644
--- a/doc/metadata/rhel7/RHEL-07-030340.rst
+++ b/doc/metadata/rhel7/V-72087.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030340
+id: V-72087
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030350.rst b/doc/metadata/rhel7/V-72089.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-030350.rst
rename to doc/metadata/rhel7/V-72089.rst
index 533dd195..0d7a8c1b 100644
--- a/doc/metadata/rhel7/RHEL-07-030350.rst
+++ b/doc/metadata/rhel7/V-72089.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030350
+id: V-72089
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030351.rst b/doc/metadata/rhel7/V-72091.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-030351.rst
rename to doc/metadata/rhel7/V-72091.rst
index dfd6eb3d..66d2312f 100644
--- a/doc/metadata/rhel7/RHEL-07-030351.rst
+++ b/doc/metadata/rhel7/V-72091.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030351
+id: V-72091
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030352.rst b/doc/metadata/rhel7/V-72093.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-030352.rst
rename to doc/metadata/rhel7/V-72093.rst
index c52c3808..33c1f00f 100644
--- a/doc/metadata/rhel7/RHEL-07-030352.rst
+++ b/doc/metadata/rhel7/V-72093.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030352
+id: V-72093
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030310.rst b/doc/metadata/rhel7/V-72095.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-030310.rst
rename to doc/metadata/rhel7/V-72095.rst
index 3e9f485a..6e2a71d0 100644
--- a/doc/metadata/rhel7/RHEL-07-030310.rst
+++ b/doc/metadata/rhel7/V-72095.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030310
+id: V-72095
 status: exception - manual intervention
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030380.rst b/doc/metadata/rhel7/V-72097.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-030380.rst
rename to doc/metadata/rhel7/V-72097.rst
index 3cb7c321..61f4454a 100644
--- a/doc/metadata/rhel7/RHEL-07-030380.rst
+++ b/doc/metadata/rhel7/V-72097.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030380
+id: V-72097
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030381.rst b/doc/metadata/rhel7/V-72099.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-030381.rst
rename to doc/metadata/rhel7/V-72099.rst
index 5b56e990..d2df6598 100644
--- a/doc/metadata/rhel7/RHEL-07-030381.rst
+++ b/doc/metadata/rhel7/V-72099.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030381
+id: V-72099
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030382.rst b/doc/metadata/rhel7/V-72101.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-030382.rst
rename to doc/metadata/rhel7/V-72101.rst
index 56bf6468..a1b3b75a 100644
--- a/doc/metadata/rhel7/RHEL-07-030382.rst
+++ b/doc/metadata/rhel7/V-72101.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030382
+id: V-72101
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030383.rst b/doc/metadata/rhel7/V-72103.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-030383.rst
rename to doc/metadata/rhel7/V-72103.rst
index 1804e953..a279c60c 100644
--- a/doc/metadata/rhel7/RHEL-07-030383.rst
+++ b/doc/metadata/rhel7/V-72103.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030383
+id: V-72103
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030390.rst b/doc/metadata/rhel7/V-72105.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-030390.rst
rename to doc/metadata/rhel7/V-72105.rst
index 363fbbde..a7c946ac 100644
--- a/doc/metadata/rhel7/RHEL-07-030390.rst
+++ b/doc/metadata/rhel7/V-72105.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030390
+id: V-72105
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030391.rst b/doc/metadata/rhel7/V-72107.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-030391.rst
rename to doc/metadata/rhel7/V-72107.rst
index 5486e994..8cc03dc4 100644
--- a/doc/metadata/rhel7/RHEL-07-030391.rst
+++ b/doc/metadata/rhel7/V-72107.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030391
+id: V-72107
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030392.rst b/doc/metadata/rhel7/V-72109.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-030392.rst
rename to doc/metadata/rhel7/V-72109.rst
index e1eec800..638d0189 100644
--- a/doc/metadata/rhel7/RHEL-07-030392.rst
+++ b/doc/metadata/rhel7/V-72109.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030392
+id: V-72109
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030400.rst b/doc/metadata/rhel7/V-72111.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030400.rst
rename to doc/metadata/rhel7/V-72111.rst
index 80493bc3..c172d147 100644
--- a/doc/metadata/rhel7/RHEL-07-030400.rst
+++ b/doc/metadata/rhel7/V-72111.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030400
+id: V-72111
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030401.rst b/doc/metadata/rhel7/V-72113.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-030401.rst
rename to doc/metadata/rhel7/V-72113.rst
index bff71f37..4457fbb5 100644
--- a/doc/metadata/rhel7/RHEL-07-030401.rst
+++ b/doc/metadata/rhel7/V-72113.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030401
+id: V-72113
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030402.rst b/doc/metadata/rhel7/V-72115.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-030402.rst
rename to doc/metadata/rhel7/V-72115.rst
index f7bf838d..85fa4c11 100644
--- a/doc/metadata/rhel7/RHEL-07-030402.rst
+++ b/doc/metadata/rhel7/V-72115.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030402
+id: V-72115
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030403.rst b/doc/metadata/rhel7/V-72117.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030403.rst
rename to doc/metadata/rhel7/V-72117.rst
index 2db10ab4..6daddbc1 100644
--- a/doc/metadata/rhel7/RHEL-07-030403.rst
+++ b/doc/metadata/rhel7/V-72117.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030403
+id: V-72117
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030404.rst b/doc/metadata/rhel7/V-72119.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-030404.rst
rename to doc/metadata/rhel7/V-72119.rst
index a8429004..db24e39c 100644
--- a/doc/metadata/rhel7/RHEL-07-030404.rst
+++ b/doc/metadata/rhel7/V-72119.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030404
+id: V-72119
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030405.rst b/doc/metadata/rhel7/V-72121.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-030405.rst
rename to doc/metadata/rhel7/V-72121.rst
index f429a43e..3165a414 100644
--- a/doc/metadata/rhel7/RHEL-07-030405.rst
+++ b/doc/metadata/rhel7/V-72121.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030405
+id: V-72121
 status: opt-in
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030420.rst b/doc/metadata/rhel7/V-72123.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030420.rst
rename to doc/metadata/rhel7/V-72123.rst
index c3bf5c7a..2e18006c 100644
--- a/doc/metadata/rhel7/RHEL-07-030420.rst
+++ b/doc/metadata/rhel7/V-72123.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030420
+id: V-72123
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030421.rst b/doc/metadata/rhel7/V-72125.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030421.rst
rename to doc/metadata/rhel7/V-72125.rst
index 74d61220..390083ea 100644
--- a/doc/metadata/rhel7/RHEL-07-030421.rst
+++ b/doc/metadata/rhel7/V-72125.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030421
+id: V-72125
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030422.rst b/doc/metadata/rhel7/V-72127.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030422.rst
rename to doc/metadata/rhel7/V-72127.rst
index 42943ef7..43e72687 100644
--- a/doc/metadata/rhel7/RHEL-07-030422.rst
+++ b/doc/metadata/rhel7/V-72127.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030422
+id: V-72127
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030423.rst b/doc/metadata/rhel7/V-72129.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030423.rst
rename to doc/metadata/rhel7/V-72129.rst
index 6795d9c8..a26af223 100644
--- a/doc/metadata/rhel7/RHEL-07-030423.rst
+++ b/doc/metadata/rhel7/V-72129.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030423
+id: V-72129
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030424.rst b/doc/metadata/rhel7/V-72131.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030424.rst
rename to doc/metadata/rhel7/V-72131.rst
index dd325386..0967d0b2 100644
--- a/doc/metadata/rhel7/RHEL-07-030424.rst
+++ b/doc/metadata/rhel7/V-72131.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030424
+id: V-72131
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030425.rst b/doc/metadata/rhel7/V-72133.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030425.rst
rename to doc/metadata/rhel7/V-72133.rst
index 9d9e7698..993fe55f 100644
--- a/doc/metadata/rhel7/RHEL-07-030425.rst
+++ b/doc/metadata/rhel7/V-72133.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030425
+id: V-72133
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030441.rst b/doc/metadata/rhel7/V-72135.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-030441.rst
rename to doc/metadata/rhel7/V-72135.rst
index 66bf57ce..db460c2a 100644
--- a/doc/metadata/rhel7/RHEL-07-030441.rst
+++ b/doc/metadata/rhel7/V-72135.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030441
+id: V-72135
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030442.rst b/doc/metadata/rhel7/V-72137.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-030442.rst
rename to doc/metadata/rhel7/V-72137.rst
index a4ee21af..e9babbdd 100644
--- a/doc/metadata/rhel7/RHEL-07-030442.rst
+++ b/doc/metadata/rhel7/V-72137.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030442
+id: V-72137
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030443.rst b/doc/metadata/rhel7/V-72139.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-030443.rst
rename to doc/metadata/rhel7/V-72139.rst
index 91c61500..e0218da6 100644
--- a/doc/metadata/rhel7/RHEL-07-030443.rst
+++ b/doc/metadata/rhel7/V-72139.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030443
+id: V-72139
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030444.rst b/doc/metadata/rhel7/V-72141.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030444.rst
rename to doc/metadata/rhel7/V-72141.rst
index ce903b90..6bd294bd 100644
--- a/doc/metadata/rhel7/RHEL-07-030444.rst
+++ b/doc/metadata/rhel7/V-72141.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030444
+id: V-72141
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030490.rst b/doc/metadata/rhel7/V-72143.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030490.rst
rename to doc/metadata/rhel7/V-72143.rst
index f6f9334b..320ffa7a 100644
--- a/doc/metadata/rhel7/RHEL-07-030490.rst
+++ b/doc/metadata/rhel7/V-72143.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030490
+id: V-72143
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030491.rst b/doc/metadata/rhel7/V-72145.rst
similarity index 68%
rename from doc/metadata/rhel7/RHEL-07-030491.rst
rename to doc/metadata/rhel7/V-72145.rst
index f2718e61..a8926586 100644
--- a/doc/metadata/rhel7/RHEL-07-030491.rst
+++ b/doc/metadata/rhel7/V-72145.rst
@@ -1,9 +1,9 @@
 ---
-id: RHEL-07-030491
+id: V-72145
 status: implemented
 tag: auditd
 ---
 
 This control is implemented by the tasks for another control:
 
-* :ref:`stig-RHEL-07-030490`
+* :ref:`stig-V-72143`
diff --git a/doc/metadata/rhel7/RHEL-07-030492.rst b/doc/metadata/rhel7/V-72147.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030492.rst
rename to doc/metadata/rhel7/V-72147.rst
index d372cd48..ae3e1ed6 100644
--- a/doc/metadata/rhel7/RHEL-07-030492.rst
+++ b/doc/metadata/rhel7/V-72147.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030492
+id: V-72147
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030510.rst b/doc/metadata/rhel7/V-72149.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030510.rst
rename to doc/metadata/rhel7/V-72149.rst
index 8d356b93..d77161d5 100644
--- a/doc/metadata/rhel7/RHEL-07-030510.rst
+++ b/doc/metadata/rhel7/V-72149.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030510
+id: V-72149
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030511.rst b/doc/metadata/rhel7/V-72151.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030511.rst
rename to doc/metadata/rhel7/V-72151.rst
index 9d753c89..a8af9fd6 100644
--- a/doc/metadata/rhel7/RHEL-07-030511.rst
+++ b/doc/metadata/rhel7/V-72151.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030511
+id: V-72151
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030512.rst b/doc/metadata/rhel7/V-72153.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030512.rst
rename to doc/metadata/rhel7/V-72153.rst
index 1ac26d8d..b4b5eb65 100644
--- a/doc/metadata/rhel7/RHEL-07-030512.rst
+++ b/doc/metadata/rhel7/V-72153.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030512
+id: V-72153
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030513.rst b/doc/metadata/rhel7/V-72155.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-030513.rst
rename to doc/metadata/rhel7/V-72155.rst
index 4eba7144..66ad3c58 100644
--- a/doc/metadata/rhel7/RHEL-07-030513.rst
+++ b/doc/metadata/rhel7/V-72155.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030513
+id: V-72155
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030514.rst b/doc/metadata/rhel7/V-72157.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030514.rst
rename to doc/metadata/rhel7/V-72157.rst
index ff5ee437..e39493a5 100644
--- a/doc/metadata/rhel7/RHEL-07-030514.rst
+++ b/doc/metadata/rhel7/V-72157.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030514
+id: V-72157
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030521.rst b/doc/metadata/rhel7/V-72159.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-030521.rst
rename to doc/metadata/rhel7/V-72159.rst
index 9fbe104a..0b1d0347 100644
--- a/doc/metadata/rhel7/RHEL-07-030521.rst
+++ b/doc/metadata/rhel7/V-72159.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030521
+id: V-72159
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030522.rst b/doc/metadata/rhel7/V-72161.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-030522.rst
rename to doc/metadata/rhel7/V-72161.rst
index 91aa72da..e45c9f36 100644
--- a/doc/metadata/rhel7/RHEL-07-030522.rst
+++ b/doc/metadata/rhel7/V-72161.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030522
+id: V-72161
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030523.rst b/doc/metadata/rhel7/V-72163.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030523.rst
rename to doc/metadata/rhel7/V-72163.rst
index 1d2c32ff..7f79c8b1 100644
--- a/doc/metadata/rhel7/RHEL-07-030523.rst
+++ b/doc/metadata/rhel7/V-72163.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030523
+id: V-72163
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030524.rst b/doc/metadata/rhel7/V-72165.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030524.rst
rename to doc/metadata/rhel7/V-72165.rst
index 496982ca..d67f1bb6 100644
--- a/doc/metadata/rhel7/RHEL-07-030524.rst
+++ b/doc/metadata/rhel7/V-72165.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030524
+id: V-72165
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030525.rst b/doc/metadata/rhel7/V-72167.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-030525.rst
rename to doc/metadata/rhel7/V-72167.rst
index 3fecdc10..bee88198 100644
--- a/doc/metadata/rhel7/RHEL-07-030525.rst
+++ b/doc/metadata/rhel7/V-72167.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030525
+id: V-72167
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030526.rst b/doc/metadata/rhel7/V-72169.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030526.rst
rename to doc/metadata/rhel7/V-72169.rst
index 050338f0..3d2bc233 100644
--- a/doc/metadata/rhel7/RHEL-07-030526.rst
+++ b/doc/metadata/rhel7/V-72169.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030526
+id: V-72169
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030530.rst b/doc/metadata/rhel7/V-72171.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-030530.rst
rename to doc/metadata/rhel7/V-72171.rst
index 366930a0..e151cc0d 100644
--- a/doc/metadata/rhel7/RHEL-07-030530.rst
+++ b/doc/metadata/rhel7/V-72171.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030530
+id: V-72171
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030531.rst b/doc/metadata/rhel7/V-72173.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030531.rst
rename to doc/metadata/rhel7/V-72173.rst
index a5b0adbb..c400734e 100644
--- a/doc/metadata/rhel7/RHEL-07-030531.rst
+++ b/doc/metadata/rhel7/V-72173.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030531
+id: V-72173
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030540.rst b/doc/metadata/rhel7/V-72175.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030540.rst
rename to doc/metadata/rhel7/V-72175.rst
index 83cfc481..0c81c5fb 100644
--- a/doc/metadata/rhel7/RHEL-07-030540.rst
+++ b/doc/metadata/rhel7/V-72175.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030540
+id: V-72175
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030541.rst b/doc/metadata/rhel7/V-72177.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030541.rst
rename to doc/metadata/rhel7/V-72177.rst
index ffb02449..eed070f2 100644
--- a/doc/metadata/rhel7/RHEL-07-030541.rst
+++ b/doc/metadata/rhel7/V-72177.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030541
+id: V-72177
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030550.rst b/doc/metadata/rhel7/V-72179.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030550.rst
rename to doc/metadata/rhel7/V-72179.rst
index c8783d8f..3fdeb118 100644
--- a/doc/metadata/rhel7/RHEL-07-030550.rst
+++ b/doc/metadata/rhel7/V-72179.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030550
+id: V-72179
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030560.rst b/doc/metadata/rhel7/V-72181.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030560.rst
rename to doc/metadata/rhel7/V-72181.rst
index 3a17d30a..00d69673 100644
--- a/doc/metadata/rhel7/RHEL-07-030560.rst
+++ b/doc/metadata/rhel7/V-72181.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030560
+id: V-72181
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030561.rst b/doc/metadata/rhel7/V-72183.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030561.rst
rename to doc/metadata/rhel7/V-72183.rst
index 082eec51..440d8413 100644
--- a/doc/metadata/rhel7/RHEL-07-030561.rst
+++ b/doc/metadata/rhel7/V-72183.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030561
+id: V-72183
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030630.rst b/doc/metadata/rhel7/V-72185.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030630.rst
rename to doc/metadata/rhel7/V-72185.rst
index 74af5fbc..d2af1fda 100644
--- a/doc/metadata/rhel7/RHEL-07-030630.rst
+++ b/doc/metadata/rhel7/V-72185.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030630
+id: V-72185
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030670.rst b/doc/metadata/rhel7/V-72187.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030670.rst
rename to doc/metadata/rhel7/V-72187.rst
index 2dbd18c0..d4f528d7 100644
--- a/doc/metadata/rhel7/RHEL-07-030670.rst
+++ b/doc/metadata/rhel7/V-72187.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030670
+id: V-72187
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030671.rst b/doc/metadata/rhel7/V-72189.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030671.rst
rename to doc/metadata/rhel7/V-72189.rst
index 22e6f4b7..4db0d893 100644
--- a/doc/metadata/rhel7/RHEL-07-030671.rst
+++ b/doc/metadata/rhel7/V-72189.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030671
+id: V-72189
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030672.rst b/doc/metadata/rhel7/V-72191.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030672.rst
rename to doc/metadata/rhel7/V-72191.rst
index 53201b9f..4d59ffa1 100644
--- a/doc/metadata/rhel7/RHEL-07-030672.rst
+++ b/doc/metadata/rhel7/V-72191.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030672
+id: V-72191
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030673.rst b/doc/metadata/rhel7/V-72193.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-030673.rst
rename to doc/metadata/rhel7/V-72193.rst
index ac8344ac..60e9b4ce 100644
--- a/doc/metadata/rhel7/RHEL-07-030673.rst
+++ b/doc/metadata/rhel7/V-72193.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030673
+id: V-72193
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030674.rst b/doc/metadata/rhel7/V-72195.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-030674.rst
rename to doc/metadata/rhel7/V-72195.rst
index 1517baae..4ecfdda9 100644
--- a/doc/metadata/rhel7/RHEL-07-030674.rst
+++ b/doc/metadata/rhel7/V-72195.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030674
+id: V-72195
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030710.rst b/doc/metadata/rhel7/V-72197.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-030710.rst
rename to doc/metadata/rhel7/V-72197.rst
index 33d67e44..67e0120b 100644
--- a/doc/metadata/rhel7/RHEL-07-030710.rst
+++ b/doc/metadata/rhel7/V-72197.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030710
+id: V-72197
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030750.rst b/doc/metadata/rhel7/V-72199.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030750.rst
rename to doc/metadata/rhel7/V-72199.rst
index a60306c7..d23e7106 100644
--- a/doc/metadata/rhel7/RHEL-07-030750.rst
+++ b/doc/metadata/rhel7/V-72199.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030750
+id: V-72199
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030751.rst b/doc/metadata/rhel7/V-72201.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030751.rst
rename to doc/metadata/rhel7/V-72201.rst
index b398cb41..4dd9420c 100644
--- a/doc/metadata/rhel7/RHEL-07-030751.rst
+++ b/doc/metadata/rhel7/V-72201.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030751
+id: V-72201
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030752.rst b/doc/metadata/rhel7/V-72203.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030752.rst
rename to doc/metadata/rhel7/V-72203.rst
index 3cbb404f..b6c14441 100644
--- a/doc/metadata/rhel7/RHEL-07-030752.rst
+++ b/doc/metadata/rhel7/V-72203.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030752
+id: V-72203
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030753.rst b/doc/metadata/rhel7/V-72205.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030753.rst
rename to doc/metadata/rhel7/V-72205.rst
index 398d7825..453cc97e 100644
--- a/doc/metadata/rhel7/RHEL-07-030753.rst
+++ b/doc/metadata/rhel7/V-72205.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030753
+id: V-72205
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030754.rst b/doc/metadata/rhel7/V-72207.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030754.rst
rename to doc/metadata/rhel7/V-72207.rst
index b4e0aa4a..a2f609c5 100644
--- a/doc/metadata/rhel7/RHEL-07-030754.rst
+++ b/doc/metadata/rhel7/V-72207.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030754
+id: V-72207
 status: implemented
 tag: auditd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030770.rst b/doc/metadata/rhel7/V-72209.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030770.rst
rename to doc/metadata/rhel7/V-72209.rst
index d4625155..2becaccd 100644
--- a/doc/metadata/rhel7/RHEL-07-030770.rst
+++ b/doc/metadata/rhel7/V-72209.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030770
+id: V-72209
 status: verification only
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030780.rst b/doc/metadata/rhel7/V-72211.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-030780.rst
rename to doc/metadata/rhel7/V-72211.rst
index 95ead0bc..c17df709 100644
--- a/doc/metadata/rhel7/RHEL-07-030780.rst
+++ b/doc/metadata/rhel7/V-72211.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030780
+id: V-72211
 status: exception - manual intervention
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030810.rst b/doc/metadata/rhel7/V-72213.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-030810.rst
rename to doc/metadata/rhel7/V-72213.rst
index 22390dec..15fc5de4 100644
--- a/doc/metadata/rhel7/RHEL-07-030810.rst
+++ b/doc/metadata/rhel7/V-72213.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030810
+id: V-72213
 status: opt-in
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-030820.rst b/doc/metadata/rhel7/V-72215.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-030820.rst
rename to doc/metadata/rhel7/V-72215.rst
index 2a4e3b0b..60a698c4 100644
--- a/doc/metadata/rhel7/RHEL-07-030820.rst
+++ b/doc/metadata/rhel7/V-72215.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-030820
+id: V-72215
 status: implemented
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040010.rst b/doc/metadata/rhel7/V-72217.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-040010.rst
rename to doc/metadata/rhel7/V-72217.rst
index f924a74c..0bce83fe 100644
--- a/doc/metadata/rhel7/RHEL-07-040010.rst
+++ b/doc/metadata/rhel7/V-72217.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040010
+id: V-72217
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040100.rst b/doc/metadata/rhel7/V-72219.rst
similarity index 90%
rename from doc/metadata/rhel7/RHEL-07-040100.rst
rename to doc/metadata/rhel7/V-72219.rst
index 67a68adf..559cc74b 100644
--- a/doc/metadata/rhel7/RHEL-07-040100.rst
+++ b/doc/metadata/rhel7/V-72219.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040100
+id: V-72219
 status: exception - manual intervention
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040110.rst b/doc/metadata/rhel7/V-72221.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-040110.rst
rename to doc/metadata/rhel7/V-72221.rst
index e677da65..69e38a60 100644
--- a/doc/metadata/rhel7/RHEL-07-040110.rst
+++ b/doc/metadata/rhel7/V-72221.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040110
+id: V-72221
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040160.rst b/doc/metadata/rhel7/V-72223.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-040160.rst
rename to doc/metadata/rhel7/V-72223.rst
index 22962ca6..14836821 100644
--- a/doc/metadata/rhel7/RHEL-07-040160.rst
+++ b/doc/metadata/rhel7/V-72223.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040160
+id: V-72223
 status: implemented
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040170.rst b/doc/metadata/rhel7/V-72225.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-040170.rst
rename to doc/metadata/rhel7/V-72225.rst
index daecd7b5..2c8eed19 100644
--- a/doc/metadata/rhel7/RHEL-07-040170.rst
+++ b/doc/metadata/rhel7/V-72225.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040170
+id: V-72225
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040180.rst b/doc/metadata/rhel7/V-72227.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-040180.rst
rename to doc/metadata/rhel7/V-72227.rst
index e5c805ef..8f267fbd 100644
--- a/doc/metadata/rhel7/RHEL-07-040180.rst
+++ b/doc/metadata/rhel7/V-72227.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040180
+id: V-72227
 status: exception - manual intervention
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040182.rst b/doc/metadata/rhel7/V-72229.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-040182.rst
rename to doc/metadata/rhel7/V-72229.rst
index 0813ecd5..b480fafa 100644
--- a/doc/metadata/rhel7/RHEL-07-040182.rst
+++ b/doc/metadata/rhel7/V-72229.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040182
+id: V-72229
 status: exception - manual intervention
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040181.rst b/doc/metadata/rhel7/V-72231.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-040181.rst
rename to doc/metadata/rhel7/V-72231.rst
index 25b63df9..a9f28385 100644
--- a/doc/metadata/rhel7/RHEL-07-040181.rst
+++ b/doc/metadata/rhel7/V-72231.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040181
+id: V-72231
 status: exception - manual intervention
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040260.rst b/doc/metadata/rhel7/V-72233.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-040260.rst
rename to doc/metadata/rhel7/V-72233.rst
index 68f689a1..758300fa 100644
--- a/doc/metadata/rhel7/RHEL-07-040260.rst
+++ b/doc/metadata/rhel7/V-72233.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040260
+id: V-72233
 status: implemented
 tag: packages
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040261.rst b/doc/metadata/rhel7/V-72235.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-040261.rst
rename to doc/metadata/rhel7/V-72235.rst
index 95f8320b..aec22aa8 100644
--- a/doc/metadata/rhel7/RHEL-07-040261.rst
+++ b/doc/metadata/rhel7/V-72235.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040261
+id: V-72235
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040190.rst b/doc/metadata/rhel7/V-72237.rst
similarity index 90%
rename from doc/metadata/rhel7/RHEL-07-040190.rst
rename to doc/metadata/rhel7/V-72237.rst
index 58fbf4ec..41d3f18f 100644
--- a/doc/metadata/rhel7/RHEL-07-040190.rst
+++ b/doc/metadata/rhel7/V-72237.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040190
+id: V-72237
 status: implemented
 tag: sshd
 ---
@@ -26,5 +26,5 @@ Ansible variable:
     ``ClientAliveCountMax`` specifies how many of these messages are sent
     without receiving a response.
 
-    Deployers should refer to :ref:`stig-RHEL-07-040191` to customize the
+    Deployers should refer to :ref:`stig-V-72241` to customize the
     ``ClientAliveCountMax`` setting.
diff --git a/doc/metadata/rhel7/V-72239.rst b/doc/metadata/rhel7/V-72239.rst
new file mode 100644
index 00000000..8461af0f
--- /dev/null
+++ b/doc/metadata/rhel7/V-72239.rst
@@ -0,0 +1,7 @@
+---
+id: V-72239
+status: implemented
+tag: sshd
+---
+
+This STIG is already applied by the changes for :ref:`stig-V-72249`.
diff --git a/doc/metadata/rhel7/RHEL-07-040191.rst b/doc/metadata/rhel7/V-72241.rst
similarity index 90%
rename from doc/metadata/rhel7/RHEL-07-040191.rst
rename to doc/metadata/rhel7/V-72241.rst
index d3e1f4a8..ea6263a0 100644
--- a/doc/metadata/rhel7/RHEL-07-040191.rst
+++ b/doc/metadata/rhel7/V-72241.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040191
+id: V-72241
 status: implemented
 tag: sshd
 ---
@@ -26,5 +26,5 @@ the following Ansible variable.
     ``ClientAliveCountMax`` specifies how many of these messages are sent
     without receiving a response.
 
-    Deployers should refer to :ref:`stig-RHEL-07-040190` to customize the
+    Deployers should refer to :ref:`stig-V-72237` to customize the
     ``ClientAliveInterval`` setting.
diff --git a/doc/metadata/rhel7/RHEL-07-040334.rst b/doc/metadata/rhel7/V-72243.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-040334.rst
rename to doc/metadata/rhel7/V-72243.rst
index 4c437efc..03c547c4 100644
--- a/doc/metadata/rhel7/RHEL-07-040334.rst
+++ b/doc/metadata/rhel7/V-72243.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040334
+id: V-72243
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040301.rst b/doc/metadata/rhel7/V-72245.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-040301.rst
rename to doc/metadata/rhel7/V-72245.rst
index 905ae307..b79a7af0 100644
--- a/doc/metadata/rhel7/RHEL-07-040301.rst
+++ b/doc/metadata/rhel7/V-72245.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040301
+id: V-72245
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040310.rst b/doc/metadata/rhel7/V-72247.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-040310.rst
rename to doc/metadata/rhel7/V-72247.rst
index e0fe555c..07b29567 100644
--- a/doc/metadata/rhel7/RHEL-07-040310.rst
+++ b/doc/metadata/rhel7/V-72247.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040310
+id: V-72247
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040332.rst b/doc/metadata/rhel7/V-72249.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-040332.rst
rename to doc/metadata/rhel7/V-72249.rst
index 7cec9d06..b9e6e39c 100644
--- a/doc/metadata/rhel7/RHEL-07-040332.rst
+++ b/doc/metadata/rhel7/V-72249.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040332
+id: V-72249
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040590.rst b/doc/metadata/rhel7/V-72251.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-040590.rst
rename to doc/metadata/rhel7/V-72251.rst
index d5845344..6d8d99de 100644
--- a/doc/metadata/rhel7/RHEL-07-040590.rst
+++ b/doc/metadata/rhel7/V-72251.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040590
+id: V-72251
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040620.rst b/doc/metadata/rhel7/V-72253.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-040620.rst
rename to doc/metadata/rhel7/V-72253.rst
index 65d8bcfd..5fc05918 100644
--- a/doc/metadata/rhel7/RHEL-07-040620.rst
+++ b/doc/metadata/rhel7/V-72253.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040620
+id: V-72253
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040640.rst b/doc/metadata/rhel7/V-72255.rst
similarity index 91%
rename from doc/metadata/rhel7/RHEL-07-040640.rst
rename to doc/metadata/rhel7/V-72255.rst
index 8b0a92f8..1c713e40 100644
--- a/doc/metadata/rhel7/RHEL-07-040640.rst
+++ b/doc/metadata/rhel7/V-72255.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040640
+id: V-72255
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040650.rst b/doc/metadata/rhel7/V-72257.rst
similarity index 91%
rename from doc/metadata/rhel7/RHEL-07-040650.rst
rename to doc/metadata/rhel7/V-72257.rst
index fe84d740..10a1bccd 100644
--- a/doc/metadata/rhel7/RHEL-07-040650.rst
+++ b/doc/metadata/rhel7/V-72257.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040650
+id: V-72257
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040660.rst b/doc/metadata/rhel7/V-72259.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-040660.rst
rename to doc/metadata/rhel7/V-72259.rst
index 85508407..d4dd7aaf 100644
--- a/doc/metadata/rhel7/RHEL-07-040660.rst
+++ b/doc/metadata/rhel7/V-72259.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040660
+id: V-72259
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040670.rst b/doc/metadata/rhel7/V-72261.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-040670.rst
rename to doc/metadata/rhel7/V-72261.rst
index 1214fe4c..899b9004 100644
--- a/doc/metadata/rhel7/RHEL-07-040670.rst
+++ b/doc/metadata/rhel7/V-72261.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040670
+id: V-72261
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040680.rst b/doc/metadata/rhel7/V-72263.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-040680.rst
rename to doc/metadata/rhel7/V-72263.rst
index 0941e0ac..1a32d288 100644
--- a/doc/metadata/rhel7/RHEL-07-040680.rst
+++ b/doc/metadata/rhel7/V-72263.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040680
+id: V-72263
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040690.rst b/doc/metadata/rhel7/V-72265.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-040690.rst
rename to doc/metadata/rhel7/V-72265.rst
index 6457b7e3..23f75f60 100644
--- a/doc/metadata/rhel7/RHEL-07-040690.rst
+++ b/doc/metadata/rhel7/V-72265.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040690
+id: V-72265
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040700.rst b/doc/metadata/rhel7/V-72267.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-040700.rst
rename to doc/metadata/rhel7/V-72267.rst
index 953e6eef..6d3177ac 100644
--- a/doc/metadata/rhel7/RHEL-07-040700.rst
+++ b/doc/metadata/rhel7/V-72267.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040700
+id: V-72267
 status: implemented
 tag: implemented
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040210.rst b/doc/metadata/rhel7/V-72269.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-040210.rst
rename to doc/metadata/rhel7/V-72269.rst
index 650e45d3..874b32d2 100644
--- a/doc/metadata/rhel7/RHEL-07-040210.rst
+++ b/doc/metadata/rhel7/V-72269.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040210
+id: V-72269
 status: implemented
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040250.rst b/doc/metadata/rhel7/V-72271.rst
similarity index 98%
rename from doc/metadata/rhel7/RHEL-07-040250.rst
rename to doc/metadata/rhel7/V-72271.rst
index 06ee2721..ce0e5d69 100644
--- a/doc/metadata/rhel7/RHEL-07-040250.rst
+++ b/doc/metadata/rhel7/V-72271.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040250
+id: V-72271
 status: opt-in
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040290.rst b/doc/metadata/rhel7/V-72273.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-040290.rst
rename to doc/metadata/rhel7/V-72273.rst
index 38a4335e..89f99140 100644
--- a/doc/metadata/rhel7/RHEL-07-040290.rst
+++ b/doc/metadata/rhel7/V-72273.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040290
+id: V-72273
 status: opt-in
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040300.rst b/doc/metadata/rhel7/V-72275.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-040300.rst
rename to doc/metadata/rhel7/V-72275.rst
index 8b4f72af..4cfb5c3e 100644
--- a/doc/metadata/rhel7/RHEL-07-040300.rst
+++ b/doc/metadata/rhel7/V-72275.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040300
+id: V-72275
 status: verification only
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040330.rst b/doc/metadata/rhel7/V-72277.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-040330.rst
rename to doc/metadata/rhel7/V-72277.rst
index ffc4d77e..b80032b5 100644
--- a/doc/metadata/rhel7/RHEL-07-040330.rst
+++ b/doc/metadata/rhel7/V-72277.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040330
+id: V-72277
 status: opt-in
 tag: auth
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040331.rst b/doc/metadata/rhel7/V-72279.rst
similarity index 68%
rename from doc/metadata/rhel7/RHEL-07-040331.rst
rename to doc/metadata/rhel7/V-72279.rst
index 246aa284..80b7d7a4 100644
--- a/doc/metadata/rhel7/RHEL-07-040331.rst
+++ b/doc/metadata/rhel7/V-72279.rst
@@ -1,9 +1,9 @@
 ---
-id: RHEL-07-040331
+id: V-72279
 status: implemented
 tag: auth
 ---
 
 This control is implemented by the tasks for another control:
 
-* :ref:`stig-RHEL-07-040330`
+* :ref:`stig-V-72277`
diff --git a/doc/metadata/rhel7/RHEL-07-040320.rst b/doc/metadata/rhel7/V-72281.rst
similarity index 89%
rename from doc/metadata/rhel7/RHEL-07-040320.rst
rename to doc/metadata/rhel7/V-72281.rst
index 1686ae53..f9513a68 100644
--- a/doc/metadata/rhel7/RHEL-07-040320.rst
+++ b/doc/metadata/rhel7/V-72281.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040320
+id: V-72281
 status: implemented
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040350.rst b/doc/metadata/rhel7/V-72283.rst
similarity index 97%
rename from doc/metadata/rhel7/RHEL-07-040350.rst
rename to doc/metadata/rhel7/V-72283.rst
index e52bd234..21113080 100644
--- a/doc/metadata/rhel7/RHEL-07-040350.rst
+++ b/doc/metadata/rhel7/V-72283.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040350
+id: V-72283
 status: implemented
 tag: kernel
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040410.rst b/doc/metadata/rhel7/V-72285.rst
similarity index 68%
rename from doc/metadata/rhel7/RHEL-07-040410.rst
rename to doc/metadata/rhel7/V-72285.rst
index d29f0a22..a1328366 100644
--- a/doc/metadata/rhel7/RHEL-07-040410.rst
+++ b/doc/metadata/rhel7/V-72285.rst
@@ -1,9 +1,9 @@
 ---
-id: RHEL-07-040410
+id: V-72285
 status: implemented
 tag: kernel
 ---
 
 This control is implemented by the tasks for another control:
 
-* :ref:`stig-RHEL-07-040421`
+* :ref:`stig-V-72283`
diff --git a/doc/metadata/rhel7/RHEL-07-040380.rst b/doc/metadata/rhel7/V-72287.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-040380.rst
rename to doc/metadata/rhel7/V-72287.rst
index 8f8e9c8c..86f9f0f8 100644
--- a/doc/metadata/rhel7/RHEL-07-040380.rst
+++ b/doc/metadata/rhel7/V-72287.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040380
+id: V-72287
 status: implemented
 tag: kernel
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-010402.rst b/doc/metadata/rhel7/V-72289.rst
similarity index 61%
rename from doc/metadata/rhel7/RHEL-07-010402.rst
rename to doc/metadata/rhel7/V-72289.rst
index b113c00e..97469a52 100644
--- a/doc/metadata/rhel7/RHEL-07-010402.rst
+++ b/doc/metadata/rhel7/V-72289.rst
@@ -1,9 +1,9 @@
 ---
-id: RHEL-07-010402
+id: V-72289
 status: implemented
-tag: auth
+tag: sshd
 ---
 
 This control is implemented by the tasks for another control:
 
-* :ref:`stig-RHEL-07-010401`
+* :ref:`stig-V-73175`
diff --git a/doc/metadata/rhel7/RHEL-07-040420.rst b/doc/metadata/rhel7/V-72291.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-040420.rst
rename to doc/metadata/rhel7/V-72291.rst
index e4da09f1..1d170624 100644
--- a/doc/metadata/rhel7/RHEL-07-040420.rst
+++ b/doc/metadata/rhel7/V-72291.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040420
+id: V-72291
 status: implemented
 tag: kernel
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040421.rst b/doc/metadata/rhel7/V-72293.rst
similarity index 68%
rename from doc/metadata/rhel7/RHEL-07-040421.rst
rename to doc/metadata/rhel7/V-72293.rst
index b8b518bf..8d774403 100644
--- a/doc/metadata/rhel7/RHEL-07-040421.rst
+++ b/doc/metadata/rhel7/V-72293.rst
@@ -1,9 +1,9 @@
 ---
-id: RHEL-07-040421
+id: V-72293
 status: implemented
 tag: kernel
 ---
 
 This control is implemented by the tasks for another control:
 
-* :ref:`stig-RHEL-07-040420`
+* :ref:`stig-V-72291`
diff --git a/doc/metadata/rhel7/RHEL-07-040470.rst b/doc/metadata/rhel7/V-72295.rst
similarity index 91%
rename from doc/metadata/rhel7/RHEL-07-040470.rst
rename to doc/metadata/rhel7/V-72295.rst
index 16f60d4e..b4a171e8 100644
--- a/doc/metadata/rhel7/RHEL-07-040470.rst
+++ b/doc/metadata/rhel7/V-72295.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040470
+id: V-72295
 status: verification only
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040480.rst b/doc/metadata/rhel7/V-72297.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-040480.rst
rename to doc/metadata/rhel7/V-72297.rst
index 395610ce..2cb6f490 100644
--- a/doc/metadata/rhel7/RHEL-07-040480.rst
+++ b/doc/metadata/rhel7/V-72297.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040480
+id: V-72297
 status: implemented
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/V-72299.rst b/doc/metadata/rhel7/V-72299.rst
new file mode 100644
index 00000000..392d262e
--- /dev/null
+++ b/doc/metadata/rhel7/V-72299.rst
@@ -0,0 +1,7 @@
+---
+id: V-72299
+status: not implemented
+tag: packages
+---
+
+This STIG is not yet implemented.
diff --git a/doc/metadata/rhel7/RHEL-07-040500.rst b/doc/metadata/rhel7/V-72301.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-040500.rst
rename to doc/metadata/rhel7/V-72301.rst
index 46e50bb1..917bb725 100644
--- a/doc/metadata/rhel7/RHEL-07-040500.rst
+++ b/doc/metadata/rhel7/V-72301.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040500
+id: V-72301
 status: implemented
 tag: packages
 ---
@@ -12,6 +12,7 @@ installed. The package name differs between Linux distributions:
 
 Deployers can opt-out of this change by setting the following Ansible variable:
 
+
 .. code-block:: yaml
 
     security_rhel7_remove_tftp_server: no
diff --git a/doc/metadata/rhel7/RHEL-07-040540.rst b/doc/metadata/rhel7/V-72303.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-040540.rst
rename to doc/metadata/rhel7/V-72303.rst
index 63945b9c..81f1006a 100644
--- a/doc/metadata/rhel7/RHEL-07-040540.rst
+++ b/doc/metadata/rhel7/V-72303.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040540
+id: V-72303
 status: implemented
 tag: sshd
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040520.rst b/doc/metadata/rhel7/V-72305.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-040520.rst
rename to doc/metadata/rhel7/V-72305.rst
index e4af730b..e28869ff 100644
--- a/doc/metadata/rhel7/RHEL-07-040520.rst
+++ b/doc/metadata/rhel7/V-72305.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040520
+id: V-72305
 status: verification only
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040560.rst b/doc/metadata/rhel7/V-72307.rst
similarity index 95%
rename from doc/metadata/rhel7/RHEL-07-040560.rst
rename to doc/metadata/rhel7/V-72307.rst
index e1c33cbf..b8a814b2 100644
--- a/doc/metadata/rhel7/RHEL-07-040560.rst
+++ b/doc/metadata/rhel7/V-72307.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040560
+id: V-72307
 status: implemented
 tag: packages
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040730.rst b/doc/metadata/rhel7/V-72309.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-040730.rst
rename to doc/metadata/rhel7/V-72309.rst
index da9e6d09..4812e4ee 100644
--- a/doc/metadata/rhel7/RHEL-07-040730.rst
+++ b/doc/metadata/rhel7/V-72309.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040730
+id: V-72309
 status: opt-in
 tag: kernel
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040740.rst b/doc/metadata/rhel7/V-72311.rst
similarity index 92%
rename from doc/metadata/rhel7/RHEL-07-040740.rst
rename to doc/metadata/rhel7/V-72311.rst
index 46c9e2d3..dfc95b0a 100644
--- a/doc/metadata/rhel7/RHEL-07-040740.rst
+++ b/doc/metadata/rhel7/V-72311.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040740
+id: V-72311
 status: exception - manual intervention
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040580.rst b/doc/metadata/rhel7/V-72313.rst
similarity index 94%
rename from doc/metadata/rhel7/RHEL-07-040580.rst
rename to doc/metadata/rhel7/V-72313.rst
index eb21c0ca..2daf3f7e 100644
--- a/doc/metadata/rhel7/RHEL-07-040580.rst
+++ b/doc/metadata/rhel7/V-72313.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040580
+id: V-72313
 status: verification only
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040820.rst b/doc/metadata/rhel7/V-72315.rst
similarity index 88%
rename from doc/metadata/rhel7/RHEL-07-040820.rst
rename to doc/metadata/rhel7/V-72315.rst
index b04b9cd6..e2cd4f5c 100644
--- a/doc/metadata/rhel7/RHEL-07-040820.rst
+++ b/doc/metadata/rhel7/V-72315.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040820
+id: V-72315
 status: exception - manual intervention
 tag: misc
 ---
@@ -7,7 +7,7 @@ tag: misc
 The ``firewalld`` service is optionally enabled and configured in the tasks for
 another STIG control:
 
-* :ref:`stig-RHEL-07-040290`
+* :ref:`stig-V-72273`
 
 Deployers should review their ``firewalld`` ruleset regularly to ensure that
 each firewall rule is specific as possible. Each rule should allow the smallest
diff --git a/doc/metadata/rhel7/RHEL-07-040830.rst b/doc/metadata/rhel7/V-72317.rst
similarity index 93%
rename from doc/metadata/rhel7/RHEL-07-040830.rst
rename to doc/metadata/rhel7/V-72317.rst
index f3ba84f1..63a94dd6 100644
--- a/doc/metadata/rhel7/RHEL-07-040830.rst
+++ b/doc/metadata/rhel7/V-72317.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040830
+id: V-72317
 status: exception - manual intervention
 tag: misc
 ---
diff --git a/doc/metadata/rhel7/RHEL-07-040860.rst b/doc/metadata/rhel7/V-72319.rst
similarity index 96%
rename from doc/metadata/rhel7/RHEL-07-040860.rst
rename to doc/metadata/rhel7/V-72319.rst
index f90e850a..c6182fc2 100644
--- a/doc/metadata/rhel7/RHEL-07-040860.rst
+++ b/doc/metadata/rhel7/V-72319.rst
@@ -1,5 +1,5 @@
 ---
-id: RHEL-07-040860
+id: V-72319
 status: implemented
 tag: kernel
 ---
diff --git a/doc/metadata/rhel7/V-72417.rst b/doc/metadata/rhel7/V-72417.rst
new file mode 100644
index 00000000..f3333da4
--- /dev/null
+++ b/doc/metadata/rhel7/V-72417.rst
@@ -0,0 +1,19 @@
+---
+id: V-72417
+status: implemented
+tag: packages
+---
+
+The STIG requires that the following multifactor authentication packages are
+installed:
+
+* authconfig
+* authconfig-gtk
+* esc
+* pam_pkcs11
+
+These packages are benign if they are not needed on a system, but
+``authconfig-gtk`` may cause some graphical dependencies to be installed
+which may not be needed on some systems.  The security role installs these
+packages, but it skips the installation of ``authconfig-gtk``. Deployers can
+install the graphical package manually if needed.
diff --git a/doc/metadata/rhel7/V-72427.rst b/doc/metadata/rhel7/V-72427.rst
new file mode 100644
index 00000000..6b8fc907
--- /dev/null
+++ b/doc/metadata/rhel7/V-72427.rst
@@ -0,0 +1,10 @@
+---
+id: V-72427
+status: exception - manual intervention
+tag: auth
+---
+
+Although the STIG requires that the ``sssd.conf`` contains both ``nss`` and
+``pam`` authentication modules, this change can be disruptive in environments
+that are already using LDAP or Active Directory for authentication. Deployers
+should make these changes only if their environment is compatible.
diff --git a/doc/metadata/rhel7/V-72433.rst b/doc/metadata/rhel7/V-72433.rst
new file mode 100644
index 00000000..31008bda
--- /dev/null
+++ b/doc/metadata/rhel7/V-72433.rst
@@ -0,0 +1,9 @@
+---
+id: V-72433
+status: exception - manual intervention
+tag: auth
+---
+
+Any adjustment to PKI authentication can cause disruptions for users. Deployers
+should verify that enabling OCSP validation is compatible with their existing
+configuration.
diff --git a/doc/metadata/rhel7/V-72435.rst b/doc/metadata/rhel7/V-72435.rst
new file mode 100644
index 00000000..8a92b91c
--- /dev/null
+++ b/doc/metadata/rhel7/V-72435.rst
@@ -0,0 +1,9 @@
+---
+id: V-72435
+status: exception - manual intervention
+tag: auth
+---
+
+Any adjustment to PKI authentication can cause disruptions for users. Deployers
+should verify that their environment is compatible with smart cards before
+requiring them for authentication.
diff --git a/doc/metadata/rhel7/V-73155.rst b/doc/metadata/rhel7/V-73155.rst
new file mode 100644
index 00000000..882640c0
--- /dev/null
+++ b/doc/metadata/rhel7/V-73155.rst
@@ -0,0 +1,9 @@
+---
+id: V-73155
+status: implemented
+tag: graphical
+---
+
+This control is implemented by the tasks for another control:
+
+* :ref:`stig-V-71891`
diff --git a/doc/metadata/rhel7/V-73157.rst b/doc/metadata/rhel7/V-73157.rst
new file mode 100644
index 00000000..a4493b77
--- /dev/null
+++ b/doc/metadata/rhel7/V-73157.rst
@@ -0,0 +1,9 @@
+---
+id: V-73157
+status: implemented
+tag: graphical
+---
+
+This control is implemented by the tasks for another control:
+
+* :ref:`stig-V-71891`
diff --git a/doc/metadata/rhel7/V-73159.rst b/doc/metadata/rhel7/V-73159.rst
new file mode 100644
index 00000000..6fe9712d
--- /dev/null
+++ b/doc/metadata/rhel7/V-73159.rst
@@ -0,0 +1,14 @@
+---
+id: V-73159
+status: opt-in
+tag: auth
+---
+
+The security role can require new or changed passwords to follow the pwquality
+rules, but this change can be disruptive for users without proper
+communication. Deployers must opt in for this change by setting the following
+variable:
+
+.. code-block:: yaml
+
+    security_enable_pwquality_password_set: yes
diff --git a/doc/metadata/rhel7/V-73161.rst b/doc/metadata/rhel7/V-73161.rst
new file mode 100644
index 00000000..76b85f25
--- /dev/null
+++ b/doc/metadata/rhel7/V-73161.rst
@@ -0,0 +1,9 @@
+---
+id: V-73161
+status: exception - manual intervention
+tag: misc
+---
+
+Deployers should review their NFS mounts to ensure they are mounted with the
+``noexec`` option. Deployers should skip this change if they execute
+applications from NFS mounts.
diff --git a/doc/metadata/rhel7/V-73163.rst b/doc/metadata/rhel7/V-73163.rst
new file mode 100644
index 00000000..7f80be97
--- /dev/null
+++ b/doc/metadata/rhel7/V-73163.rst
@@ -0,0 +1,9 @@
+---
+id: V-73163
+status: implemented
+tag: auditd
+---
+
+This control is implemented by the tasks for another control:
+
+* :ref:`stig-V-72087`
diff --git a/doc/metadata/rhel7/V-73165.rst b/doc/metadata/rhel7/V-73165.rst
new file mode 100644
index 00000000..36b3f6d0
--- /dev/null
+++ b/doc/metadata/rhel7/V-73165.rst
@@ -0,0 +1,9 @@
+---
+id: V-73165
+status: implemented
+tag: auditd
+---
+
+This control is implemented by the tasks for another control:
+
+* :ref:`stig-V-72197`
diff --git a/doc/metadata/rhel7/V-73167.rst b/doc/metadata/rhel7/V-73167.rst
new file mode 100644
index 00000000..2e7db141
--- /dev/null
+++ b/doc/metadata/rhel7/V-73167.rst
@@ -0,0 +1,9 @@
+---
+id: V-73167
+status: implemented
+tag: auditd
+---
+
+This control is implemented by the tasks for another control:
+
+* :ref:`stig-V-72197`
diff --git a/doc/metadata/rhel7/V-73171.rst b/doc/metadata/rhel7/V-73171.rst
new file mode 100644
index 00000000..e71c1bfa
--- /dev/null
+++ b/doc/metadata/rhel7/V-73171.rst
@@ -0,0 +1,9 @@
+---
+id: V-73171
+status: implemented
+tag: auditd
+---
+
+This control is implemented by the tasks for another control:
+
+* :ref:`stig-V-72197`
diff --git a/doc/metadata/rhel7/V-73173.rst b/doc/metadata/rhel7/V-73173.rst
new file mode 100644
index 00000000..3da26310
--- /dev/null
+++ b/doc/metadata/rhel7/V-73173.rst
@@ -0,0 +1,9 @@
+---
+id: V-73173
+status: implemented
+tag: auditd
+---
+
+This control is implemented by the tasks for another control:
+
+* :ref:`stig-V-72197`
diff --git a/doc/metadata/rhel7/RHEL-07-040351.rst b/doc/metadata/rhel7/V-73175.rst
similarity index 68%
rename from doc/metadata/rhel7/RHEL-07-040351.rst
rename to doc/metadata/rhel7/V-73175.rst
index f7112b69..d965b2bc 100644
--- a/doc/metadata/rhel7/RHEL-07-040351.rst
+++ b/doc/metadata/rhel7/V-73175.rst
@@ -1,9 +1,9 @@
 ---
-id: RHEL-07-040351
+id: V-73175
 status: implemented
 tag: kernel
 ---
 
 This control is implemented by the tasks for another control:
 
-* :ref:`stig-RHEL-07-040350`
+* :ref:`stig-V-72293`
diff --git a/doc/metadata/rhel7/V-73177.rst b/doc/metadata/rhel7/V-73177.rst
new file mode 100644
index 00000000..de7ee5bd
--- /dev/null
+++ b/doc/metadata/rhel7/V-73177.rst
@@ -0,0 +1,9 @@
+---
+id: V-73177
+status: exception - manual intervention
+tag: misc
+---
+
+Deployers should review the configuration of any wireless networking device
+connected to the system to ensure it must be enabled. The STIG requires that
+all wireless network devices are enabled unless required.
diff --git a/doc/metadata/stig_to_rst.py b/doc/metadata/stig_to_rst.py
new file mode 100755
index 00000000..87493a5e
--- /dev/null
+++ b/doc/metadata/stig_to_rst.py
@@ -0,0 +1,30 @@
+#!/usr/bin/env python
+# Copyright 2016, Rackspace US, Inc.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+"""Convert STIG XML to RST for easier reading."""
+import os
+import xmltodict
+
+SCRIPT_DIR = os.path.dirname(os.path.abspath(__file__))
+xml_file = 'U_Red_Hat_Enterprise_Linux_7_STIG_V1R1_Manual-xccdf.xml'
+with open('{}/{}'.format(SCRIPT_DIR, xml_file), 'r') as f:
+    xmldict = xmltodict.parse(f.read())
+
+for group in xmldict['Benchmark']['Group']:
+    rule = group['Rule']
+
+    print("\n{}\n{}\n".format(group['@id'], "=" * len(group['@id'])))
+    print("{}\n".format(rule['title']))
+    print("{}\n".format(rule['version']))
+    print("{}\n".format(rule['description'].encode('utf-8')))
diff --git a/doc/source/_exts/metadata-docs-rhel7.py b/doc/source/_exts/metadata-docs-rhel7.py
index 487e7770..c806357f 100644
--- a/doc/source/_exts/metadata-docs-rhel7.py
+++ b/doc/source/_exts/metadata-docs-rhel7.py
@@ -28,7 +28,7 @@ import yaml
 SCRIPT_DIR = os.path.dirname(os.path.abspath(__file__))
 METADATA_DIR = "{0}/../../metadata".format(SCRIPT_DIR)
 DOC_SOURCE_DIR = "{0}/..".format(SCRIPT_DIR)
-XCCDF_FILE = 'U_Red_Hat_Enterprise_Linux_7_STIG_V1R0-2_Manual-xccdf.xml'
+XCCDF_FILE = 'U_Red_Hat_Enterprise_Linux_7_STIG_V1R1_Manual-xccdf.xml'
 XCCDF_NAMESPACE = {'x': 'http://checklists.nist.gov/xccdf/1.1'}
 
 
@@ -235,6 +235,7 @@ def generate_docs():
         rule['description'] = {x.tag: x.text for x in temp.iter()}
 
         # Get the deployer notes from YAML
+        print(rule['id'])
         deployer_notes = get_deployer_notes(rule['id'])
         rule['deployer_notes'] = deployer_notes
 
diff --git a/doc/source/developer-guide.rst b/doc/source/developer-guide.rst
index ec327aed..0349fac0 100644
--- a/doc/source/developer-guide.rst
+++ b/doc/source/developer-guide.rst
@@ -35,9 +35,9 @@ STIG configuration. The frontmatter is followed by the text of the deployer
 note itself.
 
 All of the notes are found within ``doc/metadata/rhel7``. Here is an example
-of RHEL-07-020210:
+of V-71989:
 
-.. literalinclude:: ../metadata/rhel7/RHEL-07-020210.rst
+.. literalinclude:: ../metadata/rhel7/V-71989.rst
    :language: yaml
 
 The block after the first three dashes (``---``) is the metadata. The metadata
diff --git a/doc/source/special-notes.rst b/doc/source/special-notes.rst
index 7f4ed437..f3959895 100644
--- a/doc/source/special-notes.rst
+++ b/doc/source/special-notes.rst
@@ -114,7 +114,7 @@ security against attacks. The security role will enable SELinux on CentOS
 systems and enable AppArmor on Ubuntu systems.
 
 For more information on how these changes are applied, refer to the
-documentation for :ref:`RHEL-07-020210 <stig-RHEL-07-020210>`.
+documentation for :ref:`V-71989 <stig-V-71989>`.
 
 SSH server
 ----------
diff --git a/releasenotes/notes/stig-rhel7-version-1-renumbering-fiesta-aa047fea3ea35e74.yaml b/releasenotes/notes/stig-rhel7-version-1-renumbering-fiesta-aa047fea3ea35e74.yaml
new file mode 100644
index 00000000..b725d543
--- /dev/null
+++ b/releasenotes/notes/stig-rhel7-version-1-renumbering-fiesta-aa047fea3ea35e74.yaml
@@ -0,0 +1,20 @@
+---
+prelude: >
+    The first release of the Red Hat Enterprise Linux 7 STIG was entirely
+    renumbered from the pre-release versions. Many of the STIG configurations
+    simply changed numbers, but some were removed or changed. A few new
+    configurations were added as well.
+security:
+  - |
+    The latest version of the RHEL 7 STIG requires that a standard login banner
+    is presented to users when they log into the system (V-71863). The
+    security role now deploys a login banner that is used for console and ssh
+    sessions.
+  - |
+    The ``cn_map`` permissions and ownership adjustments included as part of
+    RHEL-07-040070 and RHEL-07-040080 has been removed. This STIG
+    configuration was removed in the most recent release of the RHEL 7 STIG.
+  - |
+    The PKI-based authentication checks for RHEL-07-040030, RHEL-07-040040,
+    and RHEL-07-040050 are no longer included in the RHEL 7 STIG. The tasks
+    and documentation for these outdated configurations are removed.
diff --git a/tasks/rhel7stig/aide.yml b/tasks/rhel7stig/aide.yml
index 6afceca7..0c4110d6 100644
--- a/tasks/rhel7stig/aide.yml
+++ b/tasks/rhel7stig/aide.yml
@@ -29,7 +29,7 @@
   tags:
     - medium
     - aide
-    - RHEL-07-020130
+    - V-71973
 
 - name: Check to see if AIDE database is already in place
   stat:
@@ -50,7 +50,7 @@
   tags:
     - medium
     - aide
-    - RHEL-07-020130
+    - V-71973
 
 # NOTE(mhayden): This is only needed for CentOS 7 and RHEL 7 since Ubuntu
 # copies the new AIDE database into place automatically with its AIDE wrapper
@@ -64,7 +64,7 @@
   tags:
     - medium
     - aide
-    - RHEL-07-020130
+    - V-71973
 
 # NOTE(mhayden): This is only needed for CentOS 7 and RHEL 7 since the AIDE
 # package doesn't come with a cron job file. Ubuntu packages a cron job for
@@ -81,10 +81,10 @@
   tags:
     - medium
     - aide
-    - RHEL-07-020140
+    - V-71975
 
 # NOTE(mhayden): CentOS/RHEL already provide a very strict AIDE configuration
-# that meets the requirements of RHEL-07-021600 and RHEL-07-021610. That config
+# that meets the requirements of V-72069 and V-72071. That config
 # is borrowed for Ubuntu 16.04 here.
 - name: Configure AIDE to verify additional properties
   blockinfile:
@@ -97,6 +97,6 @@
   tags:
     - low
     - aide
-    - RHEL-07-021600
-    - RHEL-07-021610
-    - RHEL-07-021620
+    - V-72069
+    - V-72071
+    - V-72073
diff --git a/tasks/rhel7stig/apt.yml b/tasks/rhel7stig/apt.yml
index d87835a5..d4781c08 100644
--- a/tasks/rhel7stig/apt.yml
+++ b/tasks/rhel7stig/apt.yml
@@ -25,43 +25,43 @@
   when:
     - not check_mode | bool
 
-- name: RHEL-07-010020 - Get files with invalid checksums (apt)
+- name: V-71855 - Get files with invalid checksums (apt)
   shell: "grep -v OK$ {{ temp_dir }}/debsums.txt | awk '{ print $1 }'"
-  register: rhel_07_010020_files
+  register: invalid_checksum_files
   changed_when: False
   when:
     - not check_mode | bool
     - ansible_os_family | lower == 'debian'
   tags:
     - high
-    - RHEL-07-010020
+    - V-71855
 
-- name: RHEL-07-010020 - Create comma-separated list
+- name: V-71855 - Create comma-separated list
   set_fact:
-    rhel_07_010020_violations: "{{ rhel_07_010020_files.stdout_lines | default([]) | join(', ') }}"
+    invalid_checksum_files_violations: "{{ invalid_checksum_files.stdout_lines | default([]) | join(', ') }}"
   when:
-    - rhel_07_010020_files is defined
-    - rhel_07_010020_files.stdout is defined
+    - invalid_checksum_files is defined
+    - invalid_checksum_files.stdout is defined
   tags:
     - high
-    - RHEL-07-010020
+    - V-71855
 
-- name: RHEL-07-010020 - The cryptographic hash of system files and commands must match vendor values (apt)
+- name: V-71855 - The cryptographic hash of system files and commands must match vendor values (apt)
   debug:
     msg: >
       The following files have checksums that differ from the checksum provided
       with their package. Each of these should be verified manually to ensure
       they have not been modified by an unauthorized user:
-      {{ rhel_07_010020_violations }}
+      {{ invalid_checksum_files_violations }}
   when:
     - ansible_os_family | lower == 'debian'
-    - rhel_07_010020_files is defined
-    - rhel_07_010020_files.stdout is defined
+    - invalid_checksum_files is defined
+    - invalid_checksum_files.stdout is defined
   tags:
     - high
-    - RHEL-07-010020
+    - V-71855
 
-# See the documentation for RHEL-07-020150 for more details on this check.
+# See the documentation for V-71977 for more details on this check.
 - name: Search for AllowUnauthenticated in /etc/apt/apt.conf.d/
   command: grep -r '^[^#].*AllowUnauthenticated \"true\"' /etc/apt/apt.conf.d/
   register: gpgcheck_result
@@ -69,7 +69,7 @@
   failed_when: False
   check_mode: no
 
-- name: RHEL-07-020150 - Package management tool must verify authenticity of packages
+- name: V-71977 - Package management tool must verify authenticity of packages
   debug:
     msg: "Remove AllowUnauthenticated from files in /etc/apt/apt.conf.d/ to ensure packages are verified."
   when:
@@ -77,9 +77,9 @@
     - gpgcheck_result.rc == 0
   tags:
     - high
-    - RHEL-07-020150
+    - V-71977
 
-- name: RHEL-07-020151 - Package management tool must verify authenticity of locally-installed packages
+- name: V-71979 - Package management tool must verify authenticity of locally-installed packages
   lineinfile:
     dest: /etc/dpkg/dpkg.cfg
     regexp: "^(#)?no-debsig"
@@ -89,4 +89,4 @@
     - security_enable_gpgcheck_packages_local | bool
   tags:
     - high
-    - RHEL-07-020151
+    - V-71979
diff --git a/tasks/rhel7stig/auditd.yml b/tasks/rhel7stig/auditd.yml
index ebc1eb76..bdf393a3 100644
--- a/tasks/rhel7stig/auditd.yml
+++ b/tasks/rhel7stig/auditd.yml
@@ -29,7 +29,7 @@
   tags:
     - always
 
-- name: RHEL-07-030330 - The operating system must off-load audit records onto a different system or media from the system being audited
+- name: V-72083 - The operating system must off-load audit records onto a different system or media from the system being audited
   lineinfile:
     dest: /etc/audisp/audisp-remote.conf
     regexp: "^(#)?remote_server"
@@ -42,9 +42,9 @@
   tags:
     - medium
     - auditd
-    - RHEL-07-030330
+    - V-72083
 
-- name: RHEL-07-030331 - The operating system must encrypt the transfer of audit records off-loaded onto a different system or media from the system being audited
+- name: V-72085 - The operating system must encrypt the transfer of audit records off-loaded onto a different system or media from the system being audited
   lineinfile:
     dest: /etc/audisp/audisp-remote.conf
     regexp: "^(#)?enable_krb5"
@@ -57,7 +57,7 @@
   tags:
     - medium
     - auditd
-    - RHEL-07-030331
+    - V-72085
 
 - name: Get valid system architectures for audit rules
   set_fact:
@@ -98,61 +98,61 @@
     - generate auditd rules
   tags:
     - auditd
-    - RHEL-07-030525
-    - RHEL-07-030513
-    - RHEL-07-030443
-    - RHEL-07-030390
-    - RHEL-07-030380
-    - RHEL-07-030420
-    - RHEL-07-030561
-    - RHEL-07-030671
-    - RHEL-07-030391
-    - RHEL-07-030392
-    - RHEL-07-030381
-    - RHEL-07-030383
-    - RHEL-07-030404
-    - RHEL-07-030401
-    - RHEL-07-030425
-    - RHEL-07-030670
-    - RHEL-07-030512
-    - RHEL-07-030382
-    - RHEL-07-030405
-    - RHEL-07-030402
-    - RHEL-07-030530
-    - RHEL-07-030524
-    - RHEL-07-030421
-    - RHEL-07-030422
-    - RHEL-07-030423
-    - RHEL-07-030630
-    - RHEL-07-030510
-    - RHEL-07-030540
-    - RHEL-07-030541
-    - RHEL-07-030560
-    - RHEL-07-030403
-    - RHEL-07-030750
-    - RHEL-07-030751
-    - RHEL-07-030444
-    - RHEL-07-030752
-    - RHEL-07-030441
-    - RHEL-07-030442
-    - RHEL-07-030400
-    - RHEL-07-030550
-    - RHEL-07-030521
-    - RHEL-07-030522
-    - RHEL-07-030526
-    - RHEL-07-030424
-    - RHEL-07-030531
-    - RHEL-07-030511
-    - RHEL-07-030753
-    - RHEL-07-030754
-    - RHEL-07-030514
-    - RHEL-07-030490
-    - RHEL-07-030523
-    - RHEL-07-030672
-    - RHEL-07-030673
-    - RHEL-07-030674
-    - RHEL-07-030710
-    - RHEL-07-030090
+    - V-72167
+    - V-72155
+    - V-72139
+    - V-72105
+    - V-72097
+    - V-72123
+    - V-72183
+    - V-72189
+    - V-72107
+    - V-72109
+    - V-72099
+    - V-72103
+    - V-72119
+    - V-72113
+    - V-72133
+    - V-72187
+    - V-72153
+    - V-72101
+    - V-72121
+    - V-72115
+    - V-72171
+    - V-72165
+    - V-72125
+    - V-72127
+    - V-72129
+    - V-72185
+    - V-72149
+    - V-72175
+    - V-72177
+    - V-72181
+    - V-72117
+    - V-72199
+    - V-72201
+    - V-72141
+    - V-72203
+    - V-72135
+    - V-72137
+    - V-72111
+    - V-72179
+    - V-72159
+    - V-72161
+    - V-72169
+    - V-72131
+    - V-72173
+    - V-72151
+    - V-72205
+    - V-72207
+    - V-72157
+    - V-72143
+    - V-72163
+    - V-72191
+    - V-72193
+    - V-72195
+    - V-72197
+    - V-72081
 
 - name: Adjust auditd/audispd configurations
   lineinfile:
@@ -168,10 +168,10 @@
   tags:
     - high
     - auditd
-    - RHEL-07-030340
-    - RHEL-07 030350
-    - RHEL-07 030351
-    - RHEL-07 030352
+    - V-72087
+    - V-72089
+    - V-72091
+    - V-72093
 
 - name: Ensure auditd is running and enabled at boot time
   service:
@@ -183,4 +183,4 @@
   tags:
     - high
     - auditd
-    - RHEL-07-030010
+    - V-72079
diff --git a/tasks/rhel7stig/auth.yml b/tasks/rhel7stig/auth.yml
index 2468c4b7..1ecc0e8d 100644
--- a/tasks/rhel7stig/auth.yml
+++ b/tasks/rhel7stig/auth.yml
@@ -41,15 +41,27 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010090
-    - RHEL-07-010100
-    - RHEL-07-010110
-    - RHEL-07-010120
-    - RHEL-07-010130
-    - RHEL-07-010140
-    - RHEL-07-010150
-    - RHEL-07-010160
-    - RHEL-07-010250
+    - V-71903
+    - V-71905
+    - V-71907
+    - V-71909
+    - V-71911
+    - V-71913
+    - V-71915
+    - V-71917
+    - V-71935
+
+- name: Use pwquality when passwords are changed or created
+  lineinfile:
+    dest: /etc/pam.d/passwd
+    line: "password required pam_pwquality.so retry=3"
+    state: present
+  when:
+    - security_enable_pwquality_password_set | bool
+  tags:
+    - auth
+    - medium
+    - V-73159
 
 - name: Check for SHA512 password storage in PAM
   command: "grep pam_unix.so {{ pam_password_file }}"
@@ -59,7 +71,7 @@
   tags:
     - always
 
-- name: RHEL-07-010170 - The PAM system service must be configured to store only encrypted representations of passwords.
+- name: V-71919 - The PAM system service must be configured to store only encrypted representations of passwords.
   debug:
     msg: >
       PAM is not using SHA512 for password storage. This is a security issue.
@@ -69,7 +81,7 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010170
+    - V-71919
 
 - name: Configure shadow-utils configuration
   lineinfile:
@@ -84,12 +96,12 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010180
-    - RHEL-07-010200
-    - RHEL-07-010220
-    - RHEL-07-010420
-    - RHEL-07-020230
-    - RHEL-07-020630
+    - V-71921
+    - V-71925
+    - V-71929
+    - V-71951
+    - V-71995
+    - V-72013
 
 # NOTE(mhayden): pam_faildelay expects the `delay` parameter to be in
 # microseconds.
@@ -106,9 +118,9 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010420
+    - V-71951
 
-- name: RHEL-07-010190 - User and group account administration utilities must be configured to store only encrypted representations of passwords.
+- name: V-71923 - User and group account administration utilities must be configured to store only encrypted representations of passwords.
   ini_file:
     dest: /etc/libuser.conf
     section: defaults
@@ -121,7 +133,7 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010190
+    - V-71923
 
 - name: Get all user accounts with a password lifetime limit under 24 hours
   shell: "awk -F: '$4 < 1 {print $1}' /etc/shadow"
@@ -131,10 +143,10 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010210
+    - V-71927
     - skip_ansible_lint
 
-- name: RHEL-07-010210 - Passwords must be restricted to a 24 hours/1 day minimum lifetime.
+- name: V-71927 - Passwords must be restricted to a 24 hours/1 day minimum lifetime.
   debug:
     msg: |
       Accounts were found with a minimum password lifetime limit under 24 hours:
@@ -144,9 +156,9 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010210
+    - V-71927
 
-- name: RHEL-07-010240 - Passwords must be prohibited from reuse for a minimum of five generations.
+- name: V-71933 - Passwords must be prohibited from reuse for a minimum of five generations.
   lineinfile:
     dest: "{{ pam_password_file }}"
     regexp: '^(password\s+[a-z0-9\=\[\] ]+\s+pam_unix\.so.+?)\s+(?:remember=\d+)?$'
@@ -158,9 +170,9 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010240
+    - V-71933
 
-- name: RHEL-07-010230 - Existing passwords must be restricted to a 60-day maximum lifetime.
+- name: V-71931 - Existing passwords must be restricted to a 60-day maximum lifetime.
   debug:
     msg: |
       The following user accounts have an existing password with a lifetime of
@@ -173,9 +185,9 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010230
+    - V-71931
 
-- name: RHEL-07-010260 - The system must not have accounts configured with blank or null passwords
+- name: V-71937 - The system must not have accounts configured with blank or null passwords
   lineinfile:
     dest: "{{ pam_auth_file }}"
     state: present
@@ -189,9 +201,9 @@
   tags:
     - auth
     - high
-    - RHEL-07-010260
+    - V-71937
 
-- name: RHEL-07-010260 - The system must not have accounts configured with blank or null passwords
+- name: V-71937 - The system must not have accounts configured with blank or null passwords
   lineinfile:
     dest: "{{ pam_auth_file }}"
     state: present
@@ -208,9 +220,9 @@
   tags:
     - auth
     - high
-    - RHEL-07-010260
+    - V-71937
 
-- name: RHEL-07-010280 - The operating system must disable account identifiers if the password expires.
+- name: V-71941 - The operating system must disable account identifiers if the password expires.
   lineinfile:
     dest: /etc/default/useradd
     regexp: '^[#\s]*INACTIVE'
@@ -220,9 +232,9 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010280
+    - V-71941
 
-- name: RHEL-07-010371 - If three unsuccessful logon attempts within 15 minutes occur the associated account must be locked.
+- name: V-71945 - If three unsuccessful logon attempts within 15 minutes occur the associated account must be locked.
   blockinfile:
     dest: pam_password_file
     state: present
@@ -235,9 +247,8 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010371
-    - RHEL-07-010372
-    - RHEL-07-010373
+    - V-71943
+    - V-71945
 
 - name: Check for 'nopasswd' in sudoers files
   shell: grep -ir nopasswd /etc/sudoers /etc/sudoers.d/ || echo 'not found'
@@ -246,9 +257,9 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010380
+    - V-71947
 
-- name: RHEL-07-010380 - Users must provide a password for privilege escalation.
+- name: V-71947 - Users must provide a password for privilege escalation.
   debug:
     msg: >
       The 'NOPASSWD' directive was found in the sudoers configuration files.
@@ -260,7 +271,7 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010380
+    - V-71947
     - skip_ansible_lint
 
 - name: Check for '!authenticate' in sudoers files
@@ -270,9 +281,9 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010381
+    - V-71949
 
-- name: RHEL-07-010381 - Users must re-authenticate for privilege escalation.
+- name: V-71949 - Users must re-authenticate for privilege escalation.
   debug:
     msg: >
       The '!authenticate' directive was found in the sudoers configuration
@@ -284,7 +295,7 @@
   tags:
     - auth
     - medium
-    - RHEL-07-010381
+    - V-71949
     - skip_ansible_lint
 
 - name: Check if sssd.conf exists
@@ -295,37 +306,6 @@
   tags:
     - always
 
-- name: RHEL-07-010400 - The operating system must prohibit the use of cached nss authenticators after one day.
-  ini_file:
-    dest: /etc/sssd/sssd.conf
-    section: nss
-    option: memcache_timeout
-    value: "{{ security_nss_cached_authenticator_timeout }}"
-    backup: yes
-  when:
-    - sssd_conf_check.stat.exists
-    - security_nss_cached_authenticator_timeout is defined
-  tags:
-    - auth
-    - medium
-    - RHEL-07-010400
-
-- name: RHEL-07-010401 - The operating system must prohibit the use of cached PAM authenticators after one day.
-  ini_file:
-    dest: /etc/sssd/sssd.conf
-    section: pam
-    option: offline_credentials_expiration
-    value: "{{ security_pam_offline_credentials_expiration_days }}"
-    backup: yes
-  when:
-    - sssd_conf_check.stat.exists
-    - security_pam_offline_credentials_expiration_days is defined
-  tags:
-    - auth
-    - medium
-    - RHEL-07-010401
-    - RHEL-07-010402
-
 - name: Set a GRUB 2 password for single-user/maintenance modes
   lineinfile:
     dest: "{{ grub_defaults_file }}"
@@ -339,8 +319,8 @@
   tags:
     - auth
     - high
-    - RHEL-07-010460
-    - RHEL-07-010470
+    - V-71961
+    - V-71963
 
 - name: Get all accounts with UID 0
   shell: "awk -F: '$3 == 0 {print $1}' /etc/passwd"
@@ -350,7 +330,7 @@
   tags:
     - auth
     - high
-    - RHEL-07-020310
+    - V-72005
     - skip_ansible_lint
 
 - name: Check for groups in /etc/passwd that are not in /etc/group
@@ -364,9 +344,9 @@
   tags:
     - auth
     - low
-    - RHEL-07-020300
+    - V-72003
 
-- name: RHEL-07-020310 - The root account must be the only account having unrestricted access to the system
+- name: V-72005 - The root account must be the only account having unrestricted access to the system
   fail:
     msg: |
       Only the 'root' user should have UID 0. Other users were found:
@@ -376,9 +356,9 @@
   tags:
     - auth
     - high
-    - RHEL-07-020310
+    - V-72005
 
-- name: RHEL-07-020620 - All local interactive users must have a home directory assigned in the /etc/passwd file.
+- name: V-72011 - All local interactive users must have a home directory assigned in the /etc/passwd file.
   debug:
     msg: |
       The following users do not have a home directory assigned:
@@ -389,7 +369,7 @@
   tags:
     - auth
     - medium
-    - RHEL-07-020620
+    - V-72011
 
 - name: Check each user to see if its home directory exists on the filesystem
   stat:
@@ -401,9 +381,9 @@
   tags:
     - auth
     - medium
-    - RHEL-07-020640
+    - V-72015
 
-- name: RHEL-07-020640 - All local interactive user home directories defined in the /etc/passwd file must exist.
+- name: V-72015 - All local interactive user home directories defined in the /etc/passwd file must exist.
   debug:
     msg: |
       These users have a home directory assigned, but the directory does not exist:
@@ -417,78 +397,22 @@
   tags:
     - auth
     - medium
-    - RHEL-07-020640
+    - V-72015
 
-- name: RHEL-07-040010 - The operating system must limit the number of concurrent sessions to 10 for all accounts and/or account types.
+- name: V-72217 - The operating system must limit the number of concurrent sessions to 10 for all accounts and/or account types.
   blockinfile:
     dest: /etc/security/limits.d/openstack-ansible-security-maxlogins.conf
     create: yes
     block: |
       # Deployed by the openstack-ansible-security role
-      # RHEL-07-040010 - Limit concurrent sessions for all accounts/types
+      # V-72217 - Limit concurrent sessions for all accounts/types
       * hard maxlogins {{ security_rhel7_concurrent_session_limit }}
   when:
     - security_rhel7_concurrent_session_limit is defined
   tags:
     - auth
     - low
-    - RHEL-07-040010
-
-- name: Check for PAM PKCS 11 authentication configuration
-  stat:
-    path: /etc/pam_pkcs11/pam_pkcs11.conf
-  register: pkcs11_conf_check
-  check_mode: no
-  tags:
-    - always
-
-- name: Check for ocsp_on in PAM PKCS 11 auth configuration
-  shell: 'grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf | grep -c ocsp_on'
-  register: oscp_on_check
-  changed_when: False
-  failed_when: False
-  check_mode: no
-  when:
-    - pkcs11_conf_check.stat.exists
-  tags:
-    - always
-
-- name: RHEL-07-040030 - Must Validate PKI-based auth attempts with OCSP
-  debug:
-    msg: >
-      PKI-based authentication attempts must use OCSP for certificate
-      validation. Review the documentation for RHEL-07-040030.
-  when:
-    - pkcs11_conf_check.stat.exists
-    - oscp_on_check.stdout != 3
-  tags:
-    - medium
-    - auth
-    - RHEL-07-040030
-
-- name: Check for cackey or coolkey in the PAM PKCS11 auth configuration
-  shell: 'egrep "use_pkcs11_module = (cackey|coolkey)" /etc/pam_pkcs11/pam_pkcs11.conf'
-  register: pkcs11_key_check
-  changed_when: False
-  failed_when: False
-  check_mode: no
-  when:
-    - pkcs11_conf_check.stat.exists
-  tags:
-    - always
-
-- name: RHEL-07-040040 - Must use cackey/cookey for PKCS 11 auth
-  debug:
-    msg: >
-      PKI-based authentication attempts must use cackey or coolkey.
-      Review the documentation for RHEL-07-040040.
-  when:
-    - pkcs11_conf_check.stat.exists
-    - pkcs11_key_check.stdout.rc != 0
-  tags:
-    - medium
-    - auth
-    - RHEL-07-040040
+    - V-72217
 
 - name: Check for pam_lastlog in PAM configuration
   command: "grep pam_lastlog {{ pam_postlogin_file }}"
@@ -499,17 +423,17 @@
   tags:
     - always
 
-- name: RHEL-07-040300 - Display date/time of last logon after logon
+- name: V-72275 - Display date/time of last logon after logon
   debug:
     msg: >
       The 'pam_lastlog' directive is missing in {{ pam_postlogin_file }}.
-      This is required by RHEL-07-040300.
+      This is required by V-72275.
   when:
     - pam_lastlog_check.rc != 0
   tags:
     - low
     - auth
-    - RHEL-07-040300
+    - V-72275
 
 - name: Check for .shosts or shosts.equiv files
   find:
@@ -535,5 +459,5 @@
   tags:
     - high
     - auth
-    - RHEL-07-040330
-    - RHEL-07-040331
+    - V-72277
+    - V-72279
diff --git a/tasks/rhel7stig/file_perms.yml b/tasks/rhel7stig/file_perms.yml
index 7e1e85ca..7f4e7de6 100644
--- a/tasks/rhel7stig/file_perms.yml
+++ b/tasks/rhel7stig/file_perms.yml
@@ -13,11 +13,11 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-- name: RHEL-07-010010 - Get packages with incorrect file permissions or ownership
+- name: V-71849 - Get packages with incorrect file permissions or ownership
   shell: "grep '^.M' {{ temp_dir }}/rpmverify.txt | awk '{ print $NF }'"
   args:
     warn: no
-  register: rhel_07_010010_packages
+  register: rpmverify_package_list
   changed_when: False
   when:
     - not check_mode | bool
@@ -26,27 +26,27 @@
   tags:
     - file_perms
     - high
-    - RHEL-07-010010
+    - V-71849
 
-- name: RHEL-07-010010 - Reset file permissions/ownership to vendor values
+- name: V-71849 - Reset file permissions/ownership to vendor values
   shell: "rpm {{ item[0] }} `rpm -qf {{ item[1] }}`"
   args:
     warn: no
   changed_when: false
   with_nested:
     - ['--setperms', '--setugids']
-    - "{{ rhel_07_010010_packages.stdout_lines | default([]) }}"
+    - "{{ rpmverify_package_list.stdout_lines | default([]) }}"
   when:
     - not check_mode | bool
     - ansible_os_family | lower == 'redhat'
-    - rhel_07_010010_packages is defined
-    - rhel_07_010010_packages.stdout_lines | length > 0
+    - rpmverify_package_list is defined
+    - rpmverify_package_list.stdout_lines | length > 0
   async: 300
   poll: 0
   tags:
     - file_perms
     - high
-    - RHEL-07-010010
+    - V-71849
     # don't trigger ANSIBLE0013
     - skip_ansible_lint
 
@@ -61,7 +61,7 @@
   tags:
     - always
 
-- name: RHEL-07-020360 - All files and directories must have a valid owner.
+- name: V-72007 - All files and directories must have a valid owner.
   debug:
     msg: |
       Files and directories were found that are owned by an invalid user:
@@ -73,7 +73,7 @@
   tags:
     - file_perms
     - medium
-    - RHEL-07-020360
+    - V-72007
 
 - name: Search for files/directories with an invalid group owner
   command: find / -xdev -nogroup -fstype local
@@ -86,7 +86,7 @@
   tags:
     - always
 
-- name: RHEL-07-020370 - All files and directories must have a valid group owner.
+- name: V-72009 - All files and directories must have a valid group owner.
   debug:
     msg: |
       Files and directories were found that are owned by an invalid group:
@@ -98,7 +98,7 @@
   tags:
     - file_perms
     - medium
-    - RHEL-07-020370
+    - V-72009
 
 - name: Set proper owner, group owner, and permissions on home directories
   file:
@@ -113,9 +113,9 @@
   tags:
     - medium
     - file_perms
-    - RHEL-07-020650
-    - RHEL-07-020660
-    - RHEL-07-020670
+    - V-72017
+    - V-72019
+    - V-72021
 
 - name: Find all world-writable directories
   shell: "find / -perm -002 -type d -exec ls -lLd {} \\; | tr -s ' ' | cut -d' ' -f 4,9 | grep -v ^root"
@@ -126,7 +126,7 @@
   tags:
     - always
 
-- name: RHEL-07-021050 - All world-writable directories must be group-owned by root, sys, bin, or an application group.
+- name: V-72047 - All world-writable directories must be group-owned by root, sys, bin, or an application group.
   debug:
     msg: |
       The group owners on the following world-writable directories should be examined:
@@ -136,7 +136,7 @@
   tags:
     - medium
     - file_perms
-    - RHEL-07-021050
+    - V-72047
 
 - name: Check if /etc/cron.allow exists
   stat:
@@ -156,32 +156,5 @@
   tags:
     - medium
     - file_perms
-    - RHEL-07-021190
-    - RHEL-07-021200
-
-- name: Check if cn_map file is present
-  stat:
-    path: /etc/pam_pkcs11/cn_map
-  check_mode: no
-  register: cn_map_check
-  tags:
-    - medium
-    - file_perms
-    - RHEL-07-040060
-    - RHEL-07-040070
-    - RHEL-07-040080
-
-- name: Set file permissions on cn_map file
-  file:
-    path: /etc/pam_pkcs11/cn_map
-    mode: "u-x,g-wx,o-wx"
-    owner: root
-    group: root
-  when:
-    - cn_map_check.stat.exists
-  tags:
-    - medium
-    - file_perms
-    - RHEL-07-040060
-    - RHEL-07-040070
-    - RHEL-07-040080
+    - V-72053
+    - V-72055
diff --git a/tasks/rhel7stig/graphical.yml b/tasks/rhel7stig/graphical.yml
index c4bc9a35..b86ae02a 100644
--- a/tasks/rhel7stig/graphical.yml
+++ b/tasks/rhel7stig/graphical.yml
@@ -16,34 +16,34 @@
 - name: Check if gdm is installed and configured
   stat:
     path: /etc/gdm/custom.conf
-  register: RHEL_07_010430_gdm_conf
+  register: gdm_conf_check
   check_mode: no
 
-- name: RHEL-07-010430 - The operating system must not allow an unattended or automatic logon to the system via a graphical user interface
+- name: V-71953 - The operating system must not allow an unattended or automatic logon to the system via a graphical user interface
   lineinfile:
     dest: /etc/gdm/custom.conf
     line: "^AutomaticLoginEnable=true"
     state: absent
   when:
-    - RHEL_07_010430_gdm_conf.stat.exists
+    - gdm_conf_check.stat.exists
     - security_disable_gdm_automatic_login | bool
   tags:
     - graphical
     - high
-    - RHEL-07-010430
+    - V-71953
 
-- name: RHEL-07-010431 - The operating system must not allow guest logon to the system.
+- name: V-71955 - The operating system must not allow guest logon to the system.
   lineinfile:
     dest: /etc/gdm/custom.conf
     line: "^TimedLoginEnable=true"
     state: absent
   when:
-    - RHEL_07_010430_gdm_conf.stat.exists
+    - gdm_conf_check.stat.exists
     - security_disable_gdm_timed_login | bool
   tags:
     - graphical
     - high
-    - RHEL-07-010431
+    - V-71955
 
 - name: Check for dconf profiles
   stat:
@@ -61,11 +61,9 @@
   tags:
     - graphical
     - medium
-    - RHEL-07-010060
-    - RHEL-07-010070
-    - RHEL-07-010071
-    - RHEL-07-010073
-    - RHEL-07-010074
+    - V-71891
+    - V-71893
+    - V-71901
 
 - name: Create dconf directories
   file:
@@ -80,13 +78,10 @@
   tags:
     - graphical
     - medium
-    - RHEL-07-010030
-    - RHEL-07-010031
-    - RHEL-07-010060
-    - RHEL-07-010070
-    - RHEL-07-010071
-    - RHEL-07-010073
-    - RHEL-07-010074
+    - V-71859
+    - V-71891
+    - V-71893
+    - V-71901
 
 - name: Configure graphical session locking
   template:
@@ -99,11 +94,9 @@
   tags:
     - graphical
     - medium
-    - RHEL-07-010060
-    - RHEL-07-010070
-    - RHEL-07-010071
-    - RHEL-07-010073
-    - RHEL-07-010074
+    - V-71891
+    - V-71893
+    - V-71901
 
 - name: Prevent users from changing graphical session locking configurations
   template:
@@ -116,11 +109,9 @@
   tags:
     - graphical
     - medium
-    - RHEL-07-010060
-    - RHEL-07-010070
-    - RHEL-07-010071
-    - RHEL-07-010073
-    - RHEL-07-010074
+    - V-71891
+    - V-71893
+    - V-71901
 
 - name: Create a GDM profile for displaying a login banner
   copy:
@@ -133,8 +124,7 @@
   tags:
     - graphical
     - medium
-    - RHEL-07-010030
-    - RHEL-07-010031
+    - V-71859
 
 - name: Create a GDM keyfile for machine-wide settings
   template:
@@ -150,5 +140,4 @@
   tags:
     - graphical
     - medium
-    - RHEL-07-010030
-    - RHEL-07-010031
+    - V-71859
diff --git a/tasks/rhel7stig/kernel.yml b/tasks/rhel7stig/kernel.yml
index 992dd4f9..c2097394 100644
--- a/tasks/rhel7stig/kernel.yml
+++ b/tasks/rhel7stig/kernel.yml
@@ -13,7 +13,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-- name: RHEL-07-020160 - USB mass storage must be disabled.
+- name: V-71983 - USB mass storage must be disabled.
   lineinfile:
     dest: /etc/modprobe.d/openstack-ansible-security-disable-usb-storage.conf
     line: install usb-storage /bin/true
@@ -23,7 +23,7 @@
   tags:
     - kernel
     - medium
-    - RHEL-07-020160
+    - V-71983
 
 - name: Set sysctl configurations
   sysctl:
@@ -35,14 +35,15 @@
   tags:
     - medium
     - kernel
-    - RHEL-07-040350
-    - RHEL-07-040351
-    - RHEL-07-040380
-    - RHEL-07-040410
-    - RHEL-07-040420
-    - RHEL-07-040421
-    - RHEL-07-040730
-    - RHEL-07-040860
+    - V-72283
+    - V-72285
+    - V-72287
+    - V-72289
+    - V-73175
+    - V-72291
+    - V-72293
+    - V-72309
+    - V-72319
 
 - name: Check kdump service
   command: systemctl status kdump
@@ -53,9 +54,9 @@
   tags:
     - kernel
     - medium
-    - RHEL-07-021230
+    - V-72057
 
-- name: RHEL-07-021230 - Kernel core dumps must be disabled unless needed.
+- name: V-72057 - Kernel core dumps must be disabled unless needed.
   service:
     name: kdump
     state: stopped
@@ -66,7 +67,7 @@
   tags:
     - kernel
     - medium
-    - RHEL-07-021230
+    - V-72057
 
 - name: Check if FIPS is enabled
   command: cat /proc/sys/crypto/fips_enabled
@@ -91,4 +92,4 @@
   tags:
     - high
     - misc
-    - RHEL-07-021280
+    - V-72067
diff --git a/tasks/rhel7stig/lsm.yml b/tasks/rhel7stig/lsm.yml
index d356a6d4..12649591 100644
--- a/tasks/rhel7stig/lsm.yml
+++ b/tasks/rhel7stig/lsm.yml
@@ -24,7 +24,7 @@
     - not check_mode
   tags:
     - high
-    - RHEL-07-020210
+    - V-71989
 
 # NOTE(mhayden): The "changed_when" is required here because this task will
 # always show as changed when SELinux is completely disabled. It's not possible
@@ -41,8 +41,8 @@
     - security_rhel7_enable_linux_security_module | bool
   tags:
     - high
-    - RHEL-07-020210
-    - RHEL-07-020211
+    - V-71989
+    - V-71991
 
 - name: Relabel files on next boot if SELinux mode changed
   file:
@@ -54,8 +54,8 @@
     - selinux_status_change | changed
   tags:
     - high
-    - RHEL-07-020210
-    - RHEL-07-020211
+    - V-71989
+    - V-71991
 
 # NOTE(mhayden): Ansible's find module doesn't support searching for files
 # based on SELinux contexts yet.
@@ -71,9 +71,9 @@
   tags:
     - lsm
     - medium
-    - RHEL-07-020940
+    - V-72039
 
-- name: RHEL-07-020940 - All system device files must be correctly labeled to prevent unauthorized modification.
+- name: V-72039 - All system device files must be correctly labeled to prevent unauthorized modification.
   debug:
     msg: |
       Devices were found without SELinux labels:
@@ -87,4 +87,4 @@
   tags:
     - lsm
     - medium
-    - RHEL-07-020940
+    - V-72039
diff --git a/tasks/rhel7stig/misc.yml b/tasks/rhel7stig/misc.yml
index d883dde1..34fd1749 100644
--- a/tasks/rhel7stig/misc.yml
+++ b/tasks/rhel7stig/misc.yml
@@ -22,7 +22,7 @@
   tags:
     - always
 
-- name: RHEL-07-020161 - File system automounter must be disabled unless required.
+- name: V-71985 - File system automounter must be disabled unless required.
   service:
     name: autofs
     state: stopped
@@ -33,7 +33,7 @@
   tags:
     - medium
     - misc
-    - RHEL-07-020161
+    - V-71985
 
 # This returns an exit code of 0 if it's running, 3 if it's masked.
 - name: Check if ctrl-alt-del.target is already masked
@@ -45,7 +45,7 @@
   tags:
     - always
 
-- name: RHEL-07-020220 - The x86 Ctrl-Alt-Delete key sequence must be disabled
+- name: V-71993 - The x86 Ctrl-Alt-Delete key sequence must be disabled
   command: systemctl mask ctrl-alt-del.target
   when:
     - security_rhel7_disable_ctrl_alt_delete | bool
@@ -55,7 +55,7 @@
   tags:
     - high
     - misc
-    - RHEL-07-020220
+    - V-71993
 
 - name: Check for /home on mounted filesystem
   debug:
@@ -67,7 +67,7 @@
   tags:
     - low
     - misc
-    - RHEL-07-021240
+    - V-72059
 
 - name: Check for /var on mounted filesystem
   debug:
@@ -79,7 +79,7 @@
   tags:
     - low
     - misc
-    - RHEL-07-021250
+    - V-72067
 
 - name: Check for /var/log/audit on mounted filesystem
   debug:
@@ -91,7 +91,7 @@
   tags:
     - low
     - misc
-    - RHEL-07-021260
+    - V-72063
 
 - name: Check for /tmp on mounted filesystem
   debug:
@@ -103,7 +103,7 @@
   tags:
     - low
     - misc
-    - RHEL-07-021270
+    - V-72065
 
 - name: Check if syslog output is being sent to another server
   command: 'grep "^[^#].*@" /etc/rsyslog.conf'
@@ -114,7 +114,7 @@
   tags:
     - always
 
-- name: RHEL-07-030770 - The system must send rsyslog output to a log aggregation server.
+- name: V-72209 - The system must send rsyslog output to a log aggregation server.
   debug:
     msg: Output from syslog must be sent to another server.
   when:
@@ -123,7 +123,7 @@
   tags:
     - medium
     - misc
-    - RHEL-07-030770
+    - V-72209
 
 - name: Check if ClamAV is installed
   stat:
@@ -149,7 +149,7 @@
     - restart clamav
   tags:
     - misc
-    - RHEL-07-030810
+    - V-72213
 
 - name: Set ClamAV server type as socket
   lineinfile:
@@ -165,7 +165,7 @@
     - restart clamav
   tags:
     - misc
-    - RHEL-07-030810
+    - V-72213
 
 - name: Allow automatic freshclam updates
   lineinfile:
@@ -180,7 +180,7 @@
     - restart clamav
   tags:
     - misc
-    - RHEL-07-030810
+    - V-72213
 
 - name: Update ClamAV database
   command: freshclam
@@ -192,7 +192,7 @@
   poll: 5
   tags:
     - misc
-    - RHEL-07-030810
+    - V-72213
 
 - name: Ensure ClamAV is running
   service:
@@ -204,9 +204,9 @@
     - security_enable_virus_scanner | bool
   tags:
     - misc
-    - RHEL-07-030810
+    - V-72213
 
-- name: RHEL-07-040160 - Set 10 minute timeout on communication sessions
+- name: V-72223 - Set 10 minute timeout on communication sessions
   blockinfile:
     dest: /etc/profile
     insertbefore: EOF
@@ -219,7 +219,7 @@
   tags:
     - medium
     - misc
-    - RHEL-07-040160
+    - V-72223
 
 - name: Start and enable chrony
   service:
@@ -232,7 +232,7 @@
   tags:
     - medium
     - misc
-    - RHEL-07-040210
+    - V-72269
 
 - name: Check if chrony configuration file exists
   stat:
@@ -241,7 +241,7 @@
   tags:
     - always
 
-- name: RHEL-07-040210 - Synchronize system clock (configuration file)
+- name: V-72269 - Synchronize system clock (configuration file)
   template:
     src: chrony.conf.j2
     dest: "{{ chrony_conf_file }}"
@@ -253,7 +253,7 @@
   tags:
     - medium
     - misc
-    - RHEL-07-040210
+    - V-72269
 
 # Returns 0 if installed, 3 if not installed
 - name: Check firewalld status
@@ -276,7 +276,7 @@
   tags:
     - medium
     - misc
-    - RHEL-07-040290
+    - V-72273
 
 - name: Limit new TCP connections to 25/minute and allow bursting to 100
   command: "firewall-cmd --direct --add-rule ipv4 filter IN_public_allow 0 -m tcp -p tcp -m limit --limit {{ security_enable_firewalld_rate_limit_per_minute }}/minute --limit-burst {{ security_enable_firewalld_rate_limit_burst }} -j ACCEPT"
@@ -288,7 +288,7 @@
   tags:
     - medium
     - misc
-    - RHEL-07-040250
+    - V-72271
 
 # Linting checks need to be skipped because this command doesn't create any
 # files.
@@ -302,7 +302,7 @@
     - always
     - skip_ansible_lint
 
-- name: RHEL-07-040320 - For systems using DNS resolution, at least two name servers must be configured.
+- name: V-72281 - For systems using DNS resolution, at least two name servers must be configured.
   debug:
     msg: |
       Two or more nameservers must be configured in /etc/resolv.conf.
@@ -313,7 +313,7 @@
   tags:
     - low
     - misc
-    - RHEL-07-040320
+    - V-72281
 
 - name: Check for interfaces in promiscuous mode
   shell: "ip link | grep -i promisc"
@@ -324,7 +324,7 @@
   tags:
     - always
 
-- name: RHEL-07-040470 - Network interfaces must not be in promiscuous mode.
+- name: V-72295 - Network interfaces must not be in promiscuous mode.
   debug:
     msg: >
       One or more network interfaces were found to be in promiscuous mode.
@@ -334,7 +334,7 @@
   tags:
     - medium
     - misc
-    - RHEL-07-040470
+    - V-72295
 
 - name: Check for postfix configuration file
   stat:
@@ -343,7 +343,7 @@
   tags:
     - always
 
-- name: RHEL-07-040480 - Prevent unrestricted mail relaying
+- name: V-72297 - Prevent unrestricted mail relaying
   lineinfile:
     dest: /etc/postfix/main.cf
     regexp: '^smtpd_client_restrictions'
@@ -354,7 +354,7 @@
   tags:
     - medium
     - misc
-    - RHEL-07-040480
+    - V-72297
 
 - name: Check for TFTP server configuration file
   stat:
@@ -375,7 +375,7 @@
   tags:
     - always
 
-- name: RHEL-07-040520 - TFTP must be configured to operate in secure mode
+- name: V-72305 - TFTP must be configured to operate in secure mode
   debug:
     msg: TFTP must be configured to run in secure mode with the '-s' flag.
   when:
@@ -384,7 +384,7 @@
   tags:
     - medium
     - misc
-    - RHEL-07-040520
+    - V-72305
 
 - name: Check to see if snmpd config contains public/private
   shell: 'egrep "^[^#].*(public|private)" /etc/snmp/snmpd.conf'
@@ -395,14 +395,23 @@
   tags:
     - always
 
-- name: RHEL-07-040580 - Change SNMP community strings from default.
+- name: V-72313 - Change SNMP community strings from default.
   debug:
     msg: >
       Change the SNMP community strings from the defaults of 'public' and
-      'private' to meet the requirements of RHEL-07-040580.
+      'private' to meet the requirements of V-72313.
   when:
     - snmp_public_private_check.rc == 0
   tags:
     - high
     - misc
-    - RHEL-07-040580
+    - V-72313
+
+- name: V-71863 - Display a login banner for console prompts
+  copy:
+    src: login_banner.txt
+    dest: /etc/issue.net
+  tags:
+    - medium
+    - misc
+    - V-71863
diff --git a/tasks/rhel7stig/packages.yml b/tasks/rhel7stig/packages.yml
index 7504e2be..a89925d6 100644
--- a/tasks/rhel7stig/packages.yml
+++ b/tasks/rhel7stig/packages.yml
@@ -24,17 +24,17 @@
     - auth
     - packages
     - services
-    - RHEL-07-010072
-    - RHEL-07-020000
-    - RHEL-07-020010
-    - RHEL-07-021280
-    - RHEL-07-021910
-    - RHEL-07-030810
-    - RHEL-07-040260
-    - RHEL-07-040500
-    - RHEL-07-040560
+    - V-71897
+    - V-71967
+    - V-71969
+    - V-72067
+    - V-72077
+    - V-72213
+    - V-72233
+    - V-72301
+    - V-72307
 
-- name: RHEL-07-020200 - Clean requirements/dependencies when removing packages (rpm)
+- name: V-71987 - Clean requirements/dependencies when removing packages (rpm)
   lineinfile:
     dest: /etc/yum.conf
     regexp: "^(#)?clean_requirements_on_remove"
@@ -46,9 +46,9 @@
   tags:
     - low
     - packages
-    - RHEL-07-020200
+    - V-71987
 
-- name: RHEL-07-020200 - Clean requirements/dependencies when removing packages (dpkg)
+- name: V-71987 - Clean requirements/dependencies when removing packages (dpkg)
   lineinfile:
     dest: /etc/apt/apt.conf.d/security-autoremove
     regexp: "^(#)?APT::Get::AutomaticRemove"
@@ -61,9 +61,9 @@
   tags:
     - low
     - packages
-    - RHEL-07-020200
+    - V-71987
 
-- name: RHEL-07-020250 - System security patches and updates must be installed and up to date. (yum)
+- name: V-71999 - System security patches and updates must be installed and up to date. (yum)
   lineinfile:
     dest: /etc/yum/yum-cron.conf
     regexp: "^apply_updates"
@@ -75,9 +75,9 @@
   tags:
     - packages
     - medium
-    - RHEL-07-020250
+    - V-71999
 
-- name: RHEL-07-020250 - System security patches and updates must be installed and up to date. (apt)
+- name: V-71999 - System security patches and updates must be installed and up to date. (apt)
   copy:
     src: 20auto-upgrades
     dest: /etc/apt/apt.conf.d/20auto-upgrades
@@ -87,4 +87,4 @@
   tags:
     - packages
     - cat2
-    - RHEL-07-020250
+    - V-71999
diff --git a/tasks/rhel7stig/rpm.yml b/tasks/rhel7stig/rpm.yml
index d467d170..d5d4228a 100644
--- a/tasks/rhel7stig/rpm.yml
+++ b/tasks/rhel7stig/rpm.yml
@@ -24,9 +24,9 @@
   when:
     - not rpmverify_task | skipped
 
-- name: RHEL-07-010020 - Get files with invalid checksums (rpm)
+- name: V-71855 - Get files with invalid checksums (rpm)
   shell: "grep '^..5' {{ temp_dir }}/rpmverify.txt | awk '{ print $NF }'"
-  register: rhel_07_010020_files
+  register: invalid_checksum_files
   changed_when: False
   when:
     - not check_mode | bool
@@ -34,29 +34,29 @@
   tags:
     - rpm
     - high
-    - RHEL-07-010020
+    - V-71855
 
-- name: RHEL-07-010020 - The cryptographic hash of system files and commands must match vendor values (rpm)
+- name: V-71855 - The cryptographic hash of system files and commands must match vendor values (rpm)
   debug:
     msg: |
       The following files have checksums that differ from the checksum provided
       with their package. Each of these should be verified manually to ensure
       they have not been modified by an unauthorized user.
 
-      {% for filename in rhel_07_010020_files.stdout_lines %}
+      {% for filename in invalid_checksum_files.stdout_lines %}
         {{ filename }}
       {% endfor %}
   when:
     - not check_mode | bool
     - ansible_os_family | lower == 'redhat'
-    - rhel_07_010020_files is defined
-    - rhel_07_010020_files.stdout is defined
+    - invalid_checksum_files is defined
+    - invalid_checksum_files.stdout is defined
   tags:
     - rpm
     - high
-    - RHEL-07-010020
+    - V-71855
 
-- name: RHEL-07-020150 - Require digital signatures for all packages
+- name: V-71977 - Require digital signatures for all packages
   lineinfile:
     dest: /etc/yum.conf
     regexp: "{{ item.regexp }}"
@@ -66,6 +66,6 @@
   tags:
     - rpm
     - high
-    - RHEL-07-020150
-    - RHEL-07-020151
-    - RHEL-07-020152
+    - V-71977
+    - V-71979
+    - V-71981
diff --git a/tasks/rhel7stig/sshd.yml b/tasks/rhel7stig/sshd.yml
index 7ee4bad8..6f417dee 100644
--- a/tasks/rhel7stig/sshd.yml
+++ b/tasks/rhel7stig/sshd.yml
@@ -37,8 +37,8 @@
   tags:
     - high
     - sshd
-    - RHEL-07-010040
-    - RHEL-07-040170
+    - V-71861
+    - V-72225
 
 - name: Adjust ssh server configuration based on STIG requirements
   blockinfile:
@@ -53,26 +53,25 @@
   tags:
     - high
     - sshd
-    - RHEL-07-010270
-    - RHEL-07-010440
-    - RHEL-07-010441
-    - RHEL-07-010442
-    - RHEL-07-040110
-    - RHEL-07-040170
-    - RHEL-07-040190
-    - RHEL-07-040191
-    - RHEL-07-040301
-    - RHEL-07-040310
-    - RHEL-07-040332
-    - RHEL-07-040334
-    - RHEL-07-040334
-    - RHEL-07-040540
-    - RHEL-07-040590
-    - RHEL-07-040620
-    - RHEL-07-040690
-    - RHEL-07-040700
-    - RHEL-07-040670
-    - RHEL-07-040680
+    - V-71939
+    - V-71957
+    - V-71959
+    - V-72221
+    - V-72225
+    - V-72237
+    - V-72241
+    - V-72245
+    - V-72247
+    - V-72249
+    - V-72243
+    - V-72243
+    - V-72303
+    - V-72251
+    - V-72253
+    - V-72265
+    - V-72267
+    - V-72261
+    - V-72263
 
 - name: Ensure sshd is enabled at boot time
   service:
@@ -83,7 +82,7 @@
   tags:
     - medium
     - sshd
-    - RHEL-07-040261
+    - V-72235
 
 - name: Public host key files must have mode 0644 or less
   file:
@@ -94,7 +93,7 @@
   tags:
     - medium
     - sshd
-    - RHEL-07-040640
+    - V-72255
 
 - name: Private host key files must have mode 0600 or less
   file:
@@ -105,4 +104,4 @@
   tags:
     - medium
     - sshd
-    - RHEL-07-040650
+    - V-72257
diff --git a/templates/dconf-screensaver-lock.j2 b/templates/dconf-screensaver-lock.j2
index 3d1709b6..825befe8 100644
--- a/templates/dconf-screensaver-lock.j2
+++ b/templates/dconf-screensaver-lock.j2
@@ -1,22 +1,22 @@
 {% if security_lock_session | bool %}
 [org/gnome/desktop/session]
-# RHEL-07-010070 - The operating system must initiate a screensaver after a
+# V-71893 - The operating system must initiate a screensaver after a
 #                  15-minute period of inactivity for graphical user
 #                  interfaces.
 idle-delay={{ security_lock_session_inactive_delay }}
 
 [org/gnome/desktop/screensaver]
-# RHEL-07-010060 - The operating system must enable a user session lock until
+# V-71891 - The operating system must enable a user session lock until
 #                  that user re-establishes access using established
 #                  identification and authentication procedures.
 lock-enabled=true
 
-# RHEL-07-010074 - The operating system must initiate a session lock for
+# V-71901 - The operating system must initiate a session lock for
 #                  graphical user interfaces when the screensaver is activated.
 lock-delay={{ security_lock_session_screensaver_lock_delay }}
 
 {% if security_lock_session_when_inactive | bool %}
-# RHEL-07-010073 - The operating system must initiate a session lock for the
+# V-71893 - The operating system must initiate a session lock for the
 #                  screensaver after a period of inactivity for graphical user
 #                  interfaces.
 idle-activation-enabled=true
diff --git a/templates/dconf-session-user-config-lockout.j2 b/templates/dconf-session-user-config-lockout.j2
index 1130cfc2..64260d91 100644
--- a/templates/dconf-session-user-config-lockout.j2
+++ b/templates/dconf-session-user-config-lockout.j2
@@ -1,4 +1,4 @@
-{% if security_lock_session | bool and security_lock_session_override_user | bool %}
+{% if security_lock_session | bool %}
 /org/gnome/desktop/session/idle-delay
 /org/gnome/desktop/screensaver/lock-enabled
 /org/gnome/desktop/screensaver/lock-delay
diff --git a/templates/osas-auditd-rhel7.j2 b/templates/osas-auditd-rhel7.j2
index cfad0e38..ab138622 100644
--- a/templates/osas-auditd-rhel7.j2
+++ b/templates/osas-auditd-rhel7.j2
@@ -53,45 +53,45 @@
 {# These events are more specific and require static templating.             #}
 {#                                                                           #}
 {% if security_rhel7_audit_account_access | bool %}
-# RHEL-07-030490 - The operating system must generate audit records for all
+# V-72143 - The operating system must generate audit records for all
 # successful/unsuccessful account access count events.
--w /var/log/tallylog -p wa -k RHEL-07-030490
-# RHEL-07-030491 - The operating system must generate audit records for all
+-w /var/log/tallylog -p wa -k V-72143
+# V-72145 - The operating system must generate audit records for all
 # unsuccessful account access events.
--w /var/run/faillock -p wa -k RHEL-07-030491
-# RHEL-07-030492 - The operating system must generate audit records for all
+-w /var/run/faillock -p wa -k V-72145
+# V-72147 - The operating system must generate audit records for all
 # successful account access events.
--w /var/log/lastlog -p wa -k RHEL-07-030492
+-w /var/log/lastlog -p wa -k V-72147
 {% endif %}
 
 {% if security_rhel7_audit_sudo_config_changes | bool %}
-# RHEL-07-030523 - The operating system must generate audit records containing
+# V-72163 - The operating system must generate audit records containing
 # the full-text recording of modifications to sudo configuration files.
--w /etc/sudoers -p wa -k RHEL-07-030523
--w /etc/sudoers.d/ -p wa -k RHEL-07-030523
+-w /etc/sudoers -p wa -k V-72163
+-w /etc/sudoers.d/ -p wa -k V-72163
 {% endif %}
 
 {% if security_rhel7_audit_insmod | bool %}
-# RHEL-07-030672 - All uses of the insmod command must be audited.
--w /sbin/insmod -p x -F auid!=4294967295 -k RHEL-07-030672
+# V-72191 - All uses of the insmod command must be audited.
+-w /sbin/insmod -p x -F auid!=4294967295 -k V-72191
 {% endif %}
 
 {% if security_rhel7_audit_rmmod | bool %}
-# RHEL-07-030673 - All uses of the rmmod command must be audited.
--w /sbin/rmmod -p x -F auid!=4294967295 -k RHEL-07-030673
+# V-72193 - All uses of the rmmod command must be audited.
+-w /sbin/rmmod -p x -F auid!=4294967295 -k V-72193
 {% endif %}
 
 {% if security_rhel7_audit_modprobe | bool %}
-# RHEL-07-030674 - All uses of the modprobe command must be audited.
--w /sbin/modprobe -p x -F auid!=4294967295 -k RHEL-07-030674
+# V-72195 - All uses of the modprobe command must be audited.
+-w /sbin/modprobe -p x -F auid!=4294967295 -k V-72195
 {% endif %}
 
 {% if security_rhel7_audit_account_actions | bool %}
-# RHEL-07-030710 - The operating system must generate audit records for all
+# V-72197 - The operating system must generate audit records for all
 # account creations, modifications, disabling, and termination events.
--w /etc/group -p wa -k RHEL-07-030710
--w /etc/passwd -p wa -k RHEL-07-030710
--w /etc/gshadow -p wa -k RHEL-07-030710
--w /etc/shadow -p wa -k RHEL-07-030710
--w /etc/security/opasswd -p wa -k RHEL-07-030710
+-w /etc/group -p wa -k V-72197
+-w /etc/passwd -p wa -k V-72197
+-w /etc/gshadow -p wa -k V-72197
+-w /etc/shadow -p wa -k V-72197
+-w /etc/security/opasswd -p wa -k V-72197
 {% endif %}
diff --git a/templates/pam_faillock.j2 b/templates/pam_faillock.j2
index 28c5ed8e..7fd6f5ac 100644
--- a/templates/pam_faillock.j2
+++ b/templates/pam_faillock.j2
@@ -1,3 +1,3 @@
-# RHEL-07-010371 - If three unsuccessful logon attempts within 15 minutes occur the associated account must be locked.
+# V-71945 - If three unsuccessful logon attempts within 15 minutes occur the associated account must be locked.
 auth required pam_faillock.so preauth silent audit deny="{{ security_pam_faillock_attempts }}" "{{ security_pam_faillock_deny_root | bool | ternary('even_deny_root','') }}" fail_interval="{{ security_pam_faillock_interval }}" unlock_time="{{ security_pam_faillock_unlock_time }}"
 auth [default=die] pam_faillock.so authfail audit deny="{{ security_pam_faillock_attempts }}" "{{ security_pam_faillock_deny_root | bool | ternary('even_deny_root','') }}" fail_interval="{{ security_pam_faillock_interval }}" unlock_time="{{ security_pam_faillock_unlock_time }}"
diff --git a/templates/sshd_config_block.j2 b/templates/sshd_config_block.j2
index 0798d5b0..49e14259 100644
--- a/templates/sshd_config_block.j2
+++ b/templates/sshd_config_block.j2
@@ -1,58 +1,58 @@
 {% if security_sshd_disallow_empty_password | bool %}
-# RHEL-07-010270 / RHEL-07-010440
+# V-71939 / RHEL-07-010440
 PermitEmptyPasswords no
 {% endif %}
 {% if security_sshd_disallow_environment_override | bool %}
-# RHEL-07-010441
+# V-71957
 PermitUserEnvironment no
 {% endif %}
 {% if security_sshd_disallow_host_based_auth | bool %}
-# RHEL-07-010442
+# V-71959
 HostbasedAuthentication no
 {% endif %}
-# RHEL-07-040110
+# V-72221
 Ciphers {{ security_sshd_cipher_list }}
-# RHEL-07-040170
+# V-72225
 Banner {{ security_sshd_banner_file }}
-# RHEL-07-040190
+# V-72237
 ClientAliveInterval {{ security_sshd_client_alive_interval }}
-# RHEL-07-040191
+# V-72241
 ClientAliveCountMax {{ security_sshd_client_alive_count_max }}
 {% if security_sshd_print_last_log | bool %}
-# RHEL-07-040301
+# V-72245
 PrintLastLog yes
 {% endif %}
 {% if security_sshd_permit_root_login | bool %}
-# RHEL-07-040310
+# V-72247
 PermitRootLogin no
 {% endif %}
 {% if security_sshd_disallow_known_hosts_auth | bool %}
-# RHEL-07-040332 / RHEL-07-040333
+# V-72249 / V-72239
 IgnoreUserKnownHosts yes
 {% endif %}
 {% if security_sshd_disallow_rhosts_auth | bool %}
-# RHEL-07-040334
+# V-72243
 IgnoreRhosts yes
 {% endif %}
 {% if security_sshd_enable_x11_forwarding | bool %}
-# RHEL-07-040540
+# V-72303
 X11Forwarding yes
 {% endif %}
-# RHEL-07-040590
+# V-72251
 Protocol {{ security_sshd_protocol }}
-# RHEL-07-040620
+# V-72253
 MACs {{security_sshd_allowed_macs }}
 {% if security_sshd_enable_privilege_separation | bool %}
-# RHEL-07-040690
+# V-72265
 UsePrivilegeSeparation sandbox
 {% endif %}
-# RHEL-07-040700
+# V-72267
 Compression {{ security_sshd_compression }}
 {% if security_sshd_disable_kerberos_auth | bool %}
-# RHEL-07-040670
+# V-72261
 KerberosAuthentication no
 {% endif %}
 {% if security_sshd_enable_strict_modes| bool %}
-# RHEL-07-040680
+# V-72263
 StrictModes yes
 {% endif %}
diff --git a/vars/main.yml b/vars/main.yml
index 6935e8d0..cc647269 100644
--- a/vars/main.yml
+++ b/vars/main.yml
@@ -55,163 +55,163 @@ auditd_config:
 #
 audited_commands:
   - command: chsh
-    stig_id: RHEL-07-030525
+    stig_id: V-72167
     arch_specific: no
   - command: chage
-    stig_id: RHEL-07-030513
+    stig_id: V-72155
     arch_specific: no
   - command: chcon
-    stig_id: RHEL-07-030443
+    stig_id: V-72139
     arch_specific: no
   - command: chmod
-    stig_id: RHEL-07-030390
+    stig_id: V-72105
     arch_specific: yes
   - command: chown
-    stig_id: RHEL-07-030380
+    stig_id: V-72097
     arch_specific: yes
   - command: creat
-    stig_id: RHEL-07-030420
+    stig_id: V-72123
     arch_specific: yes
   - command: crontab
-    stig_id: RHEL-07-030561
+    stig_id: V-72183
     arch_specific: no
   - command: delete_module
-    stig_id: RHEL-07-030671
+    stig_id: V-72189
     arch_specific: yes
   - command: fchmod
-    stig_id: RHEL-07-030391
+    stig_id: V-72107
     arch_specific: yes
   - command: fchmodat
-    stig_id: RHEL-07-030392
+    stig_id: V-72109
     arch_specific: yes
   - command: fchown
-    stig_id: RHEL-07-030381
+    stig_id: V-72099
     arch_specific: yes
   - command: fchownat
-    stig_id: RHEL-07-030383
+    stig_id: V-72103
     arch_specific: yes
   - command: fremovexattr
-    stig_id: RHEL-07-030404
+    stig_id: V-72119
     arch_specific: yes
   - command: fsetxattr
-    stig_id: RHEL-07-030401
+    stig_id: V-72113
     arch_specific: yes
   - command: ftruncate
-    stig_id: RHEL-07-030425
+    stig_id: V-72133
     arch_specific: yes
   - command: init_module
-    stig_id: RHEL-07-030670
+    stig_id: V-72187
     arch_specific: yes
   - command: gpasswd
-    stig_id: RHEL-07-030512
+    stig_id: V-72153
     arch_specific: no
   - command: lchown
-    stig_id: RHEL-07-030382
+    stig_id: V-72101
     arch_specific: yes
   - command: lremovexattr
-    stig_id: RHEL-07-030405
+    stig_id: V-72121
     arch_specific: yes
   - command: lsetxattr
-    stig_id: RHEL-07-030402
+    stig_id: V-72115
     arch_specific: yes
   - command: mount
     path: /bin
-    stig_id: RHEL-07-030530
+    stig_id: V-72171
     arch_specific: no
   - command: newgrp
-    stig_id: RHEL-07-030524
+    stig_id: V-72165
     arch_specific: no
   - command: open
-    stig_id: RHEL-07-030421
+    stig_id: V-72125
     arch_specific: yes
   - command: openat
-    stig_id: RHEL-07-030422
+    stig_id: V-72127
     arch_specific: yes
   - command: open_by_handle_at
-    stig_id: RHEL-07-030423
+    stig_id: V-72129
     arch_specific: yes
   - command: pam_timestamp_check
     path: /sbin
-    stig_id: RHEL-07-030630
+    stig_id: V-72185
     arch_specific: no
   - command: passwd
-    stig_id: RHEL-07-030510
+    stig_id: V-72149
     arch_specific: no
   - command: postdrop
     path: /usr/sbin
-    stig_id: RHEL-07-030540
+    stig_id: V-72175
     arch_specific: no
   - command: postqueue
     path: /usr/sbin
-    stig_id: RHEL-07-030541
+    stig_id: V-72177
     arch_specific: no
   - command: pt_chown
     path: /usr/libexec
-    stig_id: RHEL-07-030560
+    stig_id: V-72181
     arch_specific: no
     distro: redhat
   - command: removexattr
-    stig_id: RHEL-07-030403
+    stig_id: V-72117
     arch_specific: yes
   - command: rename
-    stig_id: RHEL-07-030750
+    stig_id: V-72199
     arch_specific: yes
   - command: renameat
-    stig_id: RHEL-07-030751
+    stig_id: V-72201
     arch_specific: yes
   - command: restorecon
     path: /usr/sbin
-    stig_id: RHEL-07-030444
+    stig_id: V-72141
     arch_specific: no
   - command: rmdir
-    stig_id: RHEL-07-030752
+    stig_id: V-72203
     arch_specific: yes
   - command: semanage
     path: /usr/sbin
-    stig_id: RHEL-07-030441
+    stig_id: V-72135
     arch_specific: no
   - command: setsebool
     path: /usr/sbin
-    stig_id: RHEL-07-030442
+    stig_id: V-72137
     arch_specific: no
   - command: setxattr
-    stig_id: RHEL-07-030400
+    stig_id: V-72111
     arch_specific: yes
   - command: ssh-keysign
     path: "{{ ssh_keysign_path }}"
-    stig_id: RHEL-07-030550
+    stig_id: V-72179
     arch_specific: no
   - command: su
     path: /bin
-    stig_id: RHEL-07-030521
+    stig_id: V-72159
     arch_specific: no
   - command: sudo
-    stig_id: RHEL-07-030522
+    stig_id: V-72161
     arch_specific: no
   - command: sudoedit
     path: /bin
-    stig_id: RHEL-07-030526
+    stig_id: V-72169
     arch_specific: no
   - command: truncate
-    stig_id: RHEL-07-030424
+    stig_id: V-72131
     arch_specific: yes
   - command: umount
     path: /bin
-    stig_id: RHEL-07-030531
+    stig_id: V-72173
     arch_specific: no
   - command: unix_chkpwd
     path: /sbin
-    stig_id: RHEL-07-030511
+    stig_id: V-72151
     arch_specific: no
   - command: unlink
-    stig_id: RHEL-07-030753
+    stig_id: V-72205
     arch_specific: yes
   - command: unlinkat
-    stig_id: RHEL-07-030754
+    stig_id: V-72207
     arch_specific: yes
   - command: userhelper
     path: /usr/sbin
-    stig_id: RHEL-07-030514
+    stig_id: V-72157
     arch_specific: no
 
 ## Password quality settings
@@ -229,47 +229,47 @@ audited_commands:
 password_quality_rhel7:
   - parameter: ucredit
     value: -1
-    stig_id: RHEL-07-010090
+    stig_id: V-71903
     description: "Password must contain at least one upper-case character"
     enabled: "{{ security_pwquality_require_uppercase }}"
   - parameter: lcredit
     value: -1
-    stig_id: RHEL-07-010100
+    stig_id: V-71905
     description: "Password must contain at least one lower-case character"
     enabled: "{{ security_pwquality_require_lowercase }}"
   - parameter: dcredit
     value: -1
-    stig_id: RHEL-07-010110
+    stig_id: V-71907
     description: "Password must contain at least one numeric character"
     enabled: "{{ security_pwquality_require_numeric }}"
   - parameter: ocredit
     value: -1
-    stig_id: RHEL-07-010120
+    stig_id: V-71909
     description: "Password must contain at least one special character"
     enabled: "{{ security_pwquality_require_special }}"
   - parameter: difok
     value: 8
-    stig_id: RHEL-07-010130
+    stig_id: V-71911
     description: "Password must have at least eight characters changed"
     enabled: "{{ security_pwquality_require_characters_changed }}"
   - parameter: minclass
     value: 4
-    stig_id: RHEL-07-010140
+    stig_id: V-71913
     description: "Password must have at least four character classes changed"
     enabled: "{{ security_pwquality_require_character_classes_changed }}"
   - parameter: maxrepeat
     value: 4
-    stig_id: RHEL-07-010150
+    stig_id: V-71915
     description: "Password must have at most four characters repeated consecutively"
     enabled: "{{ security_pwquality_limit_repeated_characters }}"
   - parameter: maxclassrepeat
     value: 4
-    stig_id: RHEL-07-010160
+    stig_id: V-71917
     description: "Password must have at most four characters in the same character class repeated consecutively"
     enabled: "{{ security_pwquality_limit_repeated_character_classes }}"
   - parameter: minlen
     value: 15
-    stig_id: RHEL-07-010250
+    stig_id: V-71935
     description: "Passwords must be a minimum of 15 characters in length"
     enabled: "{{ security_pwquality_require_minimum_password_length }}"
 
@@ -286,27 +286,27 @@ password_quality_rhel7:
 shadow_utils_rhel7:
   - parameter: ENCRYPT_METHOD
     value: "{{ security_password_encrypt_method | default('') }}"
-    stig_id: RHEL-07-010180
+    stig_id: V-71921
     ansible_os_family: all
   - parameter: PASS_MIN_DAYS
     value: "{{ security_password_min_lifetime_days | default('') }}"
-    stig_id: RHEL-07-010200
+    stig_id: V-71925
     ansible_os_family: all
   - parameter: PASS_MAX_DAYS
     value: "{{ security_password_max_lifetime_days | default('') }}"
-    stig_id: RHEL-07-010220
+    stig_id: V-71929
     ansible_os_family: all
   - parameter: FAIL_DELAY
     value: "{{ security_shadow_utils_fail_delay | default('') }}"
-    stig_id: RHEL-07-010420
+    stig_id: V-71951
     ansible_os_family: RedHat
   - parameter: UMASK
     value: "{{ security_shadow_utils_umask | default('') }}"
-    stig_id: RHEL-07-020230
+    stig_id: V-71995
     ansible_os_family: all
   - parameter: CREATE_HOME
     value: "{{ security_shadow_utils_create_home | default('') }}"
-    stig_id: RHEL-07-020630
+    stig_id: V-72013
     ansible_os_family: all
 
 ## sysctl settings
@@ -341,3 +341,6 @@ sysctl_settings_rhel7:
   - name: net.ipv6.conf.all.accept_source_route
     value: 0
     enabled: "{{ security_disallow_source_routed_packet_forward_ipv6 | bool }}"
+  - name: net.ipv4.conf.default.accept_redirects
+    value: 0
+    enabled: "{{ security_disallow_icmp_redirects | bool }}"
diff --git a/vars/redhat.yml b/vars/redhat.yml
index c9119b0b..b5d1941d 100644
--- a/vars/redhat.yml
+++ b/vars/redhat.yml
@@ -52,6 +52,12 @@ stig_packages:
       - postfix
     state: "{{ security_package_state }}"
     enabled: True
+  - packages:
+      - esc
+      - pam_pkcs11
+      - authconfig
+    state: "{{ security_package_state }}"
+    enabled: "{{ security_install_multifactor_auth_packages }}"
   - packages:
       - libselinux-python
       - policycoreutils-python