diff --git a/.github/workflows/e2e-ci.yml b/.github/workflows/e2e-ci.yml
index 14b71cddc..02b93ad7b 100644
--- a/.github/workflows/e2e-ci.yml
+++ b/.github/workflows/e2e-ci.yml
@@ -8,23 +8,27 @@ on:
 
 jobs:
   build:
-    runs-on: ubuntu-22.04
-
+    # runs-on: ubuntu-22.04
+    strategy:
+      fail-fast: true
+      matrix:
+       platform: [ ubuntu-latest, macos-latest, windows-latest ]
+    runs-on: ${{ matrix.platform }}
     steps:
      - uses: actions/checkout@v4
 
-     - name: Setup Node.js
+     - name: Setup Node.js ${{ matrix.platform }}
        uses: actions/setup-node@v4
        with:
         node-version: "18"
         check-latest: true
         cache: 'npm'
 
-     - name: Install dependencies
+     - name: Install dependencies ${{ matrix.platform }}
        run: npm ci
 
-     - name: Prepack
+     - name: Prepack ${{ matrix.platform }}
        run: npm run prepack
 
-     - name: Run e2e tests
+     - name: Run e2e tests ${{ matrix.platform }}
        run: npm run test
diff --git a/.gitignore b/.gitignore
index c3b8450f6..0dbf494d0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -17,3 +17,4 @@ out
 *.html
 saf-cli.log
 CliProcessOutput.log
+deltaProcessReport.md
diff --git a/README.md b/README.md
index a948e35a3..ffe3bc0b4 100644
--- a/README.md
+++ b/README.md
@@ -1450,13 +1450,14 @@ See the wiki for more information on 👉 [Delta](https://github.com/mitre/saf/w
 Update an existing InSpec profile with updated XCCDF guidance
 
 USAGE
-  $ saf generate delta -J <value> -X <value> -o <value> [-h] [-O <value>] [-r <value>] [-T rule|group|cis|version] [-L info|warn|debug|verbose]
+  $ saf generate delta [-L info|warn|debug|verbose] [-J <value> | --interactive] [-X <value> | ] [-o <value> | ]
+    [-O <value> | ] [-r <value> | ] [-T rule|group|cis|version | ] [-M -c <value>]
 
 FLAGS
   -h, --help               Show CLI help.
-  -J, --inspecJsonFile=<value>  (required) Input execution/profile JSON file - can be generated using the "inspec json <profile path> | jq . > profile.json" command
-  -X, --xccdfXmlFile=<value>    (required) The XCCDF XML file containing the new guidance - in the form of .xml file
-  -o, --outputFolder=<value>    (required) The output folder for the updated profile - if not empty it will be overwritten
+  -J, --inspecJsonFile=<value>  (required if not --interactive) Input execution/profile JSON file - can be generated using the "inspec json <profile path> | jq . > profile.json" command
+  -X, --xccdfXmlFile=<value>    (required if not --interactive) The XCCDF XML file containing the new guidance - in the form of .xml file
+  -o, --deltaOutputDir=<value>  (required if not --interactive) The output folder for the updated profile - if not empty it will be overwritten
   -O, --ovalXmlFile=<value>     The OVAL XML file containing definitions used in the new guidance - in the form of .xml file
   -T, --idType=<option>         [default: rule] Control ID Types: 
                                 'rule' - Vulnerability IDs (ex. 'SV-XXXXX'), 
@@ -1464,6 +1465,8 @@ FLAGS
                                 'cis' - CIS Rule IDs (ex. C-1.1.1.1), 
                                 'version' - Version IDs (ex. RHEL-07-010020 - also known as STIG IDs)
                                 <options: rule|group|cis|version>
+  -M, --runMapControls          Run the approximate string matching process
+  -c, --controlsDir=<value>     The InSpec profile directory containing the controls being updated (controls Delta is processing)
   -r, --report=<value>          Output markdown report file - must have an extension of .md
 
 GLOBAL FLAGS
@@ -1472,12 +1475,16 @@ GLOBAL FLAGS
       --interactive        Collect input tags interactively (not available on all CLI commands)
 
 EXAMPLES
-  $ saf generate delta -J ./the_profile_json_file.json -X ./the_xccdf_guidance_file.xml  -o the_output_directory -O ./the_oval_file.xml -T group -r the_update_report_file.md -L debug
+  $ saf generate delta -J <profile_json_file.json> -X <xccdf_guidance_file.xml, -o <updated_controls_directory>
+
+  $ saf generate delta -J <profile_json_file.json> -X <xccdf_guidance_file.xml, -o <updated_controls_directory> -M
+    -c <controls_directory_being_processed_by_delta>
+
 ```
 [top](#generate-data-reports-and-more)
 
 #### Delta Supporting Options
-Use this process prior of running `generate delta` if the updated guidance's have new control numbers and/or to format the controls how `generate delta` will. Running this process minimizes the delta output content and makes for better and easier visualization of the modification provided by the Delta process.
+Use this process prior of running `generate delta`. The process updates the controls with metadata provided by the XCCDF guidance to include the controls name and number. Additionally it formates the control the same way the `generate delta` will. Running this process minimizes the delta output content and makes for better and easier visualization of the modification provided by the Delta process.
 
 ```
 USAGE
diff --git a/package-lock.json b/package-lock.json
index 08df8cb1d..09fd827b6 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -50,6 +50,7 @@
         "flat": "^6.0.1",
         "form-data": "^4.0.0",
         "fs-extra": "^11.1.1",
+        "fuse.js": "^7.0.0",
         "get-installed-path": "^4.0.8",
         "htmlparser2": "^9.0.0",
         "https": "^1.0.0",
@@ -10572,6 +10573,14 @@
       "integrity": "sha512-dsKNQNdj6xA3T+QlADDA7mOSlX0qiMINjn0cgr+eGHGsbSHzTabcIogz2+p/iqP1Xs6EP/sS2SbqH+brGTbq0g==",
       "dev": true
     },
+    "node_modules/fuse.js": {
+      "version": "7.0.0",
+      "resolved": "https://registry.npmjs.org/fuse.js/-/fuse.js-7.0.0.tgz",
+      "integrity": "sha512-14F4hBIxqKvD4Zz/XjDc3y94mNZN6pRv3U13Udo0lNLCWRBUsrMv2xwcF/y/Z5sV6+FQW+/ow68cHpm4sunt8Q==",
+      "engines": {
+        "node": ">=10"
+      }
+    },
     "node_modules/gensync": {
       "version": "1.0.0-beta.2",
       "resolved": "https://registry.npmjs.org/gensync/-/gensync-1.0.0-beta.2.tgz",
diff --git a/package.json b/package.json
index f6b752c55..08b07f07d 100644
--- a/package.json
+++ b/package.json
@@ -47,6 +47,7 @@
     "flat": "^6.0.1",
     "form-data": "^4.0.0",
     "fs-extra": "^11.1.1",
+    "fuse.js": "^7.0.0",
     "get-installed-path": "^4.0.8",
     "htmlparser2": "^9.0.0",
     "https": "^1.0.0",
@@ -115,7 +116,7 @@
     "helpClass": "./lib/utils/oclif/help/help",
     "theme": "./oclif-theme.json",
     "additionalHelpFlags": [
-      "-h", "--whatzUp", "--whatzup", "--tell-me-more"
+      "-h", "--tell-me-more", "--explain"
     ],
     "additionalVersionFlags": [
       "-v"
diff --git a/src/commands/convert/hdf2csv.ts b/src/commands/convert/hdf2csv.ts
index 5826ec3f5..5401a60c4 100644
--- a/src/commands/convert/hdf2csv.ts
+++ b/src/commands/convert/hdf2csv.ts
@@ -52,12 +52,12 @@ export default class HDF2CSV extends BaseCommand<typeof HDF2CSV> {
         char: 'i',
         required: false,
         exclusive: ['interactive'],
-        description: '(required if not --interactive) Input HDF file'}),
+        description: '\x1B[31m(required if not --interactive)\x1B[34m Input HDF file'}),
       output: Flags.string({
         char: 'o',
         required: false,
         exclusive: ['interactive'],
-        description: '(required if not --interactive) Output CSV file'}),
+        description: '\x1B[31m(required if not --interactive)\x1B[34m Output CSV file'}),
       fields: Flags.string({
         char: 'f',
         required: false,
diff --git a/src/commands/generate/delta.ts b/src/commands/generate/delta.ts
index 53e5043e3..3d1e16686 100644
--- a/src/commands/generate/delta.ts
+++ b/src/commands/generate/delta.ts
@@ -1,204 +1,1069 @@
+/* eslint-disable max-depth */
 import {Flags} from '@oclif/core'
 import fs from 'fs'
-import {processInSpecProfile,
+import {
+  processInSpecProfile,
   processOVAL,
   UpdatedProfileReturn,
-  updateProfileUsingXCCDF} from '@mitre/inspec-objects'
+  updateProfileUsingXCCDF,
+  processXCCDF,
+  updateControl,
+} from '@mitre/inspec-objects'
+
+// eslint-disable-next-line no-warning-comments
+// TODO: We shouldn't have to import like this, open issue to clean library up for inspec-objects
+// test failed in updating inspec-objects to address high lvl vuln
+import Profile from '@mitre/inspec-objects/lib/objects/profile'
+import Control from '@mitre/inspec-objects/lib/objects/control'
+
 import path from 'path'
 import {createWinstonLogger} from '../../utils/logging'
 import fse from 'fs-extra'
+import Fuse from 'fuse.js'
+import {execSync} from 'child_process'
+import {isEmpty} from 'lodash'
+import {
+  addToProcessLogData,
+  printBgMagentaRed,
+  printBgRed,
+  printBgRedRed,
+  printBgYellow,
+  printCyan,
+  printGreen,
+  printMagenta,
+  printRed,
+  printYellow,
+  printYellowBgGreen,
+  printYellowGreen,
+  saveProcessLogData,
+} from '../../utils/oclif/cliHelper'
 import {BaseCommand} from '../../utils/oclif/baseCommand'
+import colors from 'colors' // eslint-disable-line no-restricted-imports
+import inquirer from 'inquirer'
+import inquirerFileTreeSelection from 'inquirer-file-tree-selection-prompt'
+import {EventEmitter} from 'events'
 
 export default class GenerateDelta extends BaseCommand<typeof GenerateDelta> {
-  static readonly description = 'Update an existing InSpec profile with updated XCCDF guidance'
-
-  static readonly examples = [
-    '<%= config.bin %> <%= command.id %> -J ./the_profile_json_file.json -X ./the_xccdf_guidance_file.xml  -o the_output_directory -O ./the_oval_file.xml -T group -r the_update_report_file.md -L debug',
-  ]
+  static description = 'Update an existing InSpec profile with updated XCCDF guidance'
 
-  static readonly flags = {
-    inspecJsonFile: Flags.string({char: 'J', required: true, description: 'Input execution/profile JSON file - can be generated using the "inspec json <profile path> | jq . > profile.json" command'}),
-    xccdfXmlFile: Flags.string({char: 'X', required: true, description: 'The XCCDF XML file containing the new guidance - in the form of .xml file'}),
-    ovalXmlFile: Flags.string({char: 'O', required: false, description: 'The OVAL XML file containing definitions used in the new guidance - in the form of .xml file'}),
-    output: Flags.string({char: 'o', required: true, description: 'The output folder for the updated profile - if it is not empty, it will be overwritten'}),
-    report: Flags.string({char: 'r', required: false, description: 'Output markdown report file - must have an extension of .md'}),
+  static flags = {
+    inspecJsonFile: Flags.string({char: 'J', required: false, exclusive: ['interactive'],
+      description: '\x1B[31m(required if not --interactive)\x1B[34m Input execution/profile (list of controls the delta is being applied from) JSON file - can be generated using the "inspec json <profile path> | jq . > profile.json" command'}),
+    xccdfXmlFile: Flags.string({char: 'X', required: false, exclusive: ['interactive'],
+      description: '\x1B[31m(required if not --interactive)\x1B[34m The XCCDF XML file containing the new guidance - in the form of .xml file'}),
+    deltaOutputDir: Flags.string({char: 'o', required: false, exclusive: ['interactive'],
+      description: '\x1B[31m(required if not --interactive)\x1B[34m The output folder for the updated profile (will contain the controls that delta was applied too) - if it is not empty, it will be overwritten. Do not use the original controls directory'}),
+    ovalXmlFile: Flags.string({char: 'O', required: false, exclusive: ['interactive'],
+      description: 'The OVAL XML file containing definitions used in the new guidance - in the form of .xml file'}),
+    reportFile: Flags.string({char: 'r', required: false, exclusive: ['interactive'],
+      description: 'Output markdown report file - must have an extension of .md'}),
     idType: Flags.string({
       char: 'T',
       required: false,
+      exclusive: ['interactive'],
       default: 'rule',
       options: ['rule', 'group', 'cis', 'version'],
       description: "Control ID Types: 'rule' - Vulnerability IDs (ex. 'SV-XXXXX'), 'group' - Group IDs (ex. 'V-XXXXX'), 'cis' - CIS Rule IDs (ex. C-1.1.1.1), 'version' - Version IDs (ex. RHEL-07-010020 - also known as STIG IDs)",
     }),
+    // New flag -M for whether to try mapping controls to new profile
+    runMapControls: Flags.boolean({
+      char: 'M',
+      required: false,
+      exclusive: ['interactive'],
+      dependsOn: ['controlsDir'],
+      description: 'Run the approximate string matching process',
+    }),
+    controlsDir: Flags.string({
+      char: 'c',
+      required: false,
+      exclusive: ['interactive'],
+      description: 'The InSpec profile directory containing the controls being updated (controls Delta is processing)'}),
   }
 
-  async run() { // skipcq: JS-0044
-    const {flags} = await this.parse(GenerateDelta)
+  static readonly examples = [
+    'saf generate delta -J <profile_json_file.json> -X <xccdf_guidance_file.xml, -o <updated_controls_directory>',
+    'saf generate delta -J <profile_json_file.json> -X <xccdf_guidance_file.xml, -o <updated_controls_directory> -M -c <controls_directory_being_processed_by_delta>',
+  ]
 
-    const logger = createWinstonLogger('generate:delta', flags.logLevel)
+  // Statistics variables
+  static match = 0
+  static noMatch = 0
+  static dupMatch = 0
+  static posMisMatch = 0
+  static newXccdfControl = 0
+  static oldControlsLength = 0
+  static newControlsLength = 0
 
-    logger.warn("'saf generate delta' is currently a release candidate. Please report any questions/bugs to https://github.com/mitre/saf/issues.")
+  async run() { // skipcq: JS-0044, JS-R1005
+    const {flags} = await this.parse(GenerateDelta)
+
+    // Flag variables
+    let inspecJsonFile = ''
+    let xccdfXmlFile = ''
+    let deltaOutputDir = ''
+    let ovalXmlFile = ''
+    let reportFile = ''
+    let idType = ''
+    let runMapControls = true
+    let controlsDir = ''
+    let logLevel = ''
 
+    // Process variables
     let existingProfile: any | null = null
     let updatedXCCDF: any = {}
     let ovalDefinitions: any = {}
-
+    let processedXCCDF: any = {}
     let markDownFile = ''
     let outputProfileFolderPath = ''
+    let mappedControls: any = {}
+
+    addToProcessLogData('==================== Delta Process =====================')
+    addToProcessLogData(`Date: ${new Date().toISOString()}`)
+
+    if (flags.interactive) {
+      const interactiveFlags = await getFlags()
+      // Required flags
+      inspecJsonFile = interactiveFlags.inspecJsonFile
+      xccdfXmlFile = interactiveFlags.xccdfXmlFile
+      deltaOutputDir = interactiveFlags.deltaOutputDir
+      // Optional flags
+      ovalXmlFile = interactiveFlags.ovalXmlFile
+      reportFile = path.join(interactiveFlags.reportDirectory, interactiveFlags.reportFileName)
+      idType = interactiveFlags.idType
+      runMapControls = interactiveFlags.runMapControls
+      controlsDir = interactiveFlags.controlsDir
+      logLevel = interactiveFlags.logLevel
+    } else if (this.requiredFlagsProvided(flags)) {
+      // Required flags
+      inspecJsonFile = flags.inspecJsonFile as string
+      xccdfXmlFile = flags.xccdfXmlFile as string
+      deltaOutputDir = flags.deltaOutputDir as string
+
+      // Optional flags
+      ovalXmlFile = flags.ovalXmlFile as string
+      reportFile = flags.reportFile as string
+      idType = flags.idType
+      runMapControls = flags.runMapControls
+      controlsDir = flags.controlsDir as string
+      logLevel = flags.logLevel
+
+      // Save the flags to the log object
+      addToProcessLogData('Process Flags ===========================================')
+      for (const key in flags) {
+        if (Object.prototype.hasOwnProperty.call(flags, key)) {
+          addToProcessLogData(key + '=' + flags[key as keyof typeof flags])
+        }
+      }
+    } else {
+      return
+    }
 
-    // Process the Input execution/profile JSON file
+    addToProcessLogData('\n')
+    const logger = createWinstonLogger('generate:delta', logLevel)
+
+    logger.warn(colors.green('╔══════════════════════════════════════════════════════════════════════════════════════════════════════════════╗'))
+    logger.warn(colors.green('║ saf generate delta is officially released - report any questions/bugs to https://github.com/mitre/saf/issues ║'))
+    logger.warn(colors.green('╚══════════════════════════════════════════════════════════════════════════════════════════════════════════════╝'))
+
+    // Process the Input execution/profile JSON file. The processInSpecProfile
+    // method will throw an error if an invalid profile file is provided.
+    // NOTE: If mapping controls to new profile (using the -M) the
+    //       existingProfile variable is re-generated as the controls change.
+    logger.info('Checking if an InSpec Profile JSON file was provided...')
     try {
-      if (fs.lstatSync(flags.inspecJsonFile).isFile()) {
-        const inspecJsonFile = flags.inspecJsonFile
-        logger.debug(`Loading ${inspecJsonFile} as Profile JSON/Execution JSON`)
+      if (fs.lstatSync(inspecJsonFile).isFile()) {
+        // const inspecJsonFile = flags.inspecJsonFile
+        logger.debug(`  Loading ${inspecJsonFile} as Profile JSON/Execution JSON`)
         existingProfile = processInSpecProfile(fs.readFileSync(inspecJsonFile, 'utf8'))
-        logger.debug(`Loaded ${inspecJsonFile} as Profile JSON/Execution JSON`)
+        logger.debug(`  Loaded ${inspecJsonFile} as Profile JSON/Execution JSON`)
       }
     } catch (error: any) {
       if (error.code === 'ENOENT') {
-        logger.error(`ERROR: No entity found for: ${flags.inspecJsonFile}. Run the --help command to more information on expected input files.`)
+        logger.error(`  ERROR: No entity found for: ${inspecJsonFile}. Run the --help command to more information on expected input files.`)
         throw error
       } else {
-        logger.error(`ERROR: Unable to process Input execution/profile JSON ${flags.inspecJsonFile} because: ${error}`)
+        logger.error(`  ERROR: Unable to process Input execution/profile JSON ${inspecJsonFile} because: ${error}`)
         throw error
       }
     }
 
-    // Process the XCCDF XML file containing the new/updated profile guidance
+    // Validate that the provided XCDDF containing the new/updated profile
+    // guidance is actually an XCCDF XML file by checking the XML schema
+    // location and name space
+    // eslint-disable-next-line no-warning-comments
+    // TODO: Use an XML parser to determine if the provided XCCDF file is an
+    //       XCCDF by checking the schema location (xsi:schemaLocation) includes xccdf
+    //       and that includes an XCCDF namespace (xmlns)
+    logger.info('Checking if the provided XCCDF is valid...')
     try {
-      if (fs.lstatSync(flags.xccdfXmlFile).isFile()) {
-        const xccdfXmlFile = flags.xccdfXmlFile
+      if (fs.lstatSync(xccdfXmlFile).isFile()) {
+        // const xccdfXmlFile = flags.xccdfXmlFile
         const inputFile = fs.readFileSync(xccdfXmlFile, 'utf8')
         const inputFirstLine = inputFile.split('\n').slice(0, 10).join('').toLowerCase()
         if (inputFirstLine.includes('xccdf')) {
-          logger.debug(`Loading ${xccdfXmlFile} as XCCDF`)
+          logger.debug(`  Loading ${xccdfXmlFile} as XCCDF`)
           updatedXCCDF = inputFile
-          logger.debug(`Loaded ${xccdfXmlFile} as XCCDF`)
+          logger.debug(`  Loaded ${xccdfXmlFile} as XCCDF`)
+          // addToProcessLogData(`XCDDF file: ${xccdfXmlFile}`)
         } else {
-          logger.error(`ERROR: Unable to load ${xccdfXmlFile} as XCCDF`)
+          logger.error(`  ERROR: Unable to load ${xccdfXmlFile} as XCCDF`)
           throw new Error('Cannot load XCCDF file')
         }
 
-        logger.debug(`Loaded ${xccdfXmlFile} as XCCDF`)
+        logger.debug(`  Loaded ${xccdfXmlFile} as XCCDF`)
       } else {
         throw new Error('No benchmark (XCCDF) file was provided.')
       }
     } catch (error: any) {
       if (error.code === 'ENOENT') {
-        logger.error(`ERROR: No entity found for: ${flags.xccdfXmlFile}. Run the --help command to more information on expected input files.`)
+        logger.error(`  ERROR: No entity found for: ${xccdfXmlFile}. Run the --help command to more information on expected input files.`)
         throw error
       } else {
-        logger.error(`ERROR: Unable to process the XCCDF XML file ${flags.xccdfXmlFile} because: ${error}`)
+        logger.error(`  ERROR: Unable to process the XCCDF XML file ${xccdfXmlFile} because: ${error}`)
         throw error
       }
     }
 
     // Process the OVAL XML file
+    logger.info('Checking if an OVAL XML file was provided...')
     try {
-      if (flags.ovalXmlFile) {
-        if (fs.lstatSync(flags.ovalXmlFile).isFile()) {
-          const ovalXmlFile = flags.ovalXmlFile
+      if (ovalXmlFile) {
+        if (fs.lstatSync(ovalXmlFile).isFile()) {
+          // const ovalXmlFile = ovalXmlFile
           const inputFile = fs.readFileSync(ovalXmlFile, 'utf8')
           const inputFirstLine = inputFile.split('\n').slice(0, 10).join('').toLowerCase()
 
           if (inputFirstLine.includes('oval_definitions')) {
-            logger.debug(`Loading ${ovalXmlFile} as OVAL`)
+            logger.debug(`  Loading ${ovalXmlFile} as OVAL`)
             ovalDefinitions = processOVAL(inputFile)
-            logger.debug(`Loaded ${ovalXmlFile} as OVAL`)
+            logger.debug(`  Loaded ${ovalXmlFile} as OVAL`)
+            // addToProcessLogData(`OVAL file: ${ovalXmlFile}`)
           } else {
-            logger.error(`ERROR: Unable to load ${ovalXmlFile} as OVAL`)
+            logger.error(`  ERROR: Unable to load ${ovalXmlFile} as OVAL`)
             throw new Error('Cannot load OVAL file')
           }
         } else {
-          logger.error(`ERROR: An OVAL flag option was detected, but no file was provided, received: ${flags.ovalXmlFile}`)
+          logger.error(`  ERROR: An OVAL flag option was detected, but no file was provided, received: ${ovalXmlFile}`)
           throw new Error('No OVAL file detected')
         }
+      } else {
+        logger.debug('  An OVAL XML file was not provided')
       }
     } catch (error: any) {
       if (error.code === 'ENOENT') {
-        logger.error(`ERROR: No entity found for: ${flags.ovalXmlFile}. Run the --help command to more information on expected input files.`)
+        logger.error(`  ERROR: No entity found for: ${ovalXmlFile}. Run the --help command to more information on expected input files.`)
         throw error
       } else {
-        logger.error(`Unable to process the OVAL XML file ${flags.ovalXmlFile} because: ${error}`)
+        logger.error(`  Unable to process the OVAL XML file ${ovalXmlFile} because: ${error}`)
         throw error
       }
     }
 
+    // Process the fuzzy search logic
+    logger.info('Checking if control mapping is required...')
+    try {
+      if (runMapControls && controlsDir) {
+        logger.info('  Mapping controls (using fuzzy logic - lower value = best match) from the old profile to the new profile')
+        addToProcessLogData('Mapping controls (using fuzzy logic - lower value = best match) from the old profile to the new profile\n')
+        // Process XCCDF of new profile to get controls
+        processedXCCDF = processXCCDF(updatedXCCDF, false, idType as 'cis' | 'version' | 'rule' | 'group', ovalDefinitions)
+        // Create a dictionary mapping new control GIDs to their old control counterparts
+        mappedControls = await this.mapControls(existingProfile, processedXCCDF)
+
+        // Iterate through each mapped control
+        // key = new control, controls[key] = old control
+        const controls: { [key: string]: any } = mappedControls
+
+        // Create a directory where we are storing the newly created mapped controls
+        // Do not over right the original controls in the directory (controlsDir)
+        const mappedDir = this.createMappedDirectory(controlsDir)
+        const shortRunningDir = path.sep + path.basename(path.dirname(controlsDir))
+        const shortProfileDir = shortRunningDir + path.sep + path.basename(controlsDir)
+        const shortMappedDir = shortRunningDir + path.sep + path.basename(mappedDir)
+        // const controls + path.sep + path.basename(controlsDir)
+        logger.info('  Updating controls with new control number')
+        printCyan('Updating Controls ===========================================================================')
+
+        // For each control, modify the control file in the old controls directory
+        // then regenerate json profile
+        // eslint-disable-next-line guard-for-in
+        for (const key in controls) {
+          const sourceShortControlFile = path.join(shortProfileDir, `${controls[key]}.rb`)
+          const mappedShortControlFile = path.join(shortMappedDir, `${controls[key]}.rb`)
+
+          const sourceControlFile = path.join(controlsDir, `${controls[key]}.rb`)
+          const mappedControlFile = path.join(mappedDir, `${controls[key]}.rb`)
+
+          printYellowGreen('Mapping (From --> To): ', `${controls[key]} --> ${key}`)
+
+          let lines
+          if (fs.existsSync(sourceControlFile)) {
+            lines = fs.readFileSync(sourceControlFile, 'utf8').split('\n')
+          } else {
+            printBgRedRed('    File not found at:', ` ${sourceControlFile}\n`)
+            printRed('╔═══════════════════════════════════════════════════════════════════════════════╗')
+            printRed('║ Make sure the appropriate Input execution/profile JSON file is being used (-J)║')
+            printRed('╚═══════════════════════════════════════════════════════════════════════════════╝')
+            return
+          }
+
+          // If the key equals the controls[wey], the update_controls4delta process was ran
+          // and the controls were properly updated to the proper control number and name.
+          if (controls[key] === key) {
+            // The controls are up to date with the xccdf
+            printYellowGreen('   Control is Current: ', `${sourceShortControlFile}`)
+            // Saved processed control to the 'mapped_controls' directory
+            printYellowGreen('    Processed control: ', `${mappedShortControlFile}\n`)
+            fs.writeFileSync(mappedControlFile, lines.join('\n'))
+          } else {
+            printYellowGreen('   Processing control: ', `${sourceShortControlFile}`)
+            // Find the line with the control name and replace it with the new control name
+            // single or double quotes are used on this line, check for both
+            // Template literals (`${controls[key]}`) must be used with dynamically created regular expression (RegExp() not / ... /)
+            const controlLineIndex = lines.findIndex(line => new RegExp(`control ['"]${controls[key]}['"] do`).test(line))
+            if (controlLineIndex === -1) {
+              printBgRedRed('    Control not found:', ` ${sourceControlFile}\n`)
+            } else {
+              lines[controlLineIndex] = lines[controlLineIndex].replace(new RegExp(`control ['"]${controls[key]}['"] do`), `control '${key}' do`)
+
+              // Saved processed control to the 'mapped_controls' directory
+              printYellowGreen('    Processed control: ', `${mappedShortControlFile}`)
+              fs.writeFileSync(mappedControlFile, lines.join('\n'))
+
+              // eslint-disable-next-line no-warning-comments
+              // TODO: Maybe copy files from the source directory and rename for duplicates and to preserve source files
+              printYellowGreen('  Mapped control file: ', `${sourceShortControlFile} to reference ID ${key}`)
+              printYellowBgGreen('     New control name: ', `${key}.rb\n`)
+            }
+          }
+        }
+
+        // Regenerate the profile json based on the updated mapped controls
+        try {
+          logger.info(`  Generating the profile json using the new mapped controls on: '${mappedDir}'`)
+          // Get the directory name without the trailing "controls" directory
+          // Here we are using the newly updated (mapped) controls
+          // const profileDir = path.dirname(controlsDir)
+          // eslint-disable-next-line no-warning-comments
+          // TODO: normally it's 'inspec json ...' but vscode doesn't recognize my alias?
+          const inspecJsonFileNew = execSync(`inspec json '${mappedDir}'`, {encoding: 'utf8', maxBuffer: 50 * 1024 * 1024})
+
+          // Replace existing profile (inputted JSON of source profile to be mapped)
+          // Allow delta to take care of the rest
+          existingProfile = processInSpecProfile(inspecJsonFileNew)
+        } catch (error: any) {
+          logger.error(`  ERROR: Unable to generate the profile json because: ${error}`)
+          throw error
+        }
+      } else if (runMapControls && !controlsDir) {
+        logger.error('  If the -M (Run the approximate string matching process) is specified\n' +
+          'the -c (The InSpec profile controls directory containing the profiles to be updated) is required')
+      }
+    } catch (error: any) {
+      logger.error('ERROR: Could not process runMapControls flag. Check the --help command for more information on the -o flag.')
+      throw error
+    }
+
     // Process the output folder
+    logger.info('Checking if provided output directory exists (create is it does not, clear if exists)...')
     try {
       // Create the folder if it doesn't exist
-      if (!fs.existsSync(flags.output)) {
-        fs.mkdirSync(path.join(flags.output), {recursive: true})
+      if (!fs.existsSync(deltaOutputDir)) {
+        fs.mkdirSync(path.join(deltaOutputDir), {recursive: true})
       }
 
-      if (path.basename(flags.output) === 'controls') {
-        logger.debug(`Deleting existing profile folder ${flags.output}`)
-        fse.emptyDirSync(flags.output)
-        outputProfileFolderPath = path.dirname(flags.output)
+      if (path.basename(deltaOutputDir) === 'controls') {
+        logger.debug(`  Deleting existing profile folder ${deltaOutputDir}`)
+        fse.emptyDirSync(deltaOutputDir)
+        outputProfileFolderPath = path.dirname(deltaOutputDir)
       } else {
-        const controlDir = path.join(flags.output, 'controls')
+        const controlDir = path.join(deltaOutputDir, 'controls')
         if (fs.existsSync(controlDir)) {
-          logger.debug(`Deleting content within existing controls folder within the profile folder ${flags.output}`)
+          logger.debug(`  Deleting content within existing controls folder within the profile folder ${deltaOutputDir}`)
           fse.emptyDirSync(controlDir)
         } else {
           fse.mkdirSync(controlDir)
         }
 
-        outputProfileFolderPath = flags.output
+        outputProfileFolderPath = deltaOutputDir
       }
     } catch (error: any) {
-      logger.error(`ERROR: Could not process output ${flags.output}. Check the --help command for more information on the -o flag.`)
+      logger.error(`  ERROR: Could not process delta output directory: ${deltaOutputDir}. Check the --help command for more information on the -o flag.`)
       throw error
     }
 
     // Set the report markdown file location
-    if (flags.report) {
-      if (fs.existsSync(flags.report) && fs.lstatSync(flags.report).isDirectory()) {
+    logger.info('Checking if an output markdown report was requested...')
+    if (reportFile) {
+      if (fs.existsSync(reportFile) && fs.lstatSync(reportFile).isDirectory()) {
         // Not a file - directory provided
-        markDownFile = path.join(flags.report, 'delta.md')
-      } else if (fs.existsSync(flags.report) && fs.lstatSync(flags.report).isFile()) {
+        markDownFile = path.join(reportFile, 'delta.md')
+      } else if (fs.existsSync(reportFile) && fs.lstatSync(reportFile).isFile()) {
         // File name provided and exists - will be overwritten
-        markDownFile = flags.report
-      } else if (path.extname(flags.report) === '.md') {
-        markDownFile = flags.report
+        markDownFile = reportFile
+      } else if (path.extname(reportFile) === '.md') {
+        markDownFile = reportFile
       } else {
         markDownFile = path.join(outputProfileFolderPath, 'delta.md')
       }
+    } else {
+      logger.debug('  An output markdown reports was not requested')
     }
 
     // If all variables have been satisfied, we can generate the delta
+    // If the -M was used the delta is generated based on the mapped controls
+    logger.info('Executing the Delta process...')
     if (existingProfile && updatedXCCDF) {
       let updatedResult: UpdatedProfileReturn
-      logger.debug(`Processing XCCDF Benchmark file: ${flags.xccdfXmlFile} using ${flags.idType} id.`)
+      logger.debug(`  Processing XCCDF Benchmark file: ${flags.xccdfXmlFile} using ${idType} id.`)
       const idTypes = ['rule', 'group', 'cis', 'version']
-      if (idTypes.includes(flags.idType)) {
-        updatedResult = updateProfileUsingXCCDF(existingProfile, updatedXCCDF, flags.idType as 'cis' | 'version' | 'rule' | 'group', logger, ovalDefinitions)
+      if (idTypes.includes(idType)) {
+        updatedResult = updateProfileUsingXCCDF(existingProfile, updatedXCCDF, idType as 'cis' | 'version' | 'rule' | 'group', logger, ovalDefinitions)
       } else {
-        logger.error(`ERROR: Invalid ID Type: ${flags.idType}. Check the --help command for the available ID Type options.`)
+        logger.error(`  ERROR: Invalid ID Type: ${idType}. Check the --help command for the available ID Type options.`)
         throw new Error('Invalid ID Type')
       }
 
-      logger.debug('Computed the delta between the existing profile and updated benchmark.')
+      logger.debug('  Computed the delta between the existing profile and updated benchmark.')
 
       updatedResult.profile.controls.forEach(control => {
-        logger.debug(`Writing updated control ${control.id}.`)
-        fs.writeFileSync(path.join(outputProfileFolderPath, 'controls', `${control.id}.rb`), control.toRuby())
+        const controls = existingProfile.controls
+
+        let index = -1
+        // eslint-disable-next-line guard-for-in
+        for (const i in controls) {
+          const controlLine = controls[i].code.split('\n')[0]
+          // NOTE: The control.id can be in the form of V-123456 or SV-123456
+          //       check the entire value or just the numeric value for a match
+          if (controlLine.includes(control.id) || controlLine.includes(control.id.split('-')[1])) {
+            index = Number.parseInt(i, 10)
+            break
+          }
+        }
+
+        // Call the .toRuby verbose if the log level is debug or verbose
+        const processLogLevel = Boolean(logLevel === 'debug' || logLevel === 'verbose')
+        if (index >= 0) {
+          // We found a mapping for this control
+          const newControl = updateControl(existingProfile.controls[index], control, logger)
+
+          logger.debug(`Writing updated control with code block for: ${control.id}.`)
+          fs.writeFileSync(path.join(outputProfileFolderPath, 'controls', `${control.id}.rb`), newControl.toRuby(processLogLevel))
+        } else {
+          // We didn't find a mapping for this control - Old style of updating controls
+          logger.debug(`Writing new control without code block for: ${control.id}.`)
+          fs.writeFileSync(path.join(outputProfileFolderPath, 'controls', `${control.id}.rb`), control.toRuby(processLogLevel))
+        }
       })
 
-      logger.info(`Writing delta file for ${existingProfile.title}`)
+      logger.info(`  Writing delta file for ${existingProfile.title}`)
       fs.writeFileSync(path.join(outputProfileFolderPath, 'delta.json'), JSON.stringify(updatedResult.diff, null, 2))
 
-      if (flags.report) {
-        logger.debug('Writing report markdown file')
-        fs.writeFileSync(path.join(markDownFile), updatedResult.markdown)
+      if (reportFile) {
+        logger.debug('  Writing report markdown file')
+        if (runMapControls) {
+          const totalMappedControls = Object.keys(mappedControls!).length // skipcq: JS-0339
+          const reportData = '## Map Controls\n' +
+            JSON.stringify(mappedControls!, null, 2) + // skipcq:  JS-0339
+            `\nTotal Mapped Controls: ${Object.keys(mappedControls!).length}\n\n` + // skipcq:  JS-0339
+            `Total Controls Available for Delta: ${GenerateDelta.oldControlsLength}\n` +
+            `     Total Controls Found on XCCDF: ${GenerateDelta.newControlsLength}\n` +
+            `                    Match Controls: ${GenerateDelta.match}\n` +
+            `        Possible Mismatch Controls: ${GenerateDelta.posMisMatch}\n` +
+            `          Duplicate Match Controls: ${GenerateDelta.dupMatch}\n` +
+            `                 No Match Controls: ${GenerateDelta.noMatch}\n` +
+            `                New XCDDF Controls: ${GenerateDelta.newXccdfControl}\n\n` +
+            'Statistics Validation ------------------------------------------\n' +
+            `Match + Mismatch = Total Mapped Controls: ${this.getMappedStatisticsValidation(totalMappedControls, 'totalMapped')}\n` +
+            `  Total Processed = Total XCCDF Controls: ${this.getMappedStatisticsValidation(totalMappedControls, 'totalProcessed')}\n\n` +
+            updatedResult.markdown
+          fs.writeFileSync(path.join(markDownFile), reportData)
+        } else {
+          fs.writeFileSync(path.join(markDownFile), updatedResult.markdown)
+        }
       }
+
+      // Print the process output report to current directory
+      addToProcessLogData('Update Results ===========================================================================\n')
+      addToProcessLogData(updatedResult.markdown)
+      saveProcessLogData()
     } else {
       if (!existingProfile) {
-        logger.error('ERROR: Could not generate delta because the existingProfile variable was not satisfied.')
+        logger.error('  ERROR: Could not generate delta because the existingProfile variable was not satisfied.')
       }
 
       if (!updatedXCCDF) {
-        logger.error('ERROR: Could not generate delta because the updatedXCCDF variable was not satisfied.')
+        logger.error('  ERROR: Could not generate delta because the updatedXCCDF variable was not satisfied.')
+      }
+    }
+  }
+
+  // Maps controls from an old profile to a new profile by updating the control IDs
+  // based on matching SRG IDs and titles.
+  //
+  // This method uses Fuse.js for fuzzy searching, a technique of finding
+  // strings that are approximately equal to a given pattern (rather than
+  // exactly) to find matching controls in the new profile based on the
+  // SRG ID (`tags.gtitle`). If a match is found and the titles match, the old
+  // control's ID is updated to the new control's ID.
+  //
+  // Example usage:
+  // ```typescript
+  // const oldProfile = processInSpecProfile(fs.readFileSync(inspecJsonFile, 'utf8'))
+  // const newProfile = processXCCDF(updatedXCCDF, false, flags.idType as 'cis' | 'version' | 'rule' | 'group', ovalDefinitions)
+  // const generateDelta = new GenerateDelta()
+  // generateDelta.mapControls(oldProfile, newProfile);
+  // ```
+  //
+  // @param oldProfile - The profile containing the old controls.
+  // @param newProfile - The profile containing the new controls.
+  async mapControls(oldProfile: Profile, newProfile: Profile): Promise<object> {
+    /*
+    If a control isn't found to have a match at all, then req is missing or has been dropped
+    Delta *should* be removing it automatically
+    */
+    const oldControls: Control[] = oldProfile.controls
+    const newControls: Control[] = newProfile.controls
+    GenerateDelta.oldControlsLength = oldControls.length
+    GenerateDelta.newControlsLength = newControls.length
+
+    const fuseOptions = {
+      // isCaseSensitive: false,
+      includeScore: true,
+      shouldSort: true,
+      includeMatches: true,
+      // findAllMatches: false,
+      // minMatchCharLength: 1,
+      // location: 0,
+      // A threshold of 0.0 requires a perfect match (of both letters and location),
+      //   threshold of 1.0 would match anything
+      threshold: 0.4,
+      // distance: 100,
+      // useExtendedSearch: false,
+
+      // text / character movements are inherent when text is changed
+      ignoreLocation: true,
+      // puts weight on length of field, skews results since often text is expanded in revisions
+      ignoreFieldNorm: true,
+      // fieldNormWeight: 1,
+      keys: ['title'],
+    }
+    const controlMappings: { [key: string]: string } = {}
+
+    printCyan('Mapping Process ===========================================================================')
+    // Create fuse object for searching through matchList
+    const fuse = await new Fuse(oldControls, fuseOptions)
+
+    // Map that holds processed controls and their scores
+    // Need to check if a control is process multiple-times and determine which
+    // control has the lower score
+    const controlIdToScoreMap = new Map()
+    for (const newControl of newControls) {
+      // Check for existence of title, remove non-displayed characters
+      // eslint-disable-next-line no-warning-comments
+      // TODO: Determine whether removing symbols other than non-displayed characters is helpful
+      // words separated by newlines don't have spaces between them
+      if (newControl.title) {
+        // Regex: [\w\s]     -> match word characters and whitespace
+        //        [\r\t\f\v] -> carriage return, tab, form feed and vertical tab
+        const result = fuse.search(newControl.title.replaceAll(/[^\w\s]|[\r\t\f\v]/g, '').replaceAll('\n', ''))
+        if (isEmpty(result)) {
+          printYellowGreen('     New XCCDF Control:', ` ${newControl.id}`)
+          printBgYellow('* No Mapping Provided *\n')
+          GenerateDelta.newXccdfControl++
+          continue
+        }
+
+        printYellowBgGreen('Processing New Control: ', `${newControl.id}`)
+        printYellowBgGreen('     New Control Title: ', `${this.updateTitle(newControl.title)}`)
+
+        if (result[0] && result[0].score && result[0].score < 0.3) { // skipcq: JS-W1044
+          if (controlIdToScoreMap.has(result[0].item.id)) {
+            const score = controlIdToScoreMap.get(result[0].item.id)
+
+            if (result[0].score < score) {
+              controlIdToScoreMap.set(result[0].item.id, result[0].score)
+            } else {
+              printBgMagentaRed('     Old Control Title:', ` ${this.updateTitle(result[0].item.title)}`)
+              printBgMagentaRed('       Duplicate Match:', ` ${result[0].item.id} --> ${newControl.id}`)
+              printBgMagentaRed('        Matching Score:', ` ${result[0].score}\n`)
+              GenerateDelta.dupMatch++
+              continue
+            }
+          }
+
+          if (typeof newControl.id === 'string' &&
+            typeof result[0].item.id === 'string') {
+            // Check non displayed characters of title
+            printYellowGreen('     Old Control Title: ', `${this.updateTitle(result[0].item.title)}`)
+            // NOTE: We determined that 0.1 needs to be reviewed due to possible
+            // words exchange that could alter the entire meaning of the title.
+
+            if (result[0].score > 0.1) {
+              // eslint-disable-next-line no-warning-comments
+              // TODO: modify output report or logger to show potential mismatches
+              // alternatively: add a match decision feature for high-scoring results
+              printBgRed('** Potential Mismatch **')
+              GenerateDelta.posMisMatch++
+            } else {
+              GenerateDelta.match++
+            }
+
+            printYellowGreen('  Best Match Candidate: ', `${result[0].item.id} --> ${newControl.id}`)
+            printYellowGreen('        Matching Score: ', `${result[0].score}\n`)
+
+            // Check if we have added an entry for the old control being processed
+            // The result[0].item.id is the old control id
+            for (const key in controlMappings) {
+              if (controlMappings[key] === result[0].item.id) {
+                delete controlMappings[key] // skipcq: JS-0320
+                // Lets now check if this entry was previously processed
+                if (controlIdToScoreMap.has(result[0].item.id)) {
+                  const score = controlIdToScoreMap.get(result[0].item.id)
+                  if (score > 0.1) {
+                    GenerateDelta.posMisMatch--
+                  } else {
+                    GenerateDelta.match--
+                  }
+
+                  GenerateDelta.noMatch++
+                }
+
+                break
+              }
+            }
+
+            controlMappings[newControl.id] = result[0].item.id
+            controlIdToScoreMap.set(result[0].item.id, result[0].score)
+          }
+        } else {
+          printBgRedRed('     Old Control Title:', ` ${this.updateTitle(result[0].item.title)}`)
+          printBgRedRed('    No Match Found for:', ` ${result[0].item.id} --> ${newControl.id}`)
+          printBgRedRed('        Matching Score:', ` ${result[0].score} \n`)
+          GenerateDelta.noMatch++
+        }
+      }
+    }
+
+    printCyan('Mapping Results ===========================================================================')
+    printYellow('\tOld Control -> New Control')
+    for (const [key, value] of Object.entries(controlMappings)) {
+      printGreen(`\t   ${value} -> ${key}`)
+    }
+
+    const totalMappedControls = Object.keys(controlMappings).length
+    printYellowGreen('Total Mapped Controls: ', `${totalMappedControls}\n`)
+
+    printCyan('Control Counts ===========================')
+    printYellowGreen('Total Controls Available for Delta: ', `${GenerateDelta.oldControlsLength}`)
+    printYellowGreen('     Total Controls Found on XCCDF: ', `${GenerateDelta.newControlsLength}\n`)
+
+    printCyan('Match Statistics =========================')
+    printYellowGreen('                    Match Controls: ', `${GenerateDelta.match}`)
+    printYellowGreen('        Possible Mismatch Controls: ', `${GenerateDelta.posMisMatch}`)
+    printYellowGreen('          Duplicate Match Controls: ', `${GenerateDelta.dupMatch}`)
+    printYellowGreen('                 No Match Controls: ', `${GenerateDelta.noMatch}`)
+    printYellowGreen('                New XCDDF Controls: ', `${GenerateDelta.newXccdfControl}\n`)
+
+    printCyan('Statistics Validation =============================================')
+    printYellowGreen('Match + Mismatch = Total Mapped Controls: ', `${this.getMappedStatisticsValidation(totalMappedControls, 'totalMapped')}`)
+    printYellowGreen('  Total Processed = Total XCCDF Controls: ', `${this.getMappedStatisticsValidation(totalMappedControls, 'totalProcessed')}\n\n`)
+
+    return controlMappings
+  }
+
+  getMappedStatisticsValidation(totalMappedControls: number, statValidation: string): string { // skipcq: JS-0105
+    let evalStats = ''
+    const match = GenerateDelta.match
+    const misMatch = GenerateDelta.posMisMatch
+    const statMach = ((match + misMatch) === totalMappedControls)
+    const dupMatch = GenerateDelta.dupMatch
+    const noMatch = GenerateDelta.noMatch
+    const newXccdfControl = GenerateDelta.newXccdfControl
+    const statTotalMatch = ((totalMappedControls + dupMatch + noMatch + newXccdfControl) === GenerateDelta.newControlsLength)
+
+    evalStats = statValidation === 'totalMapped' ?
+      `(${match}+${misMatch}=${totalMappedControls}) ${statMach}` :
+      `(${match}+${misMatch}+${dupMatch}+${noMatch}+${newXccdfControl}=${GenerateDelta.newControlsLength}) ${statTotalMatch}`
+
+    return evalStats
+  }
+
+  requiredFlagsProvided(flags: any): boolean { // skipcq: JS-0105
+    let missingFlags = false
+    let strMsg = 'Warning: The following errors occurred:\n'
+
+    if (!flags.inspecJsonFile) {
+      strMsg += colors.dim('  Missing required flag inspecJsonFile\n')
+      missingFlags = true
+    }
+
+    if (!flags.xccdfXmlFile) {
+      strMsg += colors.dim('  Missing required flag xccdfXmlFile\n')
+      missingFlags = true
+    }
+
+    if (!flags.deltaOutputDir) {
+      strMsg += colors.dim('  Missing required flag deltaOutputDir\n')
+      missingFlags = true
+    }
+
+    if (missingFlags) {
+      strMsg += 'See more help with -h or --help'
+      this.warn(strMsg)
+    }
+
+    return !missingFlags
+  }
+
+  updateTitle(str: string): string { // skipcq: JS-0105
+    return str
+      .replaceAll('\n', String.raw``)
+      .replaceAll('\r', String.raw``)
+      .replaceAll('\t', String.raw``)
+      .replaceAll('\f', String.raw``)
+      .replaceAll('\v', String.raw``)
+  }
+
+  createMappedDirectory(controlsDir: string): string { // skipcq: JS-0105
+    const destFilePath = path.basename(controlsDir)
+    const mappedDir = controlsDir.replace(destFilePath, 'mapped_controls')
+    if (fs.existsSync(mappedDir)) {
+      fs.rmSync(mappedDir, {recursive: true, force: true})
+    }
+
+    fs.mkdirSync(mappedDir)
+
+    return mappedDir
+  }
+}
+
+// Interactively ask the user for the arguments required for the cli.
+// All flags, required and optional are asked
+async function getFlags(): Promise<any> {
+  // The default max listeners is set to 10. The inquire checkbox sets a
+  // listener for each entry it displays, we are providing 16 entries,
+  // does using 16 listeners. Need to increase the defaultMaxListeners.
+  EventEmitter.defaultMaxListeners = 20
+
+  // Register the file selection prompt
+  inquirer.registerPrompt('file-tree-selection', inquirerFileTreeSelection)
+
+  // Variable used to store the prompts (question and answers)
+  const interactiveValues: {[key: string]: any} = {}
+
+  printYellow('Provide the necessary information:')
+  printGreen('  Required flag - Input execution/profile (list of controls the delta is being applied from) JSON file')
+  printGreen('  Required flag - The XCCDF XML file containing the new guidance - in the form of .xml file')
+  printGreen('  Required flag - The output folder for the updated profile (will contain the controls that delta was applied too)')
+  printMagenta('  Optional flag - The OVAL XML file containing definitions used in the new guidance - in the form of .xml file')
+  printMagenta('  Optional flag - Output markdown report file - must have an extension of .md')
+  printMagenta('  Optional flag - Control ID Types: [\'rule\', \'group\', \'cis\', \'version\']')
+  printMagenta('  Optional flag - Run the approximate string matching process')
+  printMagenta('  Optional flag - The InSpec profile directory containing the controls being updated (controls Delta is processing)\n')
+
+  // Required Flags
+  const requiredQuestions = [
+    {
+      type: 'file-tree-selection',
+      name: 'inspecJsonFile',
+      message: 'Select the Input execution/profile (list of controls the delta is being applied from) JSON file:',
+      filters: 'json',
+      pageSize: 15,
+      require: true,
+      enableGoUpperDirectory: true,
+      transformer: (input: any) => {
+        const name = input.split(path.sep).pop()
+        const fileExtension =  name.split('.').slice(1).pop()
+        if (name[0] === '.') {
+          return colors.grey(name)
+        }
+
+        if (fileExtension === 'json') {
+          return colors.green(name)
+        }
+
+        return name
+      },
+      validate: (input: any) => {
+        const name = input.split(path.sep).pop()
+        const fileExtension =  name.split('.').slice(1).pop()
+        if (fileExtension !== 'json') {
+          return 'Not a .json file, please select another file'
+        }
+
+        return true
+      },
+    },
+    {
+      type: 'file-tree-selection',
+      name: 'xccdfXmlFile',
+      message: 'Select the XCCDF XML file containing the new guidance - in the form of .xml file:',
+      filters: 'xml',
+      pageSize: 15,
+      require: true,
+      enableGoUpperDirectory: true,
+      transformer: (input: any) => {
+        const name = input.split(path.sep).pop()
+        const fileExtension =  name.split('.').slice(1).pop()
+        if (name[0] === '.') {
+          return colors.grey(name)
+        }
+
+        if (fileExtension === 'xml') {
+          return colors.green(name)
+        }
+
+        return name
+      },
+      validate: (input: any) => {
+        const name = input.split(path.sep).pop()
+        const fileExtension =  name.split('.').slice(1).pop()
+        if (fileExtension !== 'xml') {
+          return 'Not a .xml file, please select another file'
+        }
+
+        return true
+      },
+    },
+    {
+      type: 'file-tree-selection',
+      name: 'deltaOutputDir',
+      message: 'Select the output folder for the updated profile (do not use the original controls directory):',
+      pageSize: 15,
+      require: true,
+      onlyShowDir: true,
+      enableGoUpperDirectory: true,
+      transformer: (input: any) => {
+        const name = input.split(path.sep).pop()
+        if (name[0] === '.') {
+          return colors.grey(name)
+        }
+
+        return name
+      },
+    },
+  ]
+  const askRequired = inquirer.prompt(requiredQuestions).then((answers: any) => {
+    addToProcessLogData('Process Flags ============================================')
+    for (const question in answers) {
+      if (answers[question] !== null) {
+        addToProcessLogData(question + '=' + answers[question])
+        interactiveValues[question] = answers[question]
+      }
+    }
+  })
+  await askRequired
+
+  // Optional - OVAL file Flag
+  const addOvalFilePrompt = {
+    type: 'list',
+    name: 'useOvalFile',
+    message: 'Include an OVAL XML file:',
+    choices: ['true', 'false'],
+    default: false,
+    filter(val: string) {
+      return (val === 'true')
+    },
+  }
+  const ovalFilePrompt = {
+    type: 'file-tree-selection',
+    name: 'ovalXmlFile',
+    message: 'Select the OVAL XML file containing definitions used in the new guidance - in the form of .xml file:',
+    filters: 'xml',
+    pageSize: 15,
+    require: true,
+    enableGoUpperDirectory: true,
+    transformer: (input: any) => {
+      const name = input.split(path.sep).pop()
+      const fileExtension =  name.split('.').slice(1).pop()
+      if (name[0] === '.') {
+        return colors.grey(name)
+      }
+
+      if (fileExtension === 'xml') {
+        return colors.green(name)
       }
+
+      return name
+    },
+    validate: (input: any) => {
+      const name = input.split(path.sep).pop()
+      const fileExtension =  name.split('.').slice(1).pop()
+      if (fileExtension !== 'xml') {
+        return 'Not a .xml file, please select another file'
+      }
+
+      return true
+    },
+  }
+  let askOvalFile: any
+  const askOvalOptional = inquirer.prompt(addOvalFilePrompt).then((addOvalAnswer: any) => {
+    if (addOvalAnswer.useOvalFile === true) {
+      addToProcessLogData('useOvalFile=true')
+      interactiveValues.useOvalFile = true
+      askOvalFile = inquirer.prompt(ovalFilePrompt).then((answer: any) => {
+        for (const question in answer) {
+          if (answer[question] !== null) {
+            addToProcessLogData(question + '=' + answer[question])
+            interactiveValues[question] = answer[question]
+          }
+        }
+      })
+    } else {
+      addToProcessLogData('useOvalFile=false')
+      interactiveValues.useOvalFile = false
     }
+  }).finally(async () => {
+    await askOvalFile
+  })
+  await askOvalOptional
+
+  // Optional - Map controls using fuzzy logic
+  const useFuzzyLogicPrompt = {
+    type: 'list',
+    name: 'runMapControls',
+    message: 'Run the approximate string matching process (fuzzy logic):',
+    choices: ['true', 'false'],
+    default: true,
+    filter(val: string) {
+      return (val === 'true')
+    },
   }
+  const fuzzyLogicPrompt =     {
+    type: 'file-tree-selection',
+    name: 'controlsDir',
+    message: 'Select the InSpec profile directory containing the controls being updated (controls Delta is processing):',
+    pageSize: 15,
+    require: true,
+    onlyShowDir: true,
+    enableGoUpperDirectory: true,
+    transformer: (input: any) => {
+      const name = input.split(path.sep).pop()
+      if (name[0] === '.') {
+        return colors.grey(name)
+      }
+
+      return name
+    },
+  }
+  const askFuzzyLogicOptional = inquirer.prompt(useFuzzyLogicPrompt).then(async (fuzzyLogicAnswer: any) => {
+    if (fuzzyLogicAnswer.runMapControls === true) {
+      addToProcessLogData('runMapControls=true')
+      interactiveValues.runMapControls = true
+      const askFuzzyLogicDir = inquirer.prompt(fuzzyLogicPrompt).then((answer: any) => {
+        for (const question in answer) {
+          if (answer[question] !== null) {
+            addToProcessLogData(question + '=' + answer[question])
+            interactiveValues[question] = answer[question]
+          }
+        }
+      })
+      await askFuzzyLogicDir
+    } else {
+      addToProcessLogData('runMapControls=false')
+      interactiveValues.runMapControls = false
+    }
+  })
+  await askFuzzyLogicOptional
+
+  // Optional - Generate markdown report from Inspect-objects process
+  const generateReportPrompt = {
+    type: 'list',
+    name: 'generateReport',
+    message: 'Generate the Inspect-Object process markdown report file:',
+    choices: ['true', 'false'],
+    default: false,
+    filter(val: string) {
+      return (val === 'true')
+    },
+  }
+  const reportFilePrompt = [
+    {
+      type: 'file-tree-selection',
+      name: 'reportDirectory',
+      message: 'Select the output directory for the markdown report file:',
+      pageSize: 15,
+      require: true,
+      onlyShowDir: true,
+      enableGoUpperDirectory: true,
+      transformer: (input: any) => {
+        const name = input.split(path.sep).pop()
+        if (name[0] === '.') {
+          return colors.grey(name)
+        }
+
+        return name
+      },
+    },
+    {
+      type: 'input',
+      name: 'reportFileName',
+      message: 'Specify the output report filename (must have an extension of .md):',
+      require: true,
+      default() {
+        return 'deltaProcessReport.md'
+      },
+    },
+  ]
+
+  let askReportFile: any
+  const askReportOptional = inquirer.prompt(generateReportPrompt).then((genReportAnswer: any) => {
+    if (genReportAnswer.generateReport === true) {
+      addToProcessLogData('generateReport=true')
+      interactiveValues.generateReport = true
+      askReportFile = inquirer.prompt(reportFilePrompt).then((answer: any) => {
+        for (const question in answer) {
+          if (answer[question] !== null) {
+            addToProcessLogData(question + '=' + answer[question])
+            interactiveValues[question] = answer[question]
+          }
+        }
+      })
+    } else {
+      addToProcessLogData('generateReport=false')
+      interactiveValues.generateReport = false
+    }
+  }).finally(async () => {
+    await askReportFile
+  })
+  await askReportOptional
+
+  // Optional - Select what group Id to process the controls and Log Level
+  const otherOptionalPrompts = [
+    {
+      type: 'rawlist',
+      name: 'idType',
+      message: 'Select the Control ID Type used to process the controls:',
+      choices: ['rule', 'group', 'cis', 'version'],
+      default() {
+        return 'rule'
+      },
+      filter(val: string) {
+        return val.toLowerCase()
+      },
+    },
+    {
+      type: 'rawlist',
+      name: 'logLevel',
+      message: 'Select the log level:',
+      choices: ['info', 'warn', 'debug', 'verbose'],
+      default() {
+        return 'info'
+      },
+      filter(val: string) {
+        return val.toLowerCase()
+      },
+    },
+  ]
+  const askOptional = inquirer.prompt(otherOptionalPrompts).then((answers: any) => {
+    for (const question in answers) {
+      if (answers[question] !== null) {
+        addToProcessLogData(question + '=' + answers[question])
+        interactiveValues[question] = answers[question]
+      }
+    }
+  })
+  await askOptional
+  return interactiveValues
 }
diff --git a/src/commands/generate/inspec_profile.ts b/src/commands/generate/inspec_profile.ts
index 9e42f3854..678c5c232 100644
--- a/src/commands/generate/inspec_profile.ts
+++ b/src/commands/generate/inspec_profile.ts
@@ -203,7 +203,7 @@ export default class InspecProfile extends BaseCommand<typeof InspecProfile> {
     // Generate files
     generateYaml(profile, outDir, logger)
     generateReadme(readmeObj, outDir, logger)
-    generateLicenses(outDir, logger)
+    generateLicense(outDir, logger)
     generateNotice(outDir, logger)
     generateRubocopYml(outDir, logger)
     generateGemFile(outDir, logger)
@@ -542,7 +542,7 @@ function generateYaml(profile: Profile, outDir: string, logger: Logger) {
   })
 }
 
-function generateLicenses(outDir: string, logger: Logger) {
+function generateLicense(outDir: string, logger: Logger) {
   const licensesContent =
 `Licensed under the apache-2.0 license, except as noted below.  
     
@@ -558,11 +558,11 @@ are permitted provided that the following conditions are met:
   used to endorse or promote products derived from this software without specific prior
   written permission.
 `
-  fs.writeFile(path.join(outDir, 'LICENSES.md'), licensesContent, err => {
+  fs.writeFile(path.join(outDir, 'LICENSE.md'), licensesContent, err => {
     if (err) {
-      logger.error(`Error saving the LICENSES.md file to: ${outDir}. Cause: ${err}`)
+      logger.error(`Error saving the LICENSE file to: ${outDir}. Cause: ${err}`)
     } else {
-      logger.debug('LICENSES.md generated successfully!')
+      logger.debug('LICENSE generated successfully!')
     }
   })
 }
diff --git a/src/commands/generate/update_controls4delta.ts b/src/commands/generate/update_controls4delta.ts
index 23ec5e6dd..116005ffd 100644
--- a/src/commands/generate/update_controls4delta.ts
+++ b/src/commands/generate/update_controls4delta.ts
@@ -5,15 +5,53 @@ import {execSync} from 'child_process'
 import {Flags} from '@oclif/core'
 import {createWinstonLogger} from '../../utils/logging'
 import Profile from '@mitre/inspec-objects/lib/objects/profile'
-import {processInSpecProfile, processXCCDF} from '@mitre/inspec-objects'
+import {
+  processInSpecProfile,
+  processXCCDF,
+  updateControl,
+} from '@mitre/inspec-objects'
 import colors from 'colors' // eslint-disable-line no-restricted-imports
 import {BaseCommand} from '../../utils/oclif/baseCommand'
+import {
+  printGreen,
+  printRed,
+  printBoldRedGreen,
+  printYellowGreen,
+  addToProcessLogData,
+  saveProcessLogData,
+} from '../../utils/oclif/cliHelper'
+
+/**
+ * This class is used to prepare profile controls from one SRG or STIG baseline
+ * to another. The controls are updated based on guidances provided by the
+ * Extensible Configuration Checklist Description Format (XCCDF) document.
+ *
+ * The XCCDF document is an XML formatted file that containing the updated
+ * structured collection of security configuration rules for a specific target
+ * system.
+ *
+ * How are profile controls updated from baseline X to baseline Y
+ * 1 - The directory where baseline X controls are located is provided
+ * 2 - An InSpec json formatted file containing all baseline X controls is
+ *     provided or generated
+ *     a - The json file is generated using the inspec json CLI command
+ * 3 - A XCCDF file containing the new baseline guidances is provided. The file
+ *     is obtained from the DISA site
+ *
+ * Process:
+ * 1 - Housekeeping is done to ensure required data is provided
+ * 2 - The InSpec json object is processed - it is converted into a
+ *     Profile object (baseline X)
+ * 3 - The XCCDF XML data is converted into a json Profile (includes controls)
+ *     (baseline Y)
+ * 4 - The baseline Y metadata is combined with baseline X code
+ * 5 - New controls are written to provided output directory
+ */
 
 export default class GenerateUpdateControls extends BaseCommand<typeof GenerateUpdateControls> {
   static readonly usage = '<%= command.id %> [ARGUMENTS]'
 
-  static readonly description = 'Update the control names and/or format for an existing InSpec\n' +
-  'profile with updated XCCDF guidance, old controls are saved by default'
+  static readonly description = 'Update Profile Control(s) from baseline X to Y based on DISA XCCDF guidance'
 
   static readonly examples = [
     '<%= config.bin %> <%= command.id %> -X ./the_xccdf_guidance_file.xml -c the_controls_directory -L debug',
@@ -24,42 +62,75 @@ export default class GenerateUpdateControls extends BaseCommand<typeof GenerateU
   ]
 
   static readonly flags = {
-    xccdfXmlFile: Flags.string({char: 'X', required: true, description: 'The XCCDF XML file containing the new guidance - in the form of .xml file'}),
-    inspecJsonFile: Flags.string({char: 'J', required: false, description: 'Input execution/profile JSON file - can be generated using the "inspec json <profile path> > profile.json" command'}),
-    controlsDir: Flags.string({char: 'c', required: true, description: 'The InSpec profile controls directory containing the profiles to be updated'}),
-    controlPrefix: Flags.string({char: 'P', required: false, default: 'V', options: ['V', 'SV'], description: 'Old control number prefix V or SV, default V'}),
-    useXccdfGroupId: Flags.boolean({char: 'g', required: false, default: false, allowNo: true, description: 'Use the XCCDF `Group Id` to rename the controls. Uses prefix V or SV based on controlPrefix option\n[default: false]'}),
-    formatControls: Flags.boolean({char: 'f', required: false, default: true, allowNo: true, description: 'Format control contents in the same way `generate delta` will write controls\n[default: true]'}),
-    backupControls: Flags.boolean({char: 'b', required: false, default: true, allowNo: true, description: 'Preserve modified controls in a backup directory (oldControls) inside the controls directory\n[default: true]'}),
-    logLevel: Flags.string({char: 'L', required: false, default: 'info', options: ['info', 'warn', 'debug', 'verbose']}),
+    xccdfXmlFile: Flags.string({
+      char: 'X', required: true,
+      description: 'The XCCDF XML file containing the new guidance - in the form of .xml file',
+    }),
+    inspecJsonFile: Flags.string({
+      char: 'J', required: false,
+      description: 'Input execution/profile JSON file - can be generated using the "inspec json <profile path> > profile.json" command',
+    }),
+    controlsDir: Flags.string({
+      char: 'c', required: true,
+      description: 'The InSpec profile controls directory containing the profiles to be updated',
+    }),
+    controlPrefix: Flags.string({
+      char: 'P', required: false, default: 'V', options: ['V', 'SV'],
+      description: 'Old control number prefix V or SV, default V',
+    }),
+    useXccdfGroupId: Flags.boolean({
+      char: 'g', required: false, default: false, allowNo: true,
+      description: 'Use the XCCDF `Group Id` to rename the controls. Uses prefix V or SV based on controlPrefix option\n[default: false]',
+    }),
+    formatControls: Flags.boolean({
+      char: 'f', required: false, default: true, allowNo: true,
+      description: 'Format control contents in the same way `generate delta` will write controls\n[default: true]',
+    }),
+    backupControls: Flags.boolean({
+      char: 'b', required: false, default: true, allowNo: true,
+      description: 'Preserve modified controls in a backup directory (oldControls) inside the controls directory\n[default: true]',
+    }),
   }
 
+  // Class common variables
+  static backupDir = ''
+
   // skipcq: JS-R1005
   async run(): Promise<any> { // skipcq: JS-0044
     const {flags} = await this.parse(GenerateUpdateControls)
     const logger = createWinstonLogger('generate:update_controls', flags.logLevel)
 
-    this.warn(colors.yellow('╔═══════════════════════════════════════════════════════════════════════════════════════════════════════════╗'))
-    this.warn(colors.yellow('║ Make sure that profile controls are in cookstyle format - see https://docs.chef.io/workstation/cookstyle/ ║'))
-    this.warn(colors.yellow('╚═══════════════════════════════════════════════════════════════════════════════════════════════════════════╝'))
+    logger.warn(colors.yellow('╔═══════════════════════════════════════════════════════════════════════════════════════════════╗'))
+    logger.warn(colors.yellow('║ Ensure profile controls are in cookstyle format (https://docs.chef.io/workstation/cookstyle/) ║'))
+    logger.warn(colors.yellow('╚═══════════════════════════════════════════════════════════════════════════════════════════════╝'))
 
-    let inspecProfile: Profile
+    let inspecProfile: Profile = new Profile()
+    GenerateUpdateControls.backupDir = path.join(path.dirname(flags.controlsDir), 'oldControls')
 
-    // Process the XCCDF XML file containing the new/updated profile guidance
+    addToProcessLogData('==================== Update Controls for Delta Process =====================')
+    addToProcessLogData(`Date: ${new Date().toISOString()}`)
+    addToProcessLogData('\nProcess Flags ===========================================')
+    for (const key in flags) {
+      if (Object.prototype.hasOwnProperty.call(flags, key)) {
+        addToProcessLogData(key + '=' + flags[key as keyof typeof flags])
+      }
+    }
+
+    //-------------------------------------------------------------------------
+    // Check if we have a XCCDF XML file containing the new/updated profile guidance
+    logger.info(`Verifying that the XCCDF file is valid: ${path.basename(flags.xccdfXmlFile)}...`)
     try {
       if (fs.lstatSync(flags.xccdfXmlFile).isFile()) {
         const xccdfXmlFile = flags.xccdfXmlFile
-        logger.debug(`Processing the ${xccdfXmlFile} XCCDF file`)
+        // logger.debug(`Processing the ${xccdfXmlFile} XCCDF file`)
         const inputFile = fs.readFileSync(xccdfXmlFile, 'utf8')
         const inputFirstLine = inputFile.split('\n').slice(0, 10).join('').toLowerCase()
         if (inputFirstLine.includes('xccdf')) {
-          logger.debug(`The ${xccdfXmlFile} is a valid XCCDF file`)
+          logger.debug('  Valid XCCDF file provided')
         } else {
           logger.error(`ERROR: Unable to load ${xccdfXmlFile} as XCCDF`)
           throw new Error('Cannot load XCCDF file')
         }
-
-        logger.debug(`Loaded ${xccdfXmlFile} as XCCDF`)
       } else {
         throw new Error('No benchmark (XCCDF) file was provided.')
       }
@@ -73,25 +144,27 @@ export default class GenerateUpdateControls extends BaseCommand<typeof GenerateU
       }
     }
 
+    //-------------------------------------------------------------------------
     // Check if we have a controls folder
+    logger.info('Verifying that a controls folder exists...')
     if (fs.existsSync(flags.controlsDir)) {
-      logger.debug('Found controls directory')
+      logger.debug('  Found controls directory')
       fs.readdir(flags.controlsDir, function (err, files) { // skipcq: JS-0241
         if (err) {
-          logger.error(`ERROR: Checking in controls directory is empty, received: ${err.message}`)
+          logger.error(`ERROR: Checking if controls directory is empty, received: ${err.message}`)
           throw new Error(`Error checking controls directory, error: ${err.message}`)
         } else if (files.length) {
-          logger.debug(`Found ${files.length} Controls in the controls directory`)
+          logger.debug(`  Found ${files.length} Controls in the controls directory`)
           if (flags.backupControls) {
-            const oldControlsDir = path.join(flags.controlsDir, 'oldControls')
-            if (fs.existsSync(oldControlsDir)) {
-              fs.rmSync(oldControlsDir, {recursive: true, force: true})
+            // Create the backup directory inside the parent controls directory
+            if (fs.existsSync(GenerateUpdateControls.backupDir)) {
+              fs.rmSync(GenerateUpdateControls.backupDir, {recursive: true, force: true})
             }
 
-            fs.mkdirSync(oldControlsDir)
+            fs.mkdirSync(GenerateUpdateControls.backupDir)
           }
         } else {
-          // directory appears to be empty
+          // The controls directory appears to be empty
           logger.error(`No controls were found in the provide directory: ${flags.controlsDir}`)
           throw new Error(`No controls were found in the provide directory: ${flags.controlsDir}`)
         }
@@ -100,96 +173,154 @@ export default class GenerateUpdateControls extends BaseCommand<typeof GenerateU
       throw new Error('Controls folder not specified or does not exist')
     }
 
-    // Generate or Process the Input execution/profile JSON file
-    if (flags.formatControls) {
-      // Process provided Profile JSON file
-      if (flags.inspecJsonFile) {
-        try {
-          if (fs.lstatSync(flags.inspecJsonFile).isFile()) {
-            const inspecJsonFile = flags.inspecJsonFile
-            logger.debug(`Loading ${inspecJsonFile} as Profile JSON/Execution JSON`)
-            inspecProfile = processInSpecProfile(fs.readFileSync(inspecJsonFile, 'utf8'))
-            logger.debug(`Loaded ${inspecJsonFile} as Profile JSON/Execution JSON`)
-          } else {
-            throw new Error(`No entity found for: ${flags.inspecJsonFile}. Run the --help command to more information on expected input files.`)
-          }
-        } catch (error: any) {
-          if (error.code === 'ENOENT') {
-            logger.error(`ERROR: No entity found for: ${flags.inspecJsonFile}. Run the --help command to more information on expected input files.`)
-            throw error
-          } else {
-            logger.error(`ERROR: Unable to process Input execution/profile JSON ${flags.inspecJsonFile} because: ${error}`)
-            throw error
-          }
+    //-------------------------------------------------------------------------
+    // Check if we have an InSpec json file, generate if not provided
+    // Process the InSpec json content, convert entries into a Profile object
+    logger.info(`Processing the Input execution/profile JSON file: ${path.basename(flags.inspecJsonFile!)}...`) // skipcq: JS-0339
+    if (flags.inspecJsonFile) {
+      try {
+        if (fs.lstatSync(flags.inspecJsonFile).isFile()) {
+          const inspecJsonFile = flags.inspecJsonFile
+          inspecProfile = processInSpecProfile(fs.readFileSync(inspecJsonFile, 'utf8'))
+          logger.debug('  Converted JSON file into a Profile JSON/Execution object')
+        } else {
+          throw new Error(`Input execution/profile JSON file not found: ${path.basename(flags.inspecJsonFile)}.\n` +
+            'Run the --help command to more information on expected input files.')
         }
-      } else {
-        // Generate the profile json
-        try {
-          logger.info(`Generating the profile json using inspec json command on '${flags.controlsDir}'`)
-          // Get the directory name without the trailing "controls" directory
-          const profileDir = path.dirname(flags.controlsDir)
-          const inspecJsonFile = execSync(`inspec json '${profileDir}'`, {encoding: 'utf8', maxBuffer: 50 * 1024 * 1024})
-
-          logger.info('Generating InSpec Profiles from InSpec JSON summary')
-          inspecProfile = processInSpecProfile(inspecJsonFile)
-        } catch (error: any) {
-          logger.error(`ERROR: Unable to generate the profile json because: ${error}`)
+      } catch (error: any) {
+        if (error.code === 'ENOENT') {
+          logger.error(`ERROR: No entity found for: ${flags.inspecJsonFile}. Run the --help command to more information on expected input files.`)
+          throw error
+        } else {
+          logger.error(`ERROR: Unable to process Input execution/profile JSON ${flags.inspecJsonFile} because: ${error}`)
           throw error
         }
       }
+    } else {
+      // Generate the profile json
+      try {
+        logger.info(`Generating the profile json using inspec json command on '${flags.controlsDir}'`)
+        // Get the directory name without the trailing "controls" directory
+        const profileDir = path.dirname(flags.controlsDir)
+        const inspecJsonFile = execSync(`inspec json '${profileDir}'`, {encoding: 'utf8', maxBuffer: 50 * 1024 * 1024})
+
+        logger.info('Generating InSpec Profiles from InSpec JSON summary')
+        inspecProfile = processInSpecProfile(inspecJsonFile)
+      } catch (error: any) {
+        logger.error(`ERROR: Unable to generate the profile json because: ${error}`)
+        throw error
+      }
     }
 
-    // Process the XCCDF file and convert entries into a Profile object
+    //-------------------------------------------------------------------------
+    // Process the XCCDF file (convert entries into a Profile object)
     // The XCCDF contains the profiles metadata - it does not have the code descriptions
-    logger.debug(`Processing XCCDF Benchmark file: ${flags.xccdfXmlFile} using rule id (SAF inspect objects - processXCCDF).`)
+    logger.info(`Processing XCCDF Benchmark file: ${path.basename(flags.xccdfXmlFile)}...`)
     const xccdf = fs.readFileSync(flags.xccdfXmlFile, 'utf8')
-    /* eslint-disable prefer-const, max-depth */
-    let xccdfProfile: Profile
-    xccdfProfile = processXCCDF(xccdf, false, 'rule') // skipcq: JS-0242
-
-    // Create a map data type (xccdfLegacyToControlMap) with: key = legacy Id (V or SV number) and value = new Id (SV number)
-    // Create a map data type (xccdfLegacyControlsMap) to be used as a flag to identify new controls (key and value are the new control Id)
-    // Create a map data type (xccdfControlsMap) to be used as a flag to identify legacy controls (key and value are the legacy control Id)
-    // The xccdfLegacyControlsMap and xccdfControlsMap are used so we can invoke the .has(key) method (test if map contains provided key),
-    //   there is, did we processed the legacy tag and the new tag
-    logger.info('Mapping legacy control Ids')
+    const idType = (flags.useXccdfGroupId) ? 'group' : 'rule'
+    const xccdfProfile = processXCCDF(xccdf, false, idType)
+    logger.debug(`  Converted XCCDF Benchmark file into a Profile JSON/Execution object using ${idType} Id`)
+
+    //-------------------------------------------------------------------------
+    // Create variable map data types containing various Controls Id mappings.
+    // The xccdfProfile object has the following identifications (id's):
+    //   "id": "SV-205624" -> the new control Id (generated from the Rule or Group Id)
+    //   "tags"."gid": "V-205624" -> the group control Id
+    //   "tags"."legacy": ["SV-103063", "V-92975"] -> legacy control Id's
+    //
+    // Mapping is determined based on the "useXccdfGroupId" flag, if set mapping
+    // (old control Id to new Id) is accomplished using the tags.gid value,
+    // otherwise it is accomplished using the tags.legacy values.
+    // NOTE: If using tags.legacy and there isn't any legacy tags, the XCCDF
+    //       control Id is used which is defaulted to the Rule Id
+    //
+    //  xccdfLegacyToControlMap -> maps control legacy Ids to new Ids
+    //    (key = legacy Id (V or SV number) and value = new Id (SV number))
+    //
+    //  xccdfLegacyControlsMap ->  maps old control Ids, used to identify old controls
+    //    (key and value are the old control Id)
+    //
+    //  xccdfControlsMap -> maps new control Ids, used to identify new controls
+    //    (key and value are the new control Id)
+    //
+    //  xccdfNewControlsMetaDataMap -> Contains baseline Y metadata indexed by old control Id
+    //    (key = legacy Id (V or SV number) and value = new control metadata)
+    //
+    // The xccdfLegacyControlsMap and xccdfControlsMap are used so we can invoke the .has(key)
+    // method (test if map contains provided key), did we processed the legacy and the new tag
+    logger.info('Mapping legacy control Ids...')
     const xccdfLegacyToControlMap = new Map()
     const xccdfLegacyControlsMap = new Map()
     const xccdfControlsMap = new Map()
-    if (flags.useXccdfGroupId) {
-      logger.debug('Using Group Id for mapping')
-      xccdfProfile.controls.forEach(control => {
-        const controlId = flags.controlPrefix === 'V' ? control.tags.gid?.match(/^V-\d+/)?.toString() : control.tags.gid?.match(/^SV-\d+/)?.toString()
-        xccdfLegacyToControlMap.set(controlId, control.id)
-        xccdfLegacyControlsMap.set(controlId, controlId)
-        xccdfControlsMap.set(control.id, control.id)
-      })
-    } else {
-      logger.debug('Using tags to determine legacy Ids')
-      xccdfProfile.controls.forEach(control => {
-        const controlId = control.tags.legacy?.map(value => {
-          const control = flags.controlPrefix === 'V' ? value.match(/^V-\d+/)?.toString() : value.match(/^SV-\d+/)?.toString()
+    const xccdfNewControlsMetaDataMap = new Map()
+    for (const control of xccdfProfile.controls) {
+      let controlId
+      if (flags.useXccdfGroupId) {
+        logger.debug('  Using `tags.gid` to determine new Control Name/Id')
+        controlId = (flags.controlPrefix === 'V') ?
+          control.tags.gid?.match(/^V-\d+/)?.toString() :
+          control.tags.gid?.match(/^SV-\d+/)?.toString()
+      } else {
+        logger.debug('  Using `tags.legacy` to determine new Control Name/Id')
+        controlId = control.tags.legacy?.map(value => {
+          const control = (flags.controlPrefix === 'V') ?
+            value.match(/^V-\d+/)?.toString() :
+            value.match(/^SV-\d+/)?.toString()
           return (control === undefined) ? '' : control
         }).find(Boolean)
-        xccdfLegacyToControlMap.set(controlId, control.id)
-        xccdfLegacyControlsMap.set(controlId, controlId)
-        xccdfControlsMap.set(control.id, control.id)
-      })
+        // If there isn't a legacy tag, use the XCCDF Id (see note above)
+        if (controlId === '') controlId = control.id
+      }
+
+      logger.debug(`    Old Control Name/Id: ${controlId} -> New Control Name/Id: ${control.id}`)
+      xccdfLegacyToControlMap.set(controlId, control.id)
+      xccdfLegacyControlsMap.set(controlId, controlId)
+      xccdfControlsMap.set(control.id, control.id)
+      xccdfNewControlsMetaDataMap.set(controlId, control)
     }
 
-    // Create a map data type containing the controls found in the processed InSpec JSON file
-    //   The InSpec JSON file contains the controls and associated code block (these are
-    //   created from the existing controls - They are updated via the Delta process)
-    // Lint the controls using the toRuby method provided by the Controls class
-    const inspecProfileFormattedControls = new Map()
-    if (flags.formatControls) {
-      logger.debug('Formatting control contents in the same way `generate delta` will write controls.')
-      inspecProfile!.controls.forEach(control => { // skipcq: JS-0339
-        inspecProfileFormattedControls.set(control.id, control.toRuby(false))
-      })
+    //-------------------------------------------------------------------------
+    // Generate a map data type containing the XCCDF metadata (all content minus the code)
+    // and add the code from the old control (in InSpec json object)
+    //
+    //  The xccdfNewControlsMetaDataMap contains the metadata generated from
+    //  the XCCDF file (baseline Y)
+    //  The InSpec JSON file contains the controls and associated code block generated
+    //  from the existing controls (baseline X)
+    //
+    // Lint the controls using the toRuby method provided by the Controls
+    // class if format controls flag is set
+    logger.info('Formatting control contents...')
+    const baselineYControls = new Map()
+    for (const control of inspecProfile.controls) {
+      if (control.tags.nist) {
+        // Remove any previously added Rev versions to the nist tags
+        const index = control.tags.nist.findIndex(value => /Rev_[0-9]/g.test(value))
+        if (index !== -1) {
+          const badNistTag = control.tags.nist.splice(index, 1)
+          logger.debug(`  Removed invalid tags.nist Rev version: ${badNistTag}`)
+        }
+      }
+
+      const oldControlId = control.id
+      const newControl = updateControl(control, xccdfNewControlsMetaDataMap.get(control.id), logger)
+      if (flags.formatControls) {
+        logger.debug('  Formatted the same way `generate delta` will write controls.')
+        baselineYControls.set(oldControlId, newControl.toRuby(false))
+      } else {
+        logger.debug('  Did not formatted the same way `generate delta` will write controls.')
+        baselineYControls.set(oldControlId, newControl.toString())
+      }
     }
 
-    logger.debug(`Processing controls directory: ${flags.controlsDir} and updating controls file name and new control number (id).`)
+    //-------------------------------------------------------------------------
+    // Update all baseline X controls with content from baseline Y
+    // Updated controls have:
+    //   Metadata from XCCDF guidances
+    //   Code block from matching old control (inspec json)
+    const shortControlsDir = path.sep + path.basename(path.dirname(flags.controlsDir)) + path.sep + path.basename(flags.controlsDir)
+    logger.info(`Updating controls in directory: ..${shortControlsDir}`)
+
     const ext = '.rb'
     let skipped = 0
     let processed = 0
@@ -200,57 +331,49 @@ export default class GenerateUpdateControls extends BaseCommand<typeof GenerateU
 
     // Iterate trough all files processing ony control files, have a .rb extension
     const skippedControls: string[] = []
-    const skippedFormatting: string[] = []
+    const skipMetadataUpdate: string[] = []
     const isCorrectControlMap  = new Map()
     const controlsProcessedMap = new Map()
 
     for (const file of files) {
       const fileExt = path.extname(file)
       if (fileExt === ext) {
-        logger.debug(`Processing file: ${file}`)
+        logger.info(`Processing Control (file): ${file}`)
         const currentFileFullPath = path.join(controlsDir, file)
         const currentControlNumber = path.parse(file).name
-        const newXCCDFControlNumber = xccdfLegacyToControlMap.get(currentControlNumber)
-        const xccdfControlNumber = xccdfControlsMap.get(currentControlNumber)
-        const xccdfLegacyControlNumber = xccdfLegacyControlsMap.get(currentControlNumber)
+        const newXCCDFControlNumber = xccdfLegacyToControlMap.get(currentControlNumber)   // old control Id to new control Id
+        const xccdfNewControlNumber = xccdfControlsMap.get(currentControlNumber)          // new control Id to new control Id
+        const xccdfLegacyControlNumber = xccdfLegacyControlsMap.get(currentControlNumber) // old control Id to old control Id
         let updatedControl
-        // FILE = XCCDF
-        if (currentControlNumber === xccdfControlNumber) {
-          logger.debug(`  The profile control number is current: ${currentControlNumber} `)
 
+        // FILE = XCCDF (new control Id)
+        if (currentControlNumber === xccdfNewControlNumber) {
+          logger.debug(`  Baseline X Control is current: ${currentControlNumber} `)
+
+          // Update statistics (value does not matter)
           isCorrectControl++
-          isCorrectControlMap.set(currentControlNumber, currentControlNumber) // Map used to compute output statistics (value does not matter)
-          if (flags.formatControls) {
-            // Check if the formatted control is indexed by current control - if it isn't, this control was already processed
-            /* eslint-disable-next-line unicorn/prefer-ternary */
-            if (inspecProfileFormattedControls.get(currentControlNumber)) {
-              updatedControl = inspecProfileFormattedControls.get(currentControlNumber)
-            } else {
-              updatedControl = getUpdatedControl(currentFileFullPath, currentControlNumber, 'undefined')
-            }
-          } else {
-            // Just get the control data
-            updatedControl = getUpdatedControl(currentFileFullPath, currentControlNumber, 'undefined')
+          isCorrectControlMap.set(currentControlNumber, currentControlNumber)
+
+          // Process the control
+          if (baselineYControls.has(currentControlNumber)) {
+            logger.debug('  \x1B[32mUpdating Control metadata with XCCDF content\x1B[0m')
+            updatedControl = baselineYControls.get(currentControlNumber)
+            // Save file
+            saveControl(currentFileFullPath, currentControlNumber, currentControlNumber, updatedControl, flags.backupControls, false)
           }
 
-          // Save file
-          saveControl(currentFileFullPath, currentControlNumber, currentControlNumber, updatedControl, flags.backupControls, false)
-
-          // FILE = LEGACY NUMBER
+        // FILE = LEGACY NUMBER (old control Id)
         } else if (currentControlNumber === xccdfLegacyControlNumber) {
-          logger.debug(`  Control number is not current - changing: ${currentControlNumber} with: ${newXCCDFControlNumber}`)
+          logger.debug(`  Baseline X Control Id is not the same as baseline Y, changing From: ${currentControlNumber} To: ${newXCCDFControlNumber}`)
 
           // Change the V or SV Id to the SV Id based on format flag
-          if (flags.formatControls) {
-            if (inspecProfileFormattedControls.has(xccdfLegacyControlNumber)) {
-              updatedControl = inspecProfileFormattedControls.get(xccdfLegacyControlNumber).replace(`${currentControlNumber}`, `${newXCCDFControlNumber}`)
-            } else {
-              notInProfileJSON++
-              skippedFormatting.push(`(Profile: ${currentControlNumber} XCCDF: ${newXCCDFControlNumber})`)
-              updatedControl = getUpdatedControl(currentFileFullPath, currentControlNumber, 'undefined')
-            }
-            // Don't format, just replace the control name (SV or V) and assign value to the updatedControl variable
+          if (baselineYControls.has(currentControlNumber)) {
+            logger.debug('  \x1B[32mUpdating Control metadata with XCCDF content\x1B[0m')
+            updatedControl = baselineYControls.get(currentControlNumber)
           } else {
+            logger.debug('  \x1B[31mKeeping Control metadata content - Updating Control name\x1B[0m')
+            notInProfileJSON++
+            skipMetadataUpdate.push(`(${currentControlNumber} wasn't updated with metadata from: ${newXCCDFControlNumber})`)
             updatedControl = getUpdatedControl(currentFileFullPath, currentControlNumber, newXCCDFControlNumber)
           }
 
@@ -258,14 +381,14 @@ export default class GenerateUpdateControls extends BaseCommand<typeof GenerateU
           processed++
           controlsProcessedMap.set(newXCCDFControlNumber, 'processed')
 
-          // FILE ≠ XCCDF
-        } else if (xccdfControlNumber === undefined) {
-          logger.debug(`  Control not included in the SAF inspect objects (processXCCDF) output: ${currentControlNumber}`)
+        // FILE ≠ XCCDF
+        } else if (xccdfNewControlNumber === undefined) {
+          logger.warn(`  Control skipped updating (not in the XCCDF guidance): ${currentControlNumber}`)
           skipped++
           skippedControls.push(currentControlNumber)
-          // FILE ≠ XCCDF ≠ LEGACY NUMBER
+        // FILE ≠ XCCDF ≠ LEGACY NUMBER
         } else {
-          logger.debug(`  No logic found processing Control: ${currentControlNumber}`)
+          logger.error('  No logic found processing Control (not current, or in the XCCDF guidance, or a legacy Control)')
         }
       }
     }
@@ -279,22 +402,40 @@ export default class GenerateUpdateControls extends BaseCommand<typeof GenerateU
       }
     }
 
+    // listen for the logger finish event to know when logging has completely finished
     logger.on('finish', () => {
-      console.log(colors.yellow('\n     Total skipped files - no mapping to new control Id:'), colors.green(`${skipped.toString().padStart(4)}`))
-      console.log(colors.yellow('Total processed files - found mapping to new control Id: '), colors.green(`${processed.toString().padStart(3)}`))
+      addToProcessLogData('\nProcess Statistics ===========================================================================\n')
+
+      if (flags.formatControls) {
+        printGreen('╔════════════════════════════════════════════════════════════════════════════════╗')
+        printGreen('║ Controls were formatted the same way `generate delta` will update the controls ║')
+        printGreen('╚════════════════════════════════════════════════════════════════════════════════╝')
+      } else {
+        printRed('╔════════════════════════════════════════════════════════════════════════════════════╗')
+        printRed('║ Controls were NOT formatted the same way `generate delta` will update the controls ║')
+        printRed('╚════════════════════════════════════════════════════════════════════════════════════╝')
+      }
+
+      printYellowGreen('\n     Total skipped files (no mapping to new control Id):', `${skipped.toString().padStart(4)}`)
+      printYellowGreen('Total processed files (found mapping to new control Id): ', `${processed.toString().padStart(3)}`)
 
-      console.log(colors.yellow('\n    Total controls with correct identification: '), colors.green(`${isCorrectControl.toString().padStart(3)}`))
-      console.log(colors.yellow('Total new controls found in the XCCDF guidance: '), colors.green(`${newControls.toString().padStart(3)}`))
+      printYellowGreen('\n    Total controls with correct identification: ', `${isCorrectControl.toString().padStart(3)}`)
+      printYellowGreen('Total new controls found in the XCCDF guidance: ', `${newControls.toString().padStart(3)}`)
 
-      console.log(colors.yellow('\nSkipped control(s) - not included in XCCDF guidance: '), `${colors.green(skippedControls.toString())}`)
-      console.log(colors.yellow('\n  New control(s) found - included in XCCDF guidance: '), `${colors.green(newControlsFound.toString())}`)
+      printYellowGreen('\nSkipped control(s) (not included in XCCDF guidance): ', `${skippedControls.toString()}`)
+      printYellowGreen('\n  New control(s) found (included in XCCDF guidance): ', `${newControlsFound.toString()}`)
+
+      if (notInProfileJSON > 0) {
+        printBoldRedGreen('\nTotal skipped metadata update (not found in Input execution/profile JSON file): ', `${notInProfileJSON.toString().padStart(3)}`)
+        printBoldRedGreen('Control(s) skipped metadata update: ', `${skipMetadataUpdate.toString()}`)
+      }
 
-      if (flags.formatControls && notInProfileJSON > 0) {
-        console.log(colors.bold.red('\nTotal skipped formatting - not found in the profile json: '), colors.green(`${notInProfileJSON.toString().padStart(3)}`))
-        console.log(colors.bold.red('Control(s) skipped formatting: '), colors.green(`${skippedFormatting.toString()}`))
+      if (flags.logLevel !== 'info') {
+        saveProcessLogData()
       }
     })
 
+    // Signal that you're done logging - emits a finish event
     logger.end()
   }
 }
@@ -310,14 +451,14 @@ function getUpdatedControl(path: fs.PathOrFileDescriptor, currentControlNumber:
 }
 
 /* eslint-disable-next-line max-params */
-function saveControl(filePath: string, newXCCDFControlNumber: string, currentControlNumber: string,
-  updatedControl: string, backupControls: boolean, renamedControl: boolean) {
-  const controlsDir = path.dirname(filePath)
-  const newFileName = path.join(controlsDir, newXCCDFControlNumber + '.rb')
+function saveControl(filePath: string, newXCCDFControlNumber: string,
+  currentControlNumber: string, updatedControl: string,
+  backupControls: boolean, renamedControl: boolean) {
+  const newFileName = path.join(path.dirname(filePath), newXCCDFControlNumber + '.rb')
 
   // Move processed (old) control to oldControls folder
   if (backupControls) {
-    const destFilePath = path.resolve(path.join(controlsDir, 'oldControls', currentControlNumber + '.rb'))
+    const destFilePath = path.resolve(path.join(GenerateUpdateControls.backupDir, currentControlNumber + '.rb'))
     if (renamedControl) {
       fs.renameSync(filePath, destFilePath)
     } else {
diff --git a/src/types/fuse/index.d.ts b/src/types/fuse/index.d.ts
new file mode 100644
index 000000000..714e860dc
--- /dev/null
+++ b/src/types/fuse/index.d.ts
@@ -0,0 +1 @@
+declare module 'fuse.js'
diff --git a/src/utils/cliHelper.ts b/src/utils/cliHelper.ts
deleted file mode 100644
index e7851714a..000000000
--- a/src/utils/cliHelper.ts
+++ /dev/null
@@ -1,91 +0,0 @@
-import fs from 'fs'
-import colors from 'colors' // eslint-disable-line no-restricted-imports
-
-const processLogData: Array<string> = []
-let logFileName = ''
-
-export function setProcessLogFileName(fileName: string) {
-  logFileName = fileName
-}
-
-export function getProcessLogData():  Array<string> {
-  return processLogData
-}
-
-export function addToProcessLogData(str: string) {
-  processLogData.push(str)
-}
-
-export function saveProcessLogData() {
-  if (!logFileName) {
-    logFileName = 'CliProcessOutput.log'
-  }
-
-  const file = fs.createWriteStream(logFileName)
-  file.on('error', () => {
-    throw new Error('Error saving the CLI process log data')
-  })
-
-  processLogData.forEach(value => file.write(`${value}\n`))
-  file.end()
-}
-
-// Print Yellow and various combination
-export function printYellow(info: string) {
-  console.log(colors.yellow(info))
-  processLogData.push(`${info}`)
-}
-
-export function printBgYellow(info: string) {
-  console.log(colors.bgYellow(info))
-  processLogData.push(`${info}`)
-}
-
-export function printYellowGreen(title: string, info: string) {
-  console.log(colors.yellow(title), colors.green(info))
-  processLogData.push(`${title} ${info}`)
-}
-
-export function printYellowBgGreen(title: string, info: string) {
-  console.log(colors.yellow(title), colors.bgGreen(info))
-  processLogData.push(`${title} ${info}`)
-}
-
-// Print Red and various combination
-export function printRed(info: string) {
-  console.log(colors.red(info))
-  processLogData.push(`${info}`)
-}
-
-export function printBgRed(info: string) {
-  console.log(colors.bgRed(info))
-  processLogData.push(`${info}`)
-}
-
-export function printBgRedRed(title: string, info: string) {
-  console.log(colors.bgRed(title), colors.red(info))
-  processLogData.push(`${title} ${info}`)
-}
-
-// Print Magenta and various combination
-export function printMagenta(info: string) {
-  console.log(colors.magenta(info))
-  processLogData.push(`${info}`)
-}
-
-export function printBgMagentaRed(title: string, info: string) {
-  console.log(colors.bgMagenta(title), colors.red(info))
-  processLogData.push(`${title} ${info}`)
-}
-
-// Print Cyan
-export function printCyan(info: string) {
-  console.log(colors.cyan(info))
-  processLogData.push(`${info}`)
-}
-
-// Print Green
-export function printGreen(info: string) {
-  console.log(colors.green(info))
-  processLogData.push(`${info}`)
-}
diff --git a/src/utils/logging.ts b/src/utils/logging.ts
index d9d959db1..47cbaa108 100644
--- a/src/utils/logging.ts
+++ b/src/utils/logging.ts
@@ -4,13 +4,13 @@ import colors from 'colors' // eslint-disable-line no-restricted-imports
 
 /**
  * Summary type represents a summary of an HDF execution.
- * @property {string[]} profileNames - An array of profile names.
- * @property {number} controlCount - The total number of controls.
- * @property {number} passedCount - The number of controls that passed.
- * @property {number} failedCount - The number of controls that failed.
+ * @property {string[]} profileNames     - An array of profile names.
+ * @property {number} controlCount       - The total number of controls.
+ * @property {number} passedCount        - The number of controls that passed.
+ * @property {number} failedCount        - The number of controls that failed.
  * @property {number} notApplicableCount - The number of controls that are not applicable.
- * @property {number} notReviewedCount - The number of controls that were not reviewed.
- * @property {number} errorCount - The number of controls that resulted in an error.
+ * @property {number} notReviewedCount   - The number of controls that were not reviewed.
+ * @property {number} errorCount         - The number of controls that resulted in an error.
  */
 
 export type Summary = {
@@ -23,11 +23,13 @@ export type Summary = {
   errorCount: number;
 }
 
+// Use user defined colors. Used by the console log transporter
 const syslogColors = {
-  debug: 'bold blue',
+  debug: 'blue',
   info: 'cyan',
   notice: 'white',
-  warning: 'bold yellow',
+  warn: 'magenta',
+  warning: 'bold magenta',
   error: 'bold red',
   verbose: 'blue',
   crit: 'inverse yellow',
@@ -37,10 +39,11 @@ const syslogColors = {
 
 /**
  * createWinstonLogger function creates a Winston logger.
- * @param {string} mapperName - The name of the mapper.
+ * @param {string} mapperName     - The name of the mapper.
  * @param {string} [level='info'] - The log level. Default is 'info'.
- * @returns {Logger} A Winston logger.
+ * @returns {Logger}              - A Winston logger.
  */
+
 export function createWinstonLogger(mapperName: string, level = 'info'): Logger {
   const transportList: transport[] = [
     new transports.File({filename: 'saf-cli.log'}),
@@ -70,28 +73,7 @@ export function createWinstonLogger(mapperName: string, level = 'info'): Logger
     level,
   })
 }
-// export function createWinstonLogger(mapperName: string, level = 'info'): Logger {
-//   const transportList: transport[] = [
-//     new transports.File({filename: 'saf-cli.log'}),
-//   ]
-
-//   if ((process.env.NODE_ENV !== 'production' && process.env.NODE_ENV !== 'test') || level === 'verbose') {
-//     transportList.push(new transports.Console())
-//   }
 
-//   return createLogger({
-//     transports: transportList,
-//     level,
-//     format: format.combine(
-//       format.timestamp({
-//         format: 'MMM-DD-YYYY HH:mm:ss Z',
-//       }),
-//       format.printf(
-//         info => `[${[info.timestamp]}] ${mapperName} ${info.message}`,
-//       ),
-//     ),
-//   })
-// }
 /**
  * The function `getHDFSummary` takes an execution object and returns a summary string containing
  * information about the profiles, passed/failed/not applicable/not reviewed counts.
diff --git a/src/utils/oclif/cliHelper.ts b/src/utils/oclif/cliHelper.ts
index e7851714a..e26cb7bec 100644
--- a/src/utils/oclif/cliHelper.ts
+++ b/src/utils/oclif/cliHelper.ts
@@ -57,6 +57,11 @@ export function printRed(info: string) {
   processLogData.push(`${info}`)
 }
 
+export function printBoldRedGreen(title: string, info: string) {
+  console.log(colors.bold.red(title), colors.green(info))
+  processLogData.push(`${title} ${info}`)
+}
+
 export function printBgRed(info: string) {
   console.log(colors.bgRed(info))
   processLogData.push(`${info}`)
diff --git a/test/commands/convert/hdf2ckl.test.ts b/test/commands/convert/hdf2ckl.test.ts
index 196b69163..fb891b342 100644
--- a/test/commands/convert/hdf2ckl.test.ts
+++ b/test/commands/convert/hdf2ckl.test.ts
@@ -11,8 +11,8 @@ describe('Test hdf2checklist', () => {
     .stdout()
     .command(['convert hdf2ckl', '-i', path.resolve('./test/sample_data/HDF/input/red_hat_good.json'), '-o', `${tmpobj.name}/hdf2ckl_test.ckl`])
     .it('hdf-converter output test - defaults', () => {
-      const test = fs.readFileSync(`${tmpobj.name}/hdf2ckl_test.ckl`, 'utf8')
-      const sample = fs.readFileSync(path.resolve('./test/sample_data/checklist/red_hat_good.ckl'), 'utf8')
+      const test = fs.readFileSync(`${tmpobj.name}/hdf2ckl_test.ckl`, 'utf8').replace(/\r/gi, '')
+      const sample = fs.readFileSync(path.resolve('./test/sample_data/checklist/red_hat_good.ckl'), 'utf8').replace(/\r/gi, '')
       expect(omitChecklistChangingFields(test)).to.eql(omitChecklistChangingFields(sample))
     })
 
@@ -20,8 +20,8 @@ describe('Test hdf2checklist', () => {
     .stdout()
     .command(['convert hdf2ckl', '-i', path.resolve('./test/sample_data/HDF/input/vSphere8_report.json'), '-o', `${tmpobj.name}/hdf2ckl_test.ckl`])
     .it('hdf-converter output test - inspec results from profile with dependent profiles', () => {
-      const test = fs.readFileSync(`${tmpobj.name}/hdf2ckl_test.ckl`, 'utf8')
-      const sample = fs.readFileSync(path.resolve('./test/sample_data/checklist/vSphere8_report.ckl'), 'utf8')
+      const test = fs.readFileSync(`${tmpobj.name}/hdf2ckl_test.ckl`, 'utf8').replace(/\r/gi, '')
+      const sample = fs.readFileSync(path.resolve('./test/sample_data/checklist/vSphere8_report.ckl'), 'utf8').replace(/\r/gi, '')
       expect(omitChecklistChangingFields(test)).to.eql(omitChecklistChangingFields(sample))
     })
 
@@ -29,8 +29,8 @@ describe('Test hdf2checklist', () => {
     .stdout()
     .command(['convert hdf2ckl', '-i', path.resolve('./test/sample_data/HDF/input/red_hat_good.json'), '-o', `${tmpobj.name}/hdf2ckl_metadata_test.ckl`, '-m', path.resolve('./test/sample_data/checklist/metadata.json')])
     .it('hdf-converter output test - with metadata file', () => {
-      const test = fs.readFileSync(`${tmpobj.name}/hdf2ckl_metadata_test.ckl`, 'utf8')
-      const sample = fs.readFileSync(path.resolve('./test/sample_data/checklist/red_hat_good_metadata.ckl'), 'utf8')
+      const test = fs.readFileSync(`${tmpobj.name}/hdf2ckl_metadata_test.ckl`, 'utf8').replace(/\r/gi, '')
+      const sample = fs.readFileSync(path.resolve('./test/sample_data/checklist/red_hat_good_metadata.ckl'), 'utf8').replace(/\r/gi, '')
       expect(omitChecklistChangingFields(test)).to.eql(omitChecklistChangingFields(sample))
     })
 
@@ -44,8 +44,8 @@ describe('Test hdf2checklist', () => {
       '--ip', '127.0.0.1', '--role', 'Domain Controller', 
       '--assettype', 'Computing', '--techarea', 'Other Review'])
     .it('hdf-converter output test - with metadata flags', () => {
-      const test = fs.readFileSync(`${tmpobj.name}/hdf2ckl_metadata_test.ckl`, 'utf8')
-      const sample = fs.readFileSync(path.resolve('./test/sample_data/checklist/red_hat_good_metadata.ckl'), 'utf8')
+      const test = fs.readFileSync(`${tmpobj.name}/hdf2ckl_metadata_test.ckl`, 'utf8').replace(/\r/gi, '')
+      const sample = fs.readFileSync(path.resolve('./test/sample_data/checklist/red_hat_good_metadata.ckl'), 'utf8').replace(/\r/gi, '')
       expect(omitChecklistChangingFields(test)).to.eql(omitChecklistChangingFields(sample))
     })
 
@@ -53,8 +53,8 @@ describe('Test hdf2checklist', () => {
     .stdout()
     .command(['convert hdf2ckl', '-i', path.resolve('./test/sample_data/HDF/input/RHEL7_overrides_hdf.json'), '-o', `${tmpobj.name}/hdf2ckl_overrides_test.ckl`])
     .it('hdf-converter output test - with severity overrides', () => {
-      const test = fs.readFileSync(`${tmpobj.name}/hdf2ckl_overrides_test.ckl`, 'utf8')
-      const sample = fs.readFileSync(path.resolve('./test/sample_data/checklist/converted-rhel7_overrides.ckl'), 'utf8')
+      const test = fs.readFileSync(`${tmpobj.name}/hdf2ckl_overrides_test.ckl`, 'utf8').replace(/\r/gi, '')
+      const sample = fs.readFileSync(path.resolve('./test/sample_data/checklist/converted-rhel7_overrides.ckl'), 'utf8').replace(/\r/gi, '')
       expect(omitChecklistChangingFields(test)).to.eql(omitChecklistChangingFields(sample))
     })
 
diff --git a/test/commands/generate/delta.test.ts b/test/commands/generate/delta.test.ts
index 8afd82d20..fed4c36ae 100644
--- a/test/commands/generate/delta.test.ts
+++ b/test/commands/generate/delta.test.ts
@@ -1,22 +1,23 @@
+/* eslint-disable array-bracket-newline */
+/* eslint-disable array-element-newline */
 import {expect, test} from '@oclif/test'
 import tmp from 'tmp'
 import path from 'path'
 import fs from 'fs'
 
+// Functional tests
 describe('The generate delta command', () => {
-  // should process delta request with rule id type
   const tmpobj = tmp.dirSync({unsafeCleanup: true})
+
+  // should process delta request with rule id type
   test
     .stdout()
     .command(['generate delta',
-      '-J',
-      path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
-      '-X',
-      path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
-      '-o',
-      `${tmpobj.name}`,
-      '-T',
-      'rule'])
+      '-J', path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
+      '-X', path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
+      '-o', `${tmpobj.name}`,
+      '-T', 'rule',
+    ])
     .it('should generate the controls for delta request with "rule" id type', () => {
       const fileCount = fs.readdirSync(`${tmpobj.name}/controls/`).length
       expect(fileCount).to.eql(4)
@@ -27,12 +28,10 @@ describe('The generate delta command', () => {
   test
     .stdout()
     .command(['generate delta',
-      '-J',
-      path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
-      '-X',
-      path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
-      '-o',
-      `${tmpobj.name}/RHEL_7`])
+      '-J', path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
+      '-X', path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
+      '-o', `${tmpobj.name}/RHEL_7`,
+    ])
     .it('should generate the output folder and place the controls in newly created folder for review', () => {
       const fileCount = fs.readdirSync(`${tmpobj.name}/RHEL_7/controls/`).length
       expect(fileCount).to.eql(4)
@@ -41,14 +40,11 @@ describe('The generate delta command', () => {
   test
     .stdout()
     .command(['generate delta',
-      '-J',
-      path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
-      '-X',
-      path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
-      '-o',
-      `${tmpobj.name}/RHEL_7`,
-      '-r',
-      `${tmpobj.name}/RHEL_7/my-report.md`])
+      '-J', path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
+      '-X', path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
+      '-o', `${tmpobj.name}/RHEL_7`,
+      '-r', `${tmpobj.name}/RHEL_7/my-report.md`,
+    ])
     .it('should generate a report with given file name and place it on the specified directory', () => {
       expect(fs.lstatSync((`${tmpobj.name}/RHEL_7/my-report.md`)).isFile()).to.be.true // skipcq: JS-0354
     })
@@ -56,14 +52,11 @@ describe('The generate delta command', () => {
   test
     .stdout()
     .command(['generate delta',
-      '-J',
-      path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
-      '-X',
-      path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
-      '-o',
-      `${tmpobj.name}`,
-      '-r',
-      `${tmpobj.name}`])
+      '-J', path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
+      '-X', path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
+      '-o', `${tmpobj.name}`,
+      '-r', `${tmpobj.name}`,
+    ])
     .it('should generate a report name delta.md and place it in the default directory', () => {
       expect(fs.lstatSync((`${tmpobj.name}/delta.md`)).isFile()).to.be.true // skipcq: JS-0354
     })
@@ -73,14 +66,11 @@ describe('The generate delta command', () => {
   test
     .stdout()
     .command(['generate delta',
-      '-J',
-      path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
-      '-X',
-      path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
-      '-o',
-      `${tmpobj.name}`,
-      '-T',
-      'group'])
+      '-J', path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
+      '-X', path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
+      '-o', `${tmpobj.name}`,
+      '-T', 'group',
+    ])
     .it('should generate the controls for delta request with "group" id type', () => {
       const fileCount = fs.readdirSync(`${tmpobj.name}/controls/`).length
       expect(fileCount).to.eql(4)
@@ -90,14 +80,11 @@ describe('The generate delta command', () => {
   test
     .stdout()
     .command(['generate delta',
-      '-J',
-      path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
-      '-X',
-      path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
-      '-o',
-      `${tmpobj.name}`,
-      '-T',
-      'cis'])
+      '-J', path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
+      '-X', path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
+      '-o', `${tmpobj.name}`,
+      '-T', 'cis',
+    ])
     .it('should generate the controls for delta request with "cis" id type', () => {
       const fileCount = fs.readdirSync(`${tmpobj.name}/controls/`).length
       expect(fileCount).to.eql(4)
@@ -108,22 +95,57 @@ describe('The generate delta command', () => {
   test
     .stdout()
     .command(['generate delta',
-      '-J',
-      path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
-      '-X',
-      path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
-      '-o',
-      `${tmpobj.name}/controls`,
-      '-T',
-      'version'])
+      '-J', path.resolve('./test/sample_data/inspec/json/rhel-7-v3r7-mini-sample-profile.json'),
+      '-X', path.resolve('./test/sample_data/xccdf/stigs/rhel-7-v3r8-mini-sample-xxcdf.xml'),
+      '-o', `${tmpobj.name}/controls`,
+      '-T', 'version',
+    ])
     .it('should generate the controls for delta request with "version" id type', () => {
       const fileCount = fs.readdirSync(`${tmpobj.name}/controls/`).length
       expect(fileCount).to.eql(4)
     })
 
-  // should provide error if not given a proper InSpec Profile JSON file
-  // should provide error if not given a proper XCCDF file
-
   // should process delta request with oval definitions file specified
   // should provide error if oval definitions flag is specified with incorrect file format
+
+  // Process delta mapping functionality
+  test
+    .stdout()
+    .command(['generate delta',
+      '-J', path.resolve('./test/sample_data/inspec/json/profile_and_controls/Windows_Server_2022_v1r3_mini-profile.json'),
+      '-X', path.resolve('./test/sample_data/xccdf/stigs/Windows_Server_2022_V2R1_mini-sample-xccdf.xml'),
+      '-o', `${tmpobj.name}`,
+      '-T', 'rule', '-M',
+      '-c', path.resolve('./test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/'),
+    ])
+    .timeout(25000)
+    .it('should match and map controls from one profile to another', async ctx => {
+      // Wait for the command to finish execution
+      await ctx.returned
+
+      // Now you can safely access the output
+      expect(ctx.stdout).to.contain('Match Controls:  5')
+    })
+  test
+    .stdout()
+    .command(['generate delta',
+      '-J', path.resolve('./test/sample_data/inspec/json/profile_and_controls/Windows_Server_2022_v1r3_mini-profile.json'),
+      '-X', path.resolve('./test/sample_data/xccdf/stigs/Windows_Server_2022_V2R1_mini-sample-xccdf.xml'),
+      '-o', `${tmpobj.name}`,
+      '-T', 'rule', '-M',
+      '-c', path.resolve('./test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/'),
+    ])
+    .timeout(25000)
+    .it('should map to the correct filenames', async ctx => {
+      await ctx.returned
+
+      const output = ctx.stdout.split('\n')
+      expect(output.includes('Total Controls Found on Delta Directory:  5'))
+      expect(output.includes('Total Controls Found on XCCDF:  5'))
+      expect(output.includes('["+","SV-254238"]'))
+      expect(output.includes('["+","SV-254239"]'))
+      expect(output.includes('["+","SV-254240"]'))
+      expect(output.includes('["+","SV-254241"]'))
+      expect(output.includes('["+","SV-254242"]'))
+    })
 })
diff --git a/test/sample_data/inspec/json/profile_and_controls/Windows_Server_2022_v1r3_mini-profile.json b/test/sample_data/inspec/json/profile_and_controls/Windows_Server_2022_v1r3_mini-profile.json
new file mode 100644
index 000000000..43f4ecfe5
--- /dev/null
+++ b/test/sample_data/inspec/json/profile_and_controls/Windows_Server_2022_v1r3_mini-profile.json
@@ -0,0 +1 @@
+{"name":"microsoft-windows-server-2019-stig-baseline","title":"microsoft-windows-server-2019-stig-baseline","maintainer":"The Authors","copyright":"The Authors","copyright_email":"you@example.com","license":"Apache-2.0","summary":"Inspec Validation Profile for Microsoft Windows Member Server 2019 STIG","version":"1.3.24","inspec_version":">= 4.0","inputs":[],"supports":[],"controls":[{"title":"Windows Server 2019 administrative accounts must not be used with\napplications that access the Internet, such as web browsers, or with potential\nInternet sources, such as email.","desc":"Using applications that access the Internet or have potential Internet\nsources using administrative privileges exposes a system to compromise. If a\nflaw in an application is exploited while running as a privileged user, the\nentire system could be compromised. Web browsers and email are common attack\nvectors for introducing malicious code and must not be run with an\nadministrative account.\n\n    Since administrative accounts may generally change or work around technical\nrestrictions for running a web browser or other applications, it is essential\nthat policy require administrative accounts to not access the Internet or use\napplications such as email.\n\n    The policy should define specific exceptions for local service\nadministration. These exceptions may include HTTP(S)-based tools that are used\nfor the administration of the local system, services, or attached devices.\n\n    Whitelisting can be used to enforce the policy to ensure compliance.","descriptions":{"default":"Using applications that access the Internet or have potential Internet\nsources using administrative privileges exposes a system to compromise. If a\nflaw in an application is exploited while running as a privileged user, the\nentire system could be compromised. Web browsers and email are common attack\nvectors for introducing malicious code and must not be run with an\nadministrative account.\n\n    Since administrative accounts may generally change or work around technical\nrestrictions for running a web browser or other applications, it is essential\nthat policy require administrative accounts to not access the Internet or use\napplications such as email.\n\n    The policy should define specific exceptions for local service\nadministration. These exceptions may include HTTP(S)-based tools that are used\nfor the administration of the local system, services, or attached devices.\n\n    Whitelisting can be used to enforce the policy to ensure compliance.","rationale":"","check":"Determine whether organization policy, at a minimum, prohibits\nadministrative accounts from using applications that access the Internet, such\nas web browsers, or with potential Internet sources, such as email, except as\nnecessary for local service administration.\n\n    If it does not, this is a finding.\n\n    The organization may use technical means such as whitelisting to prevent\nthe use of browsers and mail applications to enforce this requirement.","fix":"Establish a policy, at minimum, to prohibit administrative accounts from\nusing applications that access the Internet, such as web browsers, or with\npotential Internet sources, such as email. Ensure the policy is enforced.\n\n    The organization may use technical means such as whitelisting to prevent\nthe use of browsers and mail applications to enforce this requirement."},"impact":0.7,"refs":[],"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-93205","rid":"SV-103293r1_rule","stig_id":"WN19-00-000030","fix_id":"F-99451r1_fix","cci":["CCI-000366"],"nist":["CM-6 b","Rev_4"]},"code":"control \"V-93205\" do\n  title \"Windows Server 2019 administrative accounts must not be used with\napplications that access the Internet, such as web browsers, or with potential\nInternet sources, such as email.\"\n  desc  \"Using applications that access the Internet or have potential Internet\nsources using administrative privileges exposes a system to compromise. If a\nflaw in an application is exploited while running as a privileged user, the\nentire system could be compromised. Web browsers and email are common attack\nvectors for introducing malicious code and must not be run with an\nadministrative account.\n\n    Since administrative accounts may generally change or work around technical\nrestrictions for running a web browser or other applications, it is essential\nthat policy require administrative accounts to not access the Internet or use\napplications such as email.\n\n    The policy should define specific exceptions for local service\nadministration. These exceptions may include HTTP(S)-based tools that are used\nfor the administration of the local system, services, or attached devices.\n\n    Whitelisting can be used to enforce the policy to ensure compliance.\"\n  desc  \"rationale\", \"\"\n  desc  'check', \"Determine whether organization policy, at a minimum, prohibits\nadministrative accounts from using applications that access the Internet, such\nas web browsers, or with potential Internet sources, such as email, except as\nnecessary for local service administration.\n\n    If it does not, this is a finding.\n\n    The organization may use technical means such as whitelisting to prevent\nthe use of browsers and mail applications to enforce this requirement.\"\n  desc  'fix', \"Establish a policy, at minimum, to prohibit administrative accounts from\nusing applications that access the Internet, such as web browsers, or with\npotential Internet sources, such as email. Ensure the policy is enforced.\n\n    The organization may use technical means such as whitelisting to prevent\nthe use of browsers and mail applications to enforce this requirement.\"\n  impact 0.7\n  tag 'severity': nil\n  tag 'gtitle': 'SRG-OS-000480-GPOS-00227'\n  tag 'gid': 'V-93205'\n  tag 'rid': 'SV-103293r1_rule'\n  tag 'stig_id': 'WN19-00-000030'\n  tag 'fix_id': 'F-99451r1_fix'\n  tag 'cci': [\"CCI-000366\"]\n  tag 'nist': [\"CM-6 b\", \"Rev_4\"]\n\n  describe \"A manual review is required to verify that administrative accounts are not being used with applications that access the Internet, such as web browsers, or with potential Internet sources, such as email\" do\n    skip \"A manual review is required to verify that administrative accounts are not being used with applications that access the Internet, such as web browsers, or with potential Internet sources, such as email\"\n  end\nend\n","source_location":{"ref":"microsoft-windows-server-2019-stig-baseline/controls/V-93205.rb","line":3},"id":"V-93205"},{"title":"Windows Server 2019 members of the Backup Operators group must have\nseparate accounts for backup duties and normal operational tasks.","desc":"Backup Operators are able to read and write to any file in the system,\nregardless of the rights assigned to it. Backup and restore rights permit users\nto circumvent the file access restrictions present on NTFS disk drives for\nbackup and restore purposes. Members of the Backup Operators group must have\nseparate logon accounts for performing backup duties.","descriptions":{"default":"Backup Operators are able to read and write to any file in the system,\nregardless of the rights assigned to it. Backup and restore rights permit users\nto circumvent the file access restrictions present on NTFS disk drives for\nbackup and restore purposes. Members of the Backup Operators group must have\nseparate logon accounts for performing backup duties.","rationale":"","check":"If no accounts are members of the Backup Operators group, this is NA.\n\n    Verify users with accounts in the Backup Operators group have a separate\nuser account for backup functions and for performing normal user tasks.\n\n    If users with accounts in the Backup Operators group do not have separate\naccounts for backup functions and standard user functions, this is a finding.","fix":"Ensure each member of the Backup Operators group has separate\naccounts for backup functions and standard user functions."},"impact":0.0,"refs":[],"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-93207","rid":"SV-103295r1_rule","stig_id":"WN19-00-000040","fix_id":"F-99453r1_fix","cci":["CCI-000366"],"nist":["CM-6 b","Rev_4"]},"code":"control \"V-93207\" do\n  title \"Windows Server 2019 members of the Backup Operators group must have\nseparate accounts for backup duties and normal operational tasks.\"\n  desc  \"Backup Operators are able to read and write to any file in the system,\nregardless of the rights assigned to it. Backup and restore rights permit users\nto circumvent the file access restrictions present on NTFS disk drives for\nbackup and restore purposes. Members of the Backup Operators group must have\nseparate logon accounts for performing backup duties.\"\n  desc  \"rationale\", \"\"\n  desc  'check', \"If no accounts are members of the Backup Operators group, this is NA.\n\n    Verify users with accounts in the Backup Operators group have a separate\nuser account for backup functions and for performing normal user tasks.\n\n    If users with accounts in the Backup Operators group do not have separate\naccounts for backup functions and standard user functions, this is a finding.\"\n  desc  'fix', \"Ensure each member of the Backup Operators group has separate\naccounts for backup functions and standard user functions.\"\n  impact 0.5\n  tag 'severity': nil\n  tag 'gtitle': 'SRG-OS-000480-GPOS-00227'\n  tag 'gid': 'V-93207'\n  tag 'rid': 'SV-103295r1_rule'\n  tag 'stig_id': 'WN19-00-000040'\n  tag 'fix_id': 'F-99453r1_fix'\n  tag 'cci': [\"CCI-000366\"]\n  tag 'nist': [\"CM-6 b\", \"Rev_4\"]\n\n  backup_operators_group = command(\"net localgroup 'Backup Operators' | Format-List | Findstr /V 'Alias Name Comment Members - command'\").stdout.strip.split(\"\\r\\n\")\n  backup_operators = input('backup_operators')\n  if backup_operators_group.empty?\n    impact 0.0\n    describe 'Backup Operators Group Empty' do\n      skip 'The control is N/A as there are no users in the Backup Operators group'\n    end\n  else\n    backup_operators_group.each do |user|\n      describe user do\n        it { should be_in backup_operators }\n      end\n    end\n  end\nend\n","source_location":{"ref":"microsoft-windows-server-2019-stig-baseline/controls/V-93207.rb","line":3},"id":"V-93207"},{"title":"Windows Server 2019 users with Administrative privileges must have separate accounts for administrative duties and normal operational tasks.","desc":"Using a privileged account to perform routine functions makes the computer vulnerable to malicious software inadvertently introduced during a session that has been granted full privileges.","descriptions":{"default":"Using a privileged account to perform routine functions makes the computer vulnerable to malicious software inadvertently introduced during a session that has been granted full privileges.","rationale":"","check":"Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account.\n    If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding.","fix":"Ensure each user with administrative privileges has a separate account for user duties and one for privileged duties."},"impact":0.0,"refs":[],"tags":{"severity":null,"gtitle":"SRG-OS-000480-GPOS-00227","gid":"V-93369","rid":"SV-103457r1_rule","stig_id":"WN19-00-000010","fix_id":"F-99615r1_fix","cci":["CCI-000366"],"nist":["CM-6 b","Rev_4"]},"code":"control \"V-93369\" do\n  title \"Windows Server 2019 users with Administrative privileges must have separate accounts for administrative duties and normal operational tasks.\"\n  desc  \"Using a privileged account to perform routine functions makes the computer vulnerable to malicious software inadvertently introduced during a session that has been granted full privileges.\"\n  desc  \"rationale\", \"\"\n  desc  \"check\", \"Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account.\n    If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding.\"\n  desc  \"fix\", \"Ensure each user with administrative privileges has a separate account for user duties and one for privileged duties.\"\n  impact 0.7\n  tag severity: nil\n  tag gtitle: \"SRG-OS-000480-GPOS-00227\"\n  tag gid: \"V-93369\"\n  tag rid: \"SV-103457r1_rule\"\n  tag stig_id: \"WN19-00-000010\"\n  tag fix_id: \"F-99615r1_fix\"\n  tag cci: [\"CCI-000366\"]\n  tag nist: [\"CM-6 b\", \"Rev_4\"]\n\n  administrators = input('administrators')\n  administrator_group = command(\"net localgroup Administrators | Format-List | Findstr /V 'Alias Name Comment Members - command'\").stdout.strip.split(\"\\r\\n\")\n  administrator_group.each do |user|\n    describe user.to_s do\n      it { should be_in administrators }\n    end\n  end\n  if administrator_group.empty?\n    impact 0.0\n    describe 'There are no users with administrative privileges' do\n      skip 'There are no users with administrative privileges so this control is NA'\n    end\n  end\nend","source_location":{"ref":"microsoft-windows-server-2019-stig-baseline/controls/V-93369.rb","line":3},"id":"V-93369"},{"title":"Windows Server 2019 manually managed application account passwords must be at least 15 characters in length.","desc":"Application/service account passwords must be of sufficient length to prevent being easily cracked. Application/service accounts that are manually managed must have passwords at least 15 characters in length.","descriptions":{"default":"Application/service account passwords must be of sufficient length to prevent being easily cracked. Application/service accounts that are manually managed must have passwords at least 15 characters in length.","rationale":"","check":"Determine if manually managed application/service accounts exist. If none exist, this is NA.\n\n    Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least 15 characters in length.\n\n    If such a policy does not exist or has not been implemented, this is a finding.","fix":"Establish a policy that requires application/service account passwords that are manually managed to be at least 15 characters in length. Ensure the policy is enforced."},"impact":0.5,"refs":[],"tags":{"severity":null,"gtitle":"SRG-OS-000078-GPOS-00046","gid":"V-93461","rid":"SV-103547r1_rule","stig_id":"WN19-00-000050","fix_id":"F-99705r1_fix","cci":["CCI-000205"],"nist":["IA-5 (1) (a)","Rev_4"]},"code":"control \"V-93461\" do\n  title \"Windows Server 2019 manually managed application account passwords must be at least #{input('minimum_password_length_manual')} characters in length.\"\n  desc  \"Application/service account passwords must be of sufficient length to prevent being easily cracked. Application/service accounts that are manually managed must have passwords at least #{input('minimum_password_length_manual')} characters in length.\"\n  desc  \"rationale\", \"\"\n  desc  \"check\", \"Determine if manually managed application/service accounts exist. If none exist, this is NA.\n\n    Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least #{input('minimum_password_length_manual')} characters in length.\n\n    If such a policy does not exist or has not been implemented, this is a finding.\"\n  desc  \"fix\", \"Establish a policy that requires application/service account passwords that are manually managed to be at least #{input('minimum_password_length_manual')} characters in length. Ensure the policy is enforced.\"\n  impact 0.5\n  tag severity: nil\n  tag gtitle: \"SRG-OS-000078-GPOS-00046\"\n  tag gid: \"V-93461\"\n  tag rid: \"SV-103547r1_rule\"\n  tag stig_id: \"WN19-00-000050\"\n  tag fix_id: \"F-99705r1_fix\"\n  tag cci: [\"CCI-000205\"]\n  tag nist: [\"IA-5 (1) (a)\", \"Rev_4\"]\n\n  mplm = input('minimum_password_length_manual')\n\n  describe 'Please Check all Accounts that are used for Services or Applications to validate they meet the Password Length Policy, Control is a Manual Check' do\n    skip \"Determine if manually managed application/service accounts exist. If none exist, this is NA. Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least #{mplm} characters in length.\"\n  end\nend\n","source_location":{"ref":"microsoft-windows-server-2019-stig-baseline/controls/V-93461.rb","line":3},"id":"V-93461"},{"title":"Windows Server 2019 passwords for the built-in Administrator account must be changed at least every 60 days.","desc":"The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure.\n    Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every \"30\" days by default.","descriptions":{"default":"The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure.\n    Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every \"30\" days by default.","rationale":"","check":"Review the password last set date for the built-in Administrator account.\n\n    Domain controllers:\n    Open \"PowerShell\".\n    Enter \"Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like \"*-500\" | Ft Name, SID, PasswordLastSet\".\n    If the \"PasswordLastSet\" date is greater than \"60\" days old, this is a finding.\n\n    Member servers and standalone systems:\n    Open \"Command Prompt\".\n    Enter 'Net User [account name] | Find /i \"Password Last Set\"', where [account name] is the name of the built-in administrator account.\n    (The name of the built-in Administrator account must be changed to something other than \"Administrator\" per STIG requirements.)\n    If the \"PasswordLastSet\" date is greater than \"60\" days old, this is a finding.","fix":"Change the built-in Administrator account password at least every \"60\" days.\n    Automated tools, such as Microsoft's LAPS, may be used on domain-joined member servers to accomplish this."},"impact":0.5,"refs":[],"tags":{"severity":null,"gtitle":"SRG-OS-000076-GPOS-00044","gid":"V-93473","rid":"SV-103559r1_rule","stig_id":"WN19-00-000020","fix_id":"F-99717r1_fix","cci":["CCI-000199"],"nist":["IA-5 (1) (d)","Rev_4"]},"code":"control \"V-93473\" do\n  title \"Windows Server 2019 passwords for the built-in Administrator account must be changed at least every 60 days.\"\n  desc  \"The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure.\n    Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every \\\"30\\\" days by default.\"\n  desc  \"rationale\", \"\"\n  desc  \"check\", \"Review the password last set date for the built-in Administrator account.\n\n    Domain controllers:\n    Open \\\"PowerShell\\\".\n    Enter \\\"Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like \\\"*-500\\\" | Ft Name, SID, PasswordLastSet\\\".\n    If the \\\"PasswordLastSet\\\" date is greater than \\\"60\\\" days old, this is a finding.\n\n    Member servers and standalone systems:\n    Open \\\"Command Prompt\\\".\n    Enter 'Net User [account name] | Find /i \\\"Password Last Set\\\"', where [account name] is the name of the built-in administrator account.\n    (The name of the built-in Administrator account must be changed to something other than \\\"Administrator\\\" per STIG requirements.)\n    If the \\\"PasswordLastSet\\\" date is greater than \\\"60\\\" days old, this is a finding.\"\n  desc  \"fix\", \"Change the built-in Administrator account password at least every \\\"60\\\" days.\n    Automated tools, such as Microsoft's LAPS, may be used on domain-joined member servers to accomplish this.\"\n  impact 0.5\n  tag severity: nil\n  tag gtitle: \"SRG-OS-000076-GPOS-00044\"\n  tag gid: \"V-93473\"\n  tag rid: \"SV-103559r1_rule\"\n  tag stig_id: \"WN19-00-000020\"\n  tag fix_id: \"F-99717r1_fix\"\n  tag cci: [\"CCI-000199\"]\n  tag nist: [\"IA-5 (1) (d)\", \"Rev_4\"]\n\n  administrator = input('local_administrator')\n  domain_role = command('wmic computersystem get domainrole | Findstr /v DomainRole').stdout.strip\n\n  if domain_role == '4' || domain_role == '5'\n    password_set_date = json({ command: \"Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where-Object {$_.SID -like '*-500' -and $_.PasswordLastSet -lt ((Get-Date).AddDays(-60))} | Select-Object -ExpandProperty PasswordLastSet | ConvertTo-Json\" })\n    date = password_set_date[\"DateTime\"]\n    describe \"Password Last Set Date\" do\n      it \"The built-in Administrator account must be changed at least every 60 days.\" do\n        expect(date).to be_nil\n      end\n    end\n  else\n    if administrator == \"Administrator\"\n      describe 'The name of the built-in Administrator account:' do\n        it 'It must be changed to something other than \"Administrator\" per STIG requirements' do\n          failure_message = \"Change the built-in Administrator account name to something other than: #{administrator}\"\n          expect(administrator).not_to eq(\"Administrator\"), failure_message\n        end\n      end\n    end\n    local_password_set_date = json({ command: \"Get-LocalUser -name #{administrator} | Where-Object {$_.PasswordLastSet -le (Get-Date).AddDays(-60)} | Select-Object -ExpandProperty PasswordLastSet | ConvertTo-Json\"})\n    local_date =  local_password_set_date[\"DateTime\"]\n    describe \"Password Last Set Date\" do\n      it \"The built-in Administrator account must be changed at least every 60 days.\" do\n        expect(local_date).to be_nil\n      end\n    end\n  end\nend","source_location":{"ref":"microsoft-windows-server-2019-stig-baseline/controls/V-93473.rb","line":3},"id":"V-93473"}],"groups":[{"title":null,"controls":["V-93205"],"id":"controls/V-93205.rb"},{"title":null,"controls":["V-93207"],"id":"controls/V-93207.rb"},{"title":null,"controls":["V-93369"],"id":"controls/V-93369.rb"},{"title":null,"controls":["V-93461"],"id":"controls/V-93461.rb"},{"title":null,"controls":["V-93473"],"id":"controls/V-93473.rb"}],"sha256":"92e03573d4f043a9e095983afd0a2dbafb832ce15a7dd379c4cb39f3322f4e42","status_message":"","status":"loaded","generator":{"name":"inspec","version":"4.56.20"}}
diff --git a/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93205.rb b/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93205.rb
new file mode 100644
index 000000000..6ffd24acc
--- /dev/null
+++ b/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93205.rb
@@ -0,0 +1,54 @@
+# encoding: UTF-8
+
+control 'V-254240' do
+  title "Windows Server 2019 administrative accounts must not be used with
+applications that access the Internet, such as web browsers, or with potential
+Internet sources, such as email."
+  desc  "Using applications that access the Internet or have potential Internet
+sources using administrative privileges exposes a system to compromise. If a
+flaw in an application is exploited while running as a privileged user, the
+entire system could be compromised. Web browsers and email are common attack
+vectors for introducing malicious code and must not be run with an
+administrative account.
+
+    Since administrative accounts may generally change or work around technical
+restrictions for running a web browser or other applications, it is essential
+that policy require administrative accounts to not access the Internet or use
+applications such as email.
+
+    The policy should define specific exceptions for local service
+administration. These exceptions may include HTTP(S)-based tools that are used
+for the administration of the local system, services, or attached devices.
+
+    Whitelisting can be used to enforce the policy to ensure compliance."
+  desc  "rationale", ""
+  desc  'check', "Determine whether organization policy, at a minimum, prohibits
+administrative accounts from using applications that access the Internet, such
+as web browsers, or with potential Internet sources, such as email, except as
+necessary for local service administration.
+
+    If it does not, this is a finding.
+
+    The organization may use technical means such as whitelisting to prevent
+the use of browsers and mail applications to enforce this requirement."
+  desc  'fix', "Establish a policy, at minimum, to prohibit administrative accounts from
+using applications that access the Internet, such as web browsers, or with
+potential Internet sources, such as email. Ensure the policy is enforced.
+
+    The organization may use technical means such as whitelisting to prevent
+the use of browsers and mail applications to enforce this requirement."
+  impact 0.7
+  tag 'severity': nil
+  tag 'gtitle': 'SRG-OS-000480-GPOS-00227'
+  tag 'gid': 'V-93205'
+  tag 'rid': 'SV-103293r1_rule'
+  tag 'stig_id': 'WN19-00-000030'
+  tag 'fix_id': 'F-99451r1_fix'
+  tag 'cci': ["CCI-000366"]
+  tag 'nist': ["CM-6 b", "Rev_4"]
+
+  describe "A manual review is required to verify that administrative accounts are not being used with applications that access the Internet, such as web browsers, or with potential Internet sources, such as email" do
+    skip "A manual review is required to verify that administrative accounts are not being used with applications that access the Internet, such as web browsers, or with potential Internet sources, such as email"
+  end
+end
+
diff --git a/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93207.rb b/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93207.rb
new file mode 100644
index 000000000..358c6ab71
--- /dev/null
+++ b/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93207.rb
@@ -0,0 +1,46 @@
+# encoding: UTF-8
+
+control 'V-254241' do
+  title "Windows Server 2019 members of the Backup Operators group must have
+separate accounts for backup duties and normal operational tasks."
+  desc  "Backup Operators are able to read and write to any file in the system,
+regardless of the rights assigned to it. Backup and restore rights permit users
+to circumvent the file access restrictions present on NTFS disk drives for
+backup and restore purposes. Members of the Backup Operators group must have
+separate logon accounts for performing backup duties."
+  desc  "rationale", ""
+  desc  'check', "If no accounts are members of the Backup Operators group, this is NA.
+
+    Verify users with accounts in the Backup Operators group have a separate
+user account for backup functions and for performing normal user tasks.
+
+    If users with accounts in the Backup Operators group do not have separate
+accounts for backup functions and standard user functions, this is a finding."
+  desc  'fix', "Ensure each member of the Backup Operators group has separate
+accounts for backup functions and standard user functions."
+  impact 0.5
+  tag 'severity': nil
+  tag 'gtitle': 'SRG-OS-000480-GPOS-00227'
+  tag 'gid': 'V-93207'
+  tag 'rid': 'SV-103295r1_rule'
+  tag 'stig_id': 'WN19-00-000040'
+  tag 'fix_id': 'F-99453r1_fix'
+  tag 'cci': ["CCI-000366"]
+  tag 'nist': ["CM-6 b", "Rev_4"]
+
+  backup_operators_group = command("net localgroup 'Backup Operators' | Format-List | Findstr /V 'Alias Name Comment Members - command'").stdout.strip.split("\r\n")
+  backup_operators = input('backup_operators')
+  if backup_operators_group.empty?
+    impact 0.0
+    describe 'Backup Operators Group Empty' do
+      skip 'The control is N/A as there are no users in the Backup Operators group'
+    end
+  else
+    backup_operators_group.each do |user|
+      describe user do
+        it { should be_in backup_operators }
+      end
+    end
+  end
+end
+
diff --git a/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93369.rb b/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93369.rb
new file mode 100644
index 000000000..89ed7ca03
--- /dev/null
+++ b/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93369.rb
@@ -0,0 +1,33 @@
+# encoding: UTF-8
+
+control 'V-254238' do
+  title "Windows Server 2019 users with Administrative privileges must have separate accounts for administrative duties and normal operational tasks."
+  desc  "Using a privileged account to perform routine functions makes the computer vulnerable to malicious software inadvertently introduced during a session that has been granted full privileges."
+  desc  "rationale", ""
+  desc  "check", "Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account.
+    If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding."
+  desc  "fix", "Ensure each user with administrative privileges has a separate account for user duties and one for privileged duties."
+  impact 0.7
+  tag severity: nil
+  tag gtitle: "SRG-OS-000480-GPOS-00227"
+  tag gid: "V-93369"
+  tag rid: "SV-103457r1_rule"
+  tag stig_id: "WN19-00-000010"
+  tag fix_id: "F-99615r1_fix"
+  tag cci: ["CCI-000366"]
+  tag nist: ["CM-6 b", "Rev_4"]
+
+  administrators = input('administrators')
+  administrator_group = command("net localgroup Administrators | Format-List | Findstr /V 'Alias Name Comment Members - command'").stdout.strip.split("\r\n")
+  administrator_group.each do |user|
+    describe user.to_s do
+      it { should be_in administrators }
+    end
+  end
+  if administrator_group.empty?
+    impact 0.0
+    describe 'There are no users with administrative privileges' do
+      skip 'There are no users with administrative privileges so this control is NA'
+    end
+  end
+end
\ No newline at end of file
diff --git a/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93461.rb b/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93461.rb
new file mode 100644
index 000000000..fe5b32b1a
--- /dev/null
+++ b/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93461.rb
@@ -0,0 +1,28 @@
+# encoding: UTF-8
+
+control 'V-254242' do
+  title "Windows Server 2019 manually managed application account passwords must be at least #{input('minimum_password_length_manual')} characters in length."
+  desc  "Application/service account passwords must be of sufficient length to prevent being easily cracked. Application/service accounts that are manually managed must have passwords at least #{input('minimum_password_length_manual')} characters in length."
+  desc  "rationale", ""
+  desc  "check", "Determine if manually managed application/service accounts exist. If none exist, this is NA.
+
+    Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least #{input('minimum_password_length_manual')} characters in length.
+
+    If such a policy does not exist or has not been implemented, this is a finding."
+  desc  "fix", "Establish a policy that requires application/service account passwords that are manually managed to be at least #{input('minimum_password_length_manual')} characters in length. Ensure the policy is enforced."
+  impact 0.5
+  tag severity: nil
+  tag gtitle: "SRG-OS-000078-GPOS-00046"
+  tag gid: "V-93461"
+  tag rid: "SV-103547r1_rule"
+  tag stig_id: "WN19-00-000050"
+  tag fix_id: "F-99705r1_fix"
+  tag cci: ["CCI-000205"]
+  tag nist: ["IA-5 (1) (a)", "Rev_4"]
+
+  mplm = input('minimum_password_length_manual')
+
+  describe 'Please Check all Accounts that are used for Services or Applications to validate they meet the Password Length Policy, Control is a Manual Check' do
+    skip "Determine if manually managed application/service accounts exist. If none exist, this is NA. Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least #{mplm} characters in length."
+  end
+end
diff --git a/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93473.rb b/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93473.rb
new file mode 100644
index 000000000..0b98b8426
--- /dev/null
+++ b/test/sample_data/inspec/json/profile_and_controls/mapped_controls/V-93473.rb
@@ -0,0 +1,60 @@
+# encoding: UTF-8
+
+control 'V-254239' do
+  title "Windows Server 2019 passwords for the built-in Administrator account must be changed at least every 60 days."
+  desc  "The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure.
+    Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every \"30\" days by default."
+  desc  "rationale", ""
+  desc  "check", "Review the password last set date for the built-in Administrator account.
+
+    Domain controllers:
+    Open \"PowerShell\".
+    Enter \"Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like \"*-500\" | Ft Name, SID, PasswordLastSet\".
+    If the \"PasswordLastSet\" date is greater than \"60\" days old, this is a finding.
+
+    Member servers and standalone systems:
+    Open \"Command Prompt\".
+    Enter 'Net User [account name] | Find /i \"Password Last Set\"', where [account name] is the name of the built-in administrator account.
+    (The name of the built-in Administrator account must be changed to something other than \"Administrator\" per STIG requirements.)
+    If the \"PasswordLastSet\" date is greater than \"60\" days old, this is a finding."
+  desc  "fix", "Change the built-in Administrator account password at least every \"60\" days.
+    Automated tools, such as Microsoft's LAPS, may be used on domain-joined member servers to accomplish this."
+  impact 0.5
+  tag severity: nil
+  tag gtitle: "SRG-OS-000076-GPOS-00044"
+  tag gid: "V-93473"
+  tag rid: "SV-103559r1_rule"
+  tag stig_id: "WN19-00-000020"
+  tag fix_id: "F-99717r1_fix"
+  tag cci: ["CCI-000199"]
+  tag nist: ["IA-5 (1) (d)", "Rev_4"]
+
+  administrator = input('local_administrator')
+  domain_role = command('wmic computersystem get domainrole | Findstr /v DomainRole').stdout.strip
+
+  if domain_role == '4' || domain_role == '5'
+    password_set_date = json({ command: "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where-Object {$_.SID -like '*-500' -and $_.PasswordLastSet -lt ((Get-Date).AddDays(-60))} | Select-Object -ExpandProperty PasswordLastSet | ConvertTo-Json" })
+    date = password_set_date["DateTime"]
+    describe "Password Last Set Date" do
+      it "The built-in Administrator account must be changed at least every 60 days." do
+        expect(date).to be_nil
+      end
+    end
+  else
+    if administrator == "Administrator"
+      describe 'The name of the built-in Administrator account:' do
+        it 'It must be changed to something other than "Administrator" per STIG requirements' do
+          failure_message = "Change the built-in Administrator account name to something other than: #{administrator}"
+          expect(administrator).not_to eq("Administrator"), failure_message
+        end
+      end
+    end
+    local_password_set_date = json({ command: "Get-LocalUser -name #{administrator} | Where-Object {$_.PasswordLastSet -le (Get-Date).AddDays(-60)} | Select-Object -ExpandProperty PasswordLastSet | ConvertTo-Json"})
+    local_date =  local_password_set_date["DateTime"]
+    describe "Password Last Set Date" do
+      it "The built-in Administrator account must be changed at least every 60 days." do
+        expect(local_date).to be_nil
+      end
+    end
+  end
+end
\ No newline at end of file
diff --git a/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93205.rb b/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93205.rb
new file mode 100644
index 000000000..5e33b6a72
--- /dev/null
+++ b/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93205.rb
@@ -0,0 +1,54 @@
+# encoding: UTF-8
+
+control "V-93205" do
+  title "Windows Server 2019 administrative accounts must not be used with
+applications that access the Internet, such as web browsers, or with potential
+Internet sources, such as email."
+  desc  "Using applications that access the Internet or have potential Internet
+sources using administrative privileges exposes a system to compromise. If a
+flaw in an application is exploited while running as a privileged user, the
+entire system could be compromised. Web browsers and email are common attack
+vectors for introducing malicious code and must not be run with an
+administrative account.
+
+    Since administrative accounts may generally change or work around technical
+restrictions for running a web browser or other applications, it is essential
+that policy require administrative accounts to not access the Internet or use
+applications such as email.
+
+    The policy should define specific exceptions for local service
+administration. These exceptions may include HTTP(S)-based tools that are used
+for the administration of the local system, services, or attached devices.
+
+    Whitelisting can be used to enforce the policy to ensure compliance."
+  desc  "rationale", ""
+  desc  'check', "Determine whether organization policy, at a minimum, prohibits
+administrative accounts from using applications that access the Internet, such
+as web browsers, or with potential Internet sources, such as email, except as
+necessary for local service administration.
+
+    If it does not, this is a finding.
+
+    The organization may use technical means such as whitelisting to prevent
+the use of browsers and mail applications to enforce this requirement."
+  desc  'fix', "Establish a policy, at minimum, to prohibit administrative accounts from
+using applications that access the Internet, such as web browsers, or with
+potential Internet sources, such as email. Ensure the policy is enforced.
+
+    The organization may use technical means such as whitelisting to prevent
+the use of browsers and mail applications to enforce this requirement."
+  impact 0.7
+  tag 'severity': nil
+  tag 'gtitle': 'SRG-OS-000480-GPOS-00227'
+  tag 'gid': 'V-93205'
+  tag 'rid': 'SV-103293r1_rule'
+  tag 'stig_id': 'WN19-00-000030'
+  tag 'fix_id': 'F-99451r1_fix'
+  tag 'cci': ["CCI-000366"]
+  tag 'nist': ["CM-6 b", "Rev_4"]
+
+  describe "A manual review is required to verify that administrative accounts are not being used with applications that access the Internet, such as web browsers, or with potential Internet sources, such as email" do
+    skip "A manual review is required to verify that administrative accounts are not being used with applications that access the Internet, such as web browsers, or with potential Internet sources, such as email"
+  end
+end
+
diff --git a/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93207.rb b/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93207.rb
new file mode 100644
index 000000000..51637ea7e
--- /dev/null
+++ b/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93207.rb
@@ -0,0 +1,46 @@
+# encoding: UTF-8
+
+control "V-93207" do
+  title "Windows Server 2019 members of the Backup Operators group must have
+separate accounts for backup duties and normal operational tasks."
+  desc  "Backup Operators are able to read and write to any file in the system,
+regardless of the rights assigned to it. Backup and restore rights permit users
+to circumvent the file access restrictions present on NTFS disk drives for
+backup and restore purposes. Members of the Backup Operators group must have
+separate logon accounts for performing backup duties."
+  desc  "rationale", ""
+  desc  'check', "If no accounts are members of the Backup Operators group, this is NA.
+
+    Verify users with accounts in the Backup Operators group have a separate
+user account for backup functions and for performing normal user tasks.
+
+    If users with accounts in the Backup Operators group do not have separate
+accounts for backup functions and standard user functions, this is a finding."
+  desc  'fix', "Ensure each member of the Backup Operators group has separate
+accounts for backup functions and standard user functions."
+  impact 0.5
+  tag 'severity': nil
+  tag 'gtitle': 'SRG-OS-000480-GPOS-00227'
+  tag 'gid': 'V-93207'
+  tag 'rid': 'SV-103295r1_rule'
+  tag 'stig_id': 'WN19-00-000040'
+  tag 'fix_id': 'F-99453r1_fix'
+  tag 'cci': ["CCI-000366"]
+  tag 'nist': ["CM-6 b", "Rev_4"]
+
+  backup_operators_group = command("net localgroup 'Backup Operators' | Format-List | Findstr /V 'Alias Name Comment Members - command'").stdout.strip.split("\r\n")
+  backup_operators = input('backup_operators')
+  if backup_operators_group.empty?
+    impact 0.0
+    describe 'Backup Operators Group Empty' do
+      skip 'The control is N/A as there are no users in the Backup Operators group'
+    end
+  else
+    backup_operators_group.each do |user|
+      describe user do
+        it { should be_in backup_operators }
+      end
+    end
+  end
+end
+
diff --git a/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93369.rb b/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93369.rb
new file mode 100644
index 000000000..34a9df325
--- /dev/null
+++ b/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93369.rb
@@ -0,0 +1,33 @@
+# encoding: UTF-8
+
+control "V-93369" do
+  title "Windows Server 2019 users with Administrative privileges must have separate accounts for administrative duties and normal operational tasks."
+  desc  "Using a privileged account to perform routine functions makes the computer vulnerable to malicious software inadvertently introduced during a session that has been granted full privileges."
+  desc  "rationale", ""
+  desc  "check", "Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account.
+    If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding."
+  desc  "fix", "Ensure each user with administrative privileges has a separate account for user duties and one for privileged duties."
+  impact 0.7
+  tag severity: nil
+  tag gtitle: "SRG-OS-000480-GPOS-00227"
+  tag gid: "V-93369"
+  tag rid: "SV-103457r1_rule"
+  tag stig_id: "WN19-00-000010"
+  tag fix_id: "F-99615r1_fix"
+  tag cci: ["CCI-000366"]
+  tag nist: ["CM-6 b", "Rev_4"]
+
+  administrators = input('administrators')
+  administrator_group = command("net localgroup Administrators | Format-List | Findstr /V 'Alias Name Comment Members - command'").stdout.strip.split("\r\n")
+  administrator_group.each do |user|
+    describe user.to_s do
+      it { should be_in administrators }
+    end
+  end
+  if administrator_group.empty?
+    impact 0.0
+    describe 'There are no users with administrative privileges' do
+      skip 'There are no users with administrative privileges so this control is NA'
+    end
+  end
+end
\ No newline at end of file
diff --git a/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93461.rb b/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93461.rb
new file mode 100644
index 000000000..acad7519f
--- /dev/null
+++ b/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93461.rb
@@ -0,0 +1,28 @@
+# encoding: UTF-8
+
+control "V-93461" do
+  title "Windows Server 2019 manually managed application account passwords must be at least #{input('minimum_password_length_manual')} characters in length."
+  desc  "Application/service account passwords must be of sufficient length to prevent being easily cracked. Application/service accounts that are manually managed must have passwords at least #{input('minimum_password_length_manual')} characters in length."
+  desc  "rationale", ""
+  desc  "check", "Determine if manually managed application/service accounts exist. If none exist, this is NA.
+
+    Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least #{input('minimum_password_length_manual')} characters in length.
+
+    If such a policy does not exist or has not been implemented, this is a finding."
+  desc  "fix", "Establish a policy that requires application/service account passwords that are manually managed to be at least #{input('minimum_password_length_manual')} characters in length. Ensure the policy is enforced."
+  impact 0.5
+  tag severity: nil
+  tag gtitle: "SRG-OS-000078-GPOS-00046"
+  tag gid: "V-93461"
+  tag rid: "SV-103547r1_rule"
+  tag stig_id: "WN19-00-000050"
+  tag fix_id: "F-99705r1_fix"
+  tag cci: ["CCI-000205"]
+  tag nist: ["IA-5 (1) (a)", "Rev_4"]
+
+  mplm = input('minimum_password_length_manual')
+
+  describe 'Please Check all Accounts that are used for Services or Applications to validate they meet the Password Length Policy, Control is a Manual Check' do
+    skip "Determine if manually managed application/service accounts exist. If none exist, this is NA. Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least #{mplm} characters in length."
+  end
+end
diff --git a/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93473.rb b/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93473.rb
new file mode 100644
index 000000000..b96812989
--- /dev/null
+++ b/test/sample_data/inspec/json/profile_and_controls/windows_server_2022_v1r3_mini_controls/V-93473.rb
@@ -0,0 +1,60 @@
+# encoding: UTF-8
+
+control "V-93473" do
+  title "Windows Server 2019 passwords for the built-in Administrator account must be changed at least every 60 days."
+  desc  "The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password not may be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure.
+    Organizations that use an automated tool, such Microsoft's Local Administrator Password Solution (LAPS), on domain-joined systems can configure this to occur more frequently. LAPS will change the password every \"30\" days by default."
+  desc  "rationale", ""
+  desc  "check", "Review the password last set date for the built-in Administrator account.
+
+    Domain controllers:
+    Open \"PowerShell\".
+    Enter \"Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where SID -Like \"*-500\" | Ft Name, SID, PasswordLastSet\".
+    If the \"PasswordLastSet\" date is greater than \"60\" days old, this is a finding.
+
+    Member servers and standalone systems:
+    Open \"Command Prompt\".
+    Enter 'Net User [account name] | Find /i \"Password Last Set\"', where [account name] is the name of the built-in administrator account.
+    (The name of the built-in Administrator account must be changed to something other than \"Administrator\" per STIG requirements.)
+    If the \"PasswordLastSet\" date is greater than \"60\" days old, this is a finding."
+  desc  "fix", "Change the built-in Administrator account password at least every \"60\" days.
+    Automated tools, such as Microsoft's LAPS, may be used on domain-joined member servers to accomplish this."
+  impact 0.5
+  tag severity: nil
+  tag gtitle: "SRG-OS-000076-GPOS-00044"
+  tag gid: "V-93473"
+  tag rid: "SV-103559r1_rule"
+  tag stig_id: "WN19-00-000020"
+  tag fix_id: "F-99717r1_fix"
+  tag cci: ["CCI-000199"]
+  tag nist: ["IA-5 (1) (d)", "Rev_4"]
+
+  administrator = input('local_administrator')
+  domain_role = command('wmic computersystem get domainrole | Findstr /v DomainRole').stdout.strip
+
+  if domain_role == '4' || domain_role == '5'
+    password_set_date = json({ command: "Get-ADUser -Filter * -Properties SID, PasswordLastSet | Where-Object {$_.SID -like '*-500' -and $_.PasswordLastSet -lt ((Get-Date).AddDays(-60))} | Select-Object -ExpandProperty PasswordLastSet | ConvertTo-Json" })
+    date = password_set_date["DateTime"]
+    describe "Password Last Set Date" do
+      it "The built-in Administrator account must be changed at least every 60 days." do
+        expect(date).to be_nil
+      end
+    end
+  else
+    if administrator == "Administrator"
+      describe 'The name of the built-in Administrator account:' do
+        it 'It must be changed to something other than "Administrator" per STIG requirements' do
+          failure_message = "Change the built-in Administrator account name to something other than: #{administrator}"
+          expect(administrator).not_to eq("Administrator"), failure_message
+        end
+      end
+    end
+    local_password_set_date = json({ command: "Get-LocalUser -name #{administrator} | Where-Object {$_.PasswordLastSet -le (Get-Date).AddDays(-60)} | Select-Object -ExpandProperty PasswordLastSet | ConvertTo-Json"})
+    local_date =  local_password_set_date["DateTime"]
+    describe "Password Last Set Date" do
+      it "The built-in Administrator account must be changed at least every 60 days." do
+        expect(local_date).to be_nil
+      end
+    end
+  end
+end
\ No newline at end of file
diff --git a/test/sample_data/xccdf/stigs/FULL_Windows_Server_2022_V2R1_mini-sample-xccdf.xml b/test/sample_data/xccdf/stigs/FULL_Windows_Server_2022_V2R1_mini-sample-xccdf.xml
new file mode 100644
index 000000000..6a41de718
--- /dev/null
+++ b/test/sample_data/xccdf/stigs/FULL_Windows_Server_2022_V2R1_mini-sample-xccdf.xml
@@ -0,0 +1,11838 @@
+<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type='text/xsl' href='STIG_unclass.xsl'?>
+<Benchmark xmlns:dc="http://purl.org/dc/elements/1.1/"
+    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    xmlns:cpe="http://cpe.mitre.org/language/2.0"
+    xmlns:xhtml="http://www.w3.org/1999/xhtml"
+    xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/schema/xccdf-1.1.4.xsd http://cpe.mitre.org/dictionary/2.0 http://cpe.mitre.org/files/cpe-dictionary_2.1.xsd" id="MS_Windows_Server_2022_STIG" xml:lang="en"
+    xmlns="http://checklists.nist.gov/xccdf/1.1">
+    <status date="2024-06-14">accepted</status>
+    <title>Microsoft Windows Server 2022 Security Technical Implementation Guide</title>
+    <description>This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.</description>
+    <notice id="terms-of-use" xml:lang="en"></notice>
+    <front-matter xml:lang="en"></front-matter>
+    <rear-matter xml:lang="en"></rear-matter>
+    <reference href="https://cyber.mil">
+        <dc:publisher>DISA</dc:publisher>
+        <dc:source>STIG.DOD.MIL</dc:source>
+    </reference>
+    <plain-text id="release-info">Release: 1 Benchmark Date: 24 Jul 2024</plain-text>
+    <plain-text id="generator">3.5</plain-text>
+    <plain-text id="conventionsVersion">1.10.0</plain-text>
+    <version>2</version>
+    <Group id="V-254238">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254238r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000010</version>
+            <title>Windows Server 2022 users with Administrative privileges must have separate accounts for administrative duties and normal operational tasks.</title>
+            <description>&lt;VulnDiscussion&gt;Using a privileged account to perform routine functions makes the computer vulnerable to malicious software inadvertently introduced during a session that has been granted full 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57674r848529_fix">Ensure each user with administrative privileges has a separate account for user duties and one for privileged duties.</fixtext>
+            <fix id="F-57674r848529_fix" />
+            <check system="C-57723r848528_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account. 
+
+If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254239">
+        <title>SRG-OS-000076-GPOS-00044</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254239r1000150_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000020</version>
+            <title>Windows Server 2022 passwords for the built-in Administrator account must be changed at least every 60 days.</title>
+            <description>&lt;VulnDiscussion&gt;The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password may not be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure.
+
+Windows LAPS must be used to change the built-in Administrator account 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004066</ident>
+            <fixtext fixref="F-57675r951094_fix">Change the enabled local Administrator account password at least every 60 days. Windows LAPS must be used to change the built-in Administrator account password. Domain-joined systems can configure this to occur more frequently. LAPS will change the password every 30 days by default. 
+
+More information is available at:
+https://techcommunity.microsoft.com/t5/windows-it-pro-blog/by-popular-demand-windows-laps-available-now/ba-p/3788747
+https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-overview#windows-laps-supported-platforms-and-azure-ad-laps-preview-status</fixtext>
+            <fix id="F-57675r951094_fix" />
+            <check system="C-57724r951093_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If there are no enabled local Administrator accounts, this is Not Applicable.
+
+Review the password last set date for the enabled local Administrator account.
+
+On the stand alone or domain-joined workstation:
+
+Open "PowerShell".
+
+Enter "Get-LocalUser -Name * | Select-Object *".
+
+If the "PasswordLastSet" date is greater than "60" days old for the local Administrator account for administering the computer/domain, this is a finding.
+
+Verify LAPS is configured and operational. 
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; LAPS &gt;&gt; Password Settings &gt;&gt; Set to enabled. Password Complexity, large letters + small letters + numbers + special, Password Length 14, Password Age 60. If not configured as shown, this is a finding. 
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; LAPS &gt;&gt; Password Settings &gt;&gt; Name of administrator Account to manage &gt;&gt; Set to enabled &gt;&gt; Administrator account name is populated. If it is not, this is a finding. 
+
+Verify LAPS Operational logs &gt;&gt; Event Viewer &gt;&gt; Applications and Services Logs &gt;&gt; Microsoft &gt;&gt; Windows &gt;&gt; LAPS &gt;&gt; Operational. Verify LAPS policy process is completing. If it is not, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254240">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254240r991589_rule" weight="10.0" severity="high">
+            <version>WN22-00-000030</version>
+            <title>Windows Server 2022 administrative accounts must not be used with applications that access the internet, such as web browsers, or with potential internet sources, such as email.</title>
+            <description>&lt;VulnDiscussion&gt;Using applications that access the internet or have potential internet sources using administrative privileges exposes a system to compromise. If a flaw in an application is exploited while running as a privileged user, the entire system could be compromised. Web browsers and email are common attack vectors for introducing malicious code and must not be run with an administrative account.
+
+Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy require administrative accounts to not access the internet or use applications such as email.
+
+The policy must define specific exceptions for local service administration. These exceptions may include HTTP(S)-based tools that are used for the administration of the local system, services, or attached devices.
+
+Whitelisting can be used to enforce the policy to ensure compliance.
+
+Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000205-GPOS-00083&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <ident system="http://cyber.mil/cci">CCI-001312</ident>
+            <fixtext fixref="F-57676r848535_fix">Establish a policy, at minimum, to prohibit administrative accounts from using applications that access the internet, such as web browsers, or with potential internet sources, such as email. Ensure the policy is enforced.
+
+The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement.</fixtext>
+            <fix id="F-57676r848535_fix" />
+            <check system="C-57725r848534_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Determine whether organization policy, at a minimum, prohibits administrative accounts from using applications that access the internet, such as web browsers, or with potential internet sources, such as email, except as necessary for local service administration.
+
+If it does not, this is a finding.
+
+The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254241">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254241r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000040</version>
+            <title>Windows Server 2022 members of the Backup Operators group must have separate accounts for backup duties and normal operational tasks.</title>
+            <description>&lt;VulnDiscussion&gt;Backup Operators are able to read and write to any file in the system, regardless of the rights assigned to it. Backup and restore rights permit users to circumvent the file access restrictions present on NTFS disk drives for backup and restore purposes. Members of the Backup Operators group must have separate logon accounts for performing backup duties.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57677r848538_fix">Ensure each member of the Backup Operators group has separate accounts for backup functions and standard user functions.</fixtext>
+            <fix id="F-57677r848538_fix" />
+            <check system="C-57726r848537_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If no accounts are members of the Backup Operators group, this is NA.
+
+Verify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks.
+
+If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254242">
+        <title>SRG-OS-000078-GPOS-00046</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254242r1000151_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000050</version>
+            <title>Windows Server 2022 manually managed application account passwords must be at least 14 characters in length.</title>
+            <description>&lt;VulnDiscussion&gt;Application/service account passwords must be of sufficient length to prevent being easily cracked. Application/service accounts that are manually managed must have passwords at least 14 characters in length.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004066</ident>
+            <fixtext fixref="F-57678r951097_fix">Establish a policy that requires application/service account passwords that are manually managed to be at least 14 characters in length. Ensure the policy is enforced.</fixtext>
+            <fix id="F-57678r951097_fix" />
+            <check system="C-57727r951096_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Determine if manually managed application/service accounts exist. If none exist, this is NA.
+
+Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least 14 characters in length.
+
+If such a policy does not exist or has not been implemented, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254243">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254243r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000060</version>
+            <title>Windows Server 2022 manually managed application account passwords must be changed at least annually or when a system administrator with knowledge of the password leaves the organization.</title>
+            <description>&lt;VulnDiscussion&gt;Setting application account passwords to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. If managed service accounts are used, this alleviates the need to manually change application account passwords.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57679r848544_fix">Change passwords for manually managed application/service accounts at least annually or when an administrator with knowledge of the password leaves the organization.
+
+It is recommended that system-managed service accounts be used whenever possible.</fixtext>
+            <fix id="F-57679r848544_fix" />
+            <check system="C-57728r848543_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Determine if manually managed application/service accounts exist. If none exist, this is NA.
+
+If passwords for manually managed application/service accounts are not changed at least annually or when an administrator with knowledge of the password leaves the organization, this is a finding.
+
+Identify manually managed application/service accounts.
+
+To determine the date a password was last changed:
+
+Domain controllers:
+
+Open "PowerShell".
+
+Enter "Get-AdUser -Identity [application account name] -Properties PasswordLastSet | FT Name, PasswordLastSet", where [application account name] is the name of the manually managed application/service account.
+
+If the "PasswordLastSet" date is more than one year old, this is a finding.
+
+Member servers and standalone or nondomain-joined systems:
+
+Open "Command Prompt".
+
+Enter 'Net User [application account name] | Find /i "Password Last Set"', where [application account name] is the name of the manually managed application/service account.
+
+If the "Password Last Set" date is more than one year old, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254244">
+        <title>SRG-OS-000104-GPOS-00051</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254244r958482_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000070</version>
+            <title>Windows Server 2022 shared user accounts must not be permitted.</title>
+            <description>&lt;VulnDiscussion&gt;Shared accounts (accounts where two or more people log on with the same user identification) do not provide adequate identification and authentication. There is no way to provide for nonrepudiation or individual accountability for system access and resource usage.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000764</ident>
+            <fixtext fixref="F-57680r848547_fix">Remove unapproved shared accounts from the system.
+
+Document required shared accounts with the ISSO. Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity.</fixtext>
+            <fix id="F-57680r848547_fix" />
+            <check system="C-57729r848546_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Determine whether any shared accounts exist. If no shared accounts exist, this is NA.
+
+Shared accounts, such as required by an application, may be approved by the organization. This must be documented with the Information System Security Officer (ISSO). Documentation must include the reason for the account, who has access to the account, and how the risk of using the shared account is mitigated to include monitoring account activity.
+
+If unapproved shared accounts exist, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254245">
+        <title>SRG-OS-000370-GPOS-00155</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254245r958808_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000080</version>
+            <title>Windows Server 2022 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.</title>
+            <description>&lt;VulnDiscussion&gt;Using an allowlist provides a configuration management method to allow the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities.
+
+The organization must identify authorized software programs and only permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as allowlisting.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001774</ident>
+            <fixtext fixref="F-57681r890535_fix">Configure an application allowlisting program to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.
+
+Configuration of allowlisting applications will vary by the program. AppLocker is an allowlisting application built in to Windows Server.
+
+If AppLocker is used, it is configured through group policy in Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Application Control Policies &gt;&gt; AppLocker.
+
+Implementation guidance for AppLocker is available at the following link:
+
+https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-application-control/applocker/applocker-policies-deployment-guide</fixtext>
+            <fix id="F-57681r890535_fix" />
+            <check system="C-57730r890534_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the operating system employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs.
+
+If an application allowlisting program is not in use on the system, this is a finding.
+
+Configuration of allowlisting applications will vary by the program.
+
+AppLocker is an allowlisting application built in to Windows Server. A deny-by-default implementation is initiated by enabling any AppLocker rules within a category, only allowing what is specified by defined rules.
+
+If AppLocker is used, perform the following to view the configuration of AppLocker:
+
+Open "PowerShell".
+
+If the AppLocker PowerShell module has not been imported previously, execute the following first:
+
+Import-Module AppLocker
+
+Execute the following command, substituting [c:\temp\file.xml] with a location and file name appropriate for the system:
+
+Get-AppLockerPolicy -Effective -XML &gt; c:\temp\file.xml
+
+This will produce an xml file with the effective settings that can be viewed in a browser or opened in a program such as Excel for review.
+
+Implementation guidance for AppLocker is available at the following link:
+
+https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-application-control/applocker/applocker-policies-deployment-guide</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254246">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254246r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000090</version>
+            <title>Windows Server 2022 domain-joined systems must have a Trusted Platform Module (TPM) enabled and ready for use.</title>
+            <description>&lt;VulnDiscussion&gt;Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. A number of system requirements must be met in order for Credential Guard to be configured and enabled properly. Without a TPM enabled and ready for use, Credential Guard keys are stored in a less secure method using 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57682r848553_fix">Ensure domain-joined systems have a TPM that is configured for use. (Versions 2.0 or 1.2 support Credential Guard.)
+
+The TPM must be enabled in the firmware.
+
+Run "tpm.msc" for configuration options in Windows.</fixtext>
+            <fix id="F-57682r848553_fix" />
+            <check system="C-57731r848552_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>For standalone or nondomain-joined systems, this is NA.
+
+Verify the system has a TPM and it is ready for use.
+
+Run "tpm.msc".
+
+Review the sections in the center pane.
+
+"Status" must indicate it has been configured with a message such as "The TPM is ready for use" or "The TPM is on and ownership has been taken".
+
+TPM Manufacturer Information - Specific Version = 2.0 or 1.2
+
+If a TPM is not found or is not ready for use, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254247">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254247r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000100</version>
+            <title>Windows Server 2022 must be maintained at a supported servicing level.</title>
+            <description>&lt;VulnDiscussion&gt;Systems at unsupported servicing levels will not receive security updates for new vulnerabilities, which leave them subject to exploitation. Systems must be maintained at a servicing level supported by the vendor with new security updates.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57683r848556_fix">Update the system to a Version 21H2 (Build 20348.xxx) or greater.</fixtext>
+            <fix id="F-57683r848556_fix" />
+            <check system="C-57732r848555_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Open "Command Prompt".
+
+Enter "winver.exe".
+
+If the "About Windows" dialog box does not display "Microsoft Windows Server Version 21H1 (Build 20348.xxx)" or greater, this is a finding.
+
+Preview versions must not be used in a production environment.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254248">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254248r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000110</version>
+            <title>Windows Server 2022 must use an antivirus program.</title>
+            <description>&lt;VulnDiscussion&gt;Malicious software can establish a base on individual desktops and servers. Employing an automated mechanism to detect this type of software will aid in elimination of the software from the operating system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57684r848559_fix">If no antivirus software is in use, install Microsoft Defender or third-party antivirus.
+
+Open "PowerShell".
+
+Enter "Install-WindowsFeature -Name Windows-Defender".
+
+For third-party antivirus, install per antivirus instructions and disable Windows Defender.
+
+Open "PowerShell".
+
+Enter "Uninstall-WindowsFeature -Name Windows-Defender".</fixtext>
+            <fix id="F-57684r848559_fix" />
+            <check system="C-57733r848558_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify an antivirus solution is installed on the system. The antivirus solution may be bundled with an approved host-based security solution.
+
+If there is no antivirus solution installed on the system, this is a finding.
+
+Verify if Microsoft Defender antivirus is in use or enabled:
+
+Open "PowerShell".
+
+Enter "get-service | where {$_.DisplayName -Like "*Defender*"} | Select Status,DisplayName"
+
+Verify if third-party antivirus is in use or enabled:
+
+Open "PowerShell".
+
+Enter "get-service | where {$_.DisplayName -Like "*mcafee*"} | Select Status,DisplayName
+
+Enter "get-service | where {$_.DisplayName -Like "*symantec*"} | Select Status,DisplayName</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254249">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254249r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000120</version>
+            <title>Windows Server 2022 must have a host-based intrusion detection or prevention system.</title>
+            <description>&lt;VulnDiscussion&gt;A properly configured Host-based Intrusion Detection System (HIDS) or Host-based Intrusion Prevention System (HIPS) provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57685r848562_fix">Install a HIDS or HIPS on each server.</fixtext>
+            <fix id="F-57685r848562_fix" />
+            <check system="C-57734r848561_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Determine whether there is a HIDS or HIPS on each server. 
+
+If the HIPS component of ESS is installed and active on the host and the alerts of blocked activity are being logged and monitored, this meets the requirement. 
+
+A HIDS device is not required on a system that has the role as the Network Intrusion Device (NID). However, this exception needs to be documented with the Information System Security Officer (ISSO).
+
+If a HIDS is not installed on the system, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254250">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254250r958472_rule" weight="10.0" severity="high">
+            <version>WN22-00-000130</version>
+            <title>Windows Server 2022 local volumes must use a format that supports NTFS attributes.</title>
+            <description>&lt;VulnDiscussion&gt;The ability to set access permissions and auditing is critical to maintaining the security and proper access controls of a system. To support this, volumes must be formatted using a file system that supports NTFS attributes.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57686r848565_fix">Format volumes to use NTFS or ReFS.</fixtext>
+            <fix id="F-57686r848565_fix" />
+            <check system="C-57735r848564_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Open "Computer Management".
+
+Select "Disk Management" under "Storage".
+
+For each local volume, if the file system does not indicate "NTFS", this is a finding.
+
+"ReFS" (resilient file system) is also acceptable and would not be a finding.
+
+This does not apply to system partitions such the Recovery and EFI System Partition.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254251">
+        <title>SRG-OS-000312-GPOS-00122</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254251r958702_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000140</version>
+            <title>Windows Server 2022 permissions for the system drive root directory (usually C:\) must conform to minimum requirements.</title>
+            <description>&lt;VulnDiscussion&gt;Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications.
+
+The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN22-SO-000240).
+
+Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002165</ident>
+            <fixtext fixref="F-57687r848568_fix">Maintain the default permissions for the system drive's root directory and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN22-SO-000240).
+
+Default Permissions
+C:\
+Type - "Allow" for all
+Inherited from - "None" for all
+
+Principal - Access - Applies to
+
+SYSTEM - Full control - This folder, subfolders, and files
+Administrators - Full control - This folder, subfolders, and files
+Users - Read &amp; execute - This folder, subfolders, and files
+Users - Create folders/append data - This folder and subfolders
+Users - Create files/write data - Subfolders only
+CREATOR OWNER - Full Control - Subfolders and files only</fixtext>
+            <fix id="F-57687r848568_fix" />
+            <check system="C-57736r848567_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN22-SO-000240).
+
+Review the permissions for the system drive's root directory (usually C:\). Nonprivileged groups such as Users or Authenticated Users must not have greater than "Read &amp; execute" permissions except where noted as defaults. Individual accounts must not be used to assign permissions.
+
+If permissions are not as restrictive as the default permissions listed below, this is a finding.
+
+Viewing in File Explorer:
+
+View the Properties of the system drive's root directory.
+
+Select the "Security" tab, and the "Advanced" button.
+
+Default permissions:
+C:\
+Type - "Allow" for all
+Inherited from - "None" for all
+
+Principal - Access - Applies to
+
+SYSTEM - Full control - This folder, subfolders, and files
+Administrators - Full control - This folder, subfolders, and files
+Users - Read &amp; execute - This folder, subfolders, and files
+Users - Create folders/append data - This folder and subfolders
+Users - Create files/write data - Subfolders only
+CREATOR OWNER - Full Control - Subfolders and files only
+
+Alternately, use icacls:
+
+Open "Command Prompt (Admin)".
+
+Enter "icacls" followed by the directory:
+
+"icacls c:\"
+
+The following results must be displayed:
+
+c:\
+NT AUTHORITY\SYSTEM:(OI)(CI)(F)
+BUILTIN\Administrators:(OI)(CI)(F)
+BUILTIN\Users:(OI)(CI)(RX)
+BUILTIN\Users:(CI)(AD)
+BUILTIN\Users:(CI)(IO)(WD)
+CREATOR OWNER:(OI)(CI)(IO)(F)
+Successfully processed 1 files; Failed processing 0 files</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254252">
+        <title>SRG-OS-000312-GPOS-00122</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254252r958702_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000150</version>
+            <title>Windows Server 2022 permissions for program file directories must conform to minimum requirements.</title>
+            <description>&lt;VulnDiscussion&gt;Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications.
+
+The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN22-SO-000240).
+
+Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002165</ident>
+            <fixtext fixref="F-57688r848571_fix">Maintain the default permissions for the program file directories and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN22-SO-000240).
+
+Default permissions:
+\Program Files and \Program Files (x86)
+Type - "Allow" for all
+Inherited from - "None" for all
+
+Principal - Access - Applies to
+
+TrustedInstaller - Full control - This folder and subfolders
+SYSTEM - Modify - This folder only
+SYSTEM - Full control - Subfolders and files only
+Administrators - Modify - This folder only
+Administrators - Full control - Subfolders and files only
+Users - Read &amp; execute - This folder, subfolders, and files
+CREATOR OWNER - Full control - Subfolders and files only
+ALL APPLICATION PACKAGES - Read &amp; execute - This folder, subfolders, and files
+ALL RESTRICTED APPLICATION PACKAGES - Read &amp; execute - This folder, subfolders, and files</fixtext>
+            <fix id="F-57688r848571_fix" />
+            <check system="C-57737r848570_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN22-SO-000240).
+
+Review the permissions for the program file directories (Program Files and Program Files [x86]). Nonprivileged groups such as Users or Authenticated Users must not have greater than "Read &amp; execute" permissions. Individual accounts must not be used to assign permissions.
+
+If permissions are not as restrictive as the default permissions listed below, this is a finding.
+
+Viewing in File Explorer:
+
+For each folder, view the Properties.
+
+Select the "Security" tab, and the "Advanced" button.
+
+Default permissions:
+\Program Files and \Program Files (x86)
+Type - "Allow" for all
+Inherited from - "None" for all
+
+Principal - Access - Applies to
+
+TrustedInstaller - Full control - This folder and subfolders
+SYSTEM - Modify - This folder only
+SYSTEM - Full control - Subfolders and files only
+Administrators - Modify - This folder only
+Administrators - Full control - Subfolders and files only
+Users - Read &amp; execute - This folder, subfolders and files
+CREATOR OWNER - Full control - Subfolders and files only
+ALL APPLICATION PACKAGES - Read &amp; execute - This folder, subfolders, and files
+ALL RESTRICTED APPLICATION PACKAGES - Read &amp; execute - This folder, subfolders, and files
+
+Alternately, use icacls:
+
+Open a Command prompt (admin).
+
+Enter "icacls" followed by the directory:
+
+'icacls "c:\program files"'
+'icacls "c:\program files (x86)"'
+
+The following results must be displayed for each when entered:
+
+c:\program files (c:\program files (x86))
+NT SERVICE\TrustedInstaller:(F)
+NT SERVICE\TrustedInstaller:(CI)(IO)(F)
+NT AUTHORITY\SYSTEM:(M)
+NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
+BUILTIN\Administrators:(M)
+BUILTIN\Administrators:(OI)(CI)(IO)(F)
+BUILTIN\Users:(RX)
+BUILTIN\Users:(OI)(CI)(IO)(GR,GE)
+CREATOR OWNER:(OI)(CI)(IO)(F)
+APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(RX)
+APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)
+APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX)
+APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)
+Successfully processed 1 files; Failed processing 0 files</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254253">
+        <title>SRG-OS-000312-GPOS-00122</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254253r958702_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000160</version>
+            <title>Windows Server 2022 permissions for the Windows installation directory must conform to minimum requirements.</title>
+            <description>&lt;VulnDiscussion&gt;Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications.
+
+The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN22-SO-000240).
+
+Satisfies: SRG-OS-000312-GPOS-00122, SRG-OS-000312-GPOS-00123, SRG-OS-000312-GPOS-00124&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002165</ident>
+            <fixtext fixref="F-57689r848574_fix">Maintain the default file ACLs and configure the Security Option "Network access: Let Everyone permissions apply to anonymous users" to "Disabled" (WN22-SO-000240).
+
+Default permissions:
+Type - "Allow" for all
+Inherited from - "None" for all
+
+Principal - Access - Applies to
+
+TrustedInstaller - Full control - This folder and subfolders
+SYSTEM - Modify - This folder only
+SYSTEM - Full control - Subfolders and files only
+Administrators - Modify - This folder only
+Administrators - Full control - Subfolders and files only
+Users - Read &amp; execute - This folder, subfolders, and files
+CREATOR OWNER - Full control - Subfolders and files only
+ALL APPLICATION PACKAGES - Read &amp; execute - This folder, subfolders, and files
+ALL RESTRICTED APPLICATION PACKAGES - Read &amp; execute - This folder, subfolders, and files</fixtext>
+            <fix id="F-57689r848574_fix" />
+            <check system="C-57738r848573_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>The default permissions are adequate when the Security Option "Network access: Let Everyone permissions apply to anonymous users" is set to "Disabled" (WN22-SO-000240).
+
+Review the permissions for the Windows installation directory (usually C:\Windows). Nonprivileged groups such as Users or Authenticated Users must not have greater than "Read &amp; execute" permissions. Individual accounts must not be used to assign permissions.
+
+If permissions are not as restrictive as the default permissions listed below, this is a finding:
+
+Viewing in File Explorer:
+
+For each folder, view the Properties.
+
+Select the "Security" tab and the "Advanced" button.
+
+Default permissions:
+\Windows
+Type - "Allow" for all
+Inherited from - "None" for all
+
+Principal - Access - Applies to
+
+TrustedInstaller - Full control - This folder and subfolders
+SYSTEM - Modify - This folder only
+SYSTEM - Full control - Subfolders and files only
+Administrators - Modify - This folder only
+Administrators - Full control - Subfolders and files only
+Users - Read &amp; execute - This folder, subfolders, and files
+CREATOR OWNER - Full control - Subfolders and files only
+ALL APPLICATION PACKAGES - Read &amp; execute - This folder, subfolders, and files
+ALL RESTRICTED APPLICATION PACKAGES - Read &amp; execute - This folder, subfolders, and files
+
+Alternately, use icacls:
+
+Open a Command prompt (admin).
+
+Enter "icacls" followed by the directory:
+
+"icacls c:\windows"
+
+The following results must be displayed for each when entered:
+
+c:\windows
+NT SERVICE\TrustedInstaller:(F)
+NT SERVICE\TrustedInstaller:(CI)(IO)(F)
+NT AUTHORITY\SYSTEM:(M)
+NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
+BUILTIN\Administrators:(M)
+BUILTIN\Administrators:(OI)(CI)(IO)(F)
+BUILTIN\Users:(RX)
+BUILTIN\Users:(OI)(CI)(IO)(GR,GE)
+CREATOR OWNER:(OI)(CI)(IO)(F)
+APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(RX)
+APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)
+APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX)
+APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)
+Successfully processed 1 files; Failed processing 0 files</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254254">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254254r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000170</version>
+            <title>Windows Server 2022 default permissions for the HKEY_LOCAL_MACHINE registry hive must be maintained.</title>
+            <description>&lt;VulnDiscussion&gt;The registry is integral to the function, security, and stability of the Windows system. Changing the system's registry permissions allows the possibility of unauthorized and anonymous modification to the operating system.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57690r951100_fix">Maintain the default permissions for the HKEY_LOCAL_MACHINE registry hive.
+
+The default permissions of the higher-level keys are noted below.
+
+HKEY_LOCAL_MACHINE\SECURITY
+
+Type - "Allow" for all
+Inherited from - "None" for all
+Principal - Access - Applies to
+SYSTEM - Full Control - This key and subkeys
+Administrators - Special - This key and subkeys
+
+HKEY_LOCAL_MACHINE\SOFTWARE
+
+Type - "Allow" for all
+Inherited from - "None" for all
+Principal - Access - Applies to
+Users - Read - This key and subkeys
+Administrators - Full Control - This key and subkeys
+SYSTEM - Full Control - This key and subkeys
+CREATOR OWNER - Full Control - This key and subkeys
+ALL APPLICATION PACKAGES - Read - This key and subkeys
+
+HKEY_LOCAL_MACHINE\SYSTEM
+
+Type - "Allow" for all
+Inherited from - "None" for all
+Principal - Access - Applies to
+Users - Read - This key and subkeys
+Administrators - Full Control - This key and subkeys
+SYSTEM - Full Control - This key and subkeys
+CREATOR OWNER - Full Control - This key and subkeys
+ALL APPLICATION PACKAGES - Read - This key and subkeys
+Server Operators - Read - This Key and subkeys (Domain controllers only)
+
+Microsoft has also given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2022 to the following SID:
+S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681</fixtext>
+            <fix id="F-57690r951100_fix" />
+            <check system="C-57739r951099_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Review the registry permissions for the keys of the HKEY_LOCAL_MACHINE hive noted below.
+
+If any nonprivileged groups such as Everyone, Users, or Authenticated Users have greater than Read permission, this is a finding.
+
+If permissions are not as restrictive as the default permissions listed below, this is a finding:
+
+Run "Regedit".
+
+Right-click on the registry areas noted below.
+
+Select "Permissions" and the "Advanced" button.
+
+HKEY_LOCAL_MACHINE\SECURITY
+
+Type - "Allow" for all
+Inherited from - "None" for all
+Principal - Access - Applies to
+SYSTEM - Full Control - This key and subkeys
+Administrators - Special - This key and subkeys
+
+HKEY_LOCAL_MACHINE\SOFTWARE
+
+Type - "Allow" for all
+Inherited from - "None" for all
+Principal - Access - Applies to
+Users - Read - This key and subkeys
+Administrators - Full Control - This key and subkeys
+SYSTEM - Full Control - This key and subkeys
+CREATOR OWNER - Full Control - This key and subkeys
+ALL APPLICATION PACKAGES - Read - This key and subkeys
+
+HKEY_LOCAL_MACHINE\SYSTEM
+
+Type - "Allow" for all
+Inherited from - "None" for all
+Principal - Access - Applies to
+Users - Read - This key and subkeys
+Administrators - Full Control - This key and subkeys
+SYSTEM - Full Control - This key and subkeys
+CREATOR OWNER - Full Control - This key and Subkeys
+ALL APPLICATION PACKAGES - Read - This key and subkeys
+Server Operators - Read - This Key and subkeys (Domain controllers only)
+
+Other examples under the noted keys may also be sampled. There may be some instances where nonprivileged groups have greater than Read permission.
+
+Microsoft has given Read permission to the SOFTWARE and SYSTEM registry keys in Windows Server 2022 to the following SID. This is currently not a finding.
+S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681
+
+If the defaults have not been changed, these are not a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254255">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254255r958472_rule" weight="10.0" severity="low">
+            <version>WN22-00-000180</version>
+            <title>Windows Server 2022 nonadministrative accounts or groups must only have print permissions on printer shares.</title>
+            <description>&lt;VulnDiscussion&gt;Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57691r848580_fix">Configure the permissions on shared printers to restrict standard users to only have Print permissions.</fixtext>
+            <fix id="F-57691r848580_fix" />
+            <check system="C-57740r848579_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Open "Printers &amp; scanners" in "Settings".
+
+If there are no printers configured, this is NA. (Exclude Microsoft Print to PDF and Microsoft XPS Document Writer, which do not support sharing.)
+
+For each printer:
+
+Select the printer and "Manage". 
+
+Select "Printer Properties". 
+
+Select the "Sharing" tab. 
+
+If "Share this printer" is checked, select the "Security" tab.
+
+If any standard user accounts or groups have permissions other than "Print", this is a finding.
+
+The default is for the "Everyone" group to be given "Print" permission.
+
+"All APPLICATION PACKAGES" and "CREATOR OWNER" are not standard user accounts.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254256">
+        <title>SRG-OS-000118-GPOS-00060</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254256r1000152_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000190</version>
+            <title>Windows Server 2022 outdated or unused accounts must be removed or disabled.</title>
+            <description>&lt;VulnDiscussion&gt;Outdated or unused accounts provide penetration points that may go undetected. Inactive accounts must be deleted if no longer necessary or, if still required, disabled until 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-003627</ident>
+            <fixtext fixref="F-57692r848583_fix">Regularly review accounts to determine if they are still active. Remove or disable accounts that have not been used in the last 35 days.</fixtext>
+            <fix id="F-57692r848583_fix" />
+            <check system="C-57741r848582_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Open "Windows PowerShell".
+
+Domain Controllers:
+
+Enter "Search-ADAccount -AccountInactive -UsersOnly -TimeSpan 35.00:00:00"
+
+This will return accounts that have not been logged on to for 35 days, along with various attributes such as the Enabled status and LastLogonDate.
+
+Member servers and standalone or nondomain-joined systems:
+
+Copy or enter the lines below to the PowerShell window and enter. (Entering twice may be required. Do not include the quotes at the beginning and end of the query.)
+
+"([ADSI]('WinNT://{0}' -f $env:COMPUTERNAME)).Children | Where { $_.SchemaClassName -eq 'user' } | ForEach {
+ $user = ([ADSI]$_.Path)
+ $lastLogin = $user.Properties.LastLogin.Value
+ $enabled = ($user.Properties.UserFlags.Value -band 0x2) -ne 0x2
+ if ($lastLogin -eq $null) {
+ $lastLogin = 'Never'
+ }
+ Write-Host $user.Name $lastLogin $enabled 
+}"
+
+This will return a list of local accounts with the account name, last logon, and if the account is enabled (True/False).
+For example: User1 10/31/2015 5:49:56 AM True
+
+Review the list of accounts returned by the above queries to determine the finding validity for each account reported.
+
+Exclude the following accounts:
+
+- Built-in administrator account (Renamed, SID ending in 500)
+- Built-in guest account (Renamed, Disabled, SID ending in 501)
+- Application accounts
+
+If any enabled accounts have not been logged on to within the past 35 days, this is a finding.
+
+Inactive accounts that have been reviewed and deemed to be required must be documented with the Information System Security Officer (ISSO).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254257">
+        <title>SRG-OS-000104-GPOS-00051</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254257r958482_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000200</version>
+            <title>Windows Server 2022 accounts must require passwords.</title>
+            <description>&lt;VulnDiscussion&gt;The lack of password protection enables anyone to gain access to the information system, which opens a backdoor opportunity for intruders to compromise the system as well as other resources. Accounts on a system must require passwords.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000764</ident>
+            <fixtext fixref="F-57693r848586_fix">Configure all enabled accounts to require passwords.
+
+The password required flag can be set by entering the following on a command line: "Net user [username] /passwordreq:yes", substituting [username] with the name of the user account.</fixtext>
+            <fix id="F-57693r848586_fix" />
+            <check system="C-57742r848585_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Review the password required status for enabled user accounts.
+
+Open "PowerShell".
+
+Domain Controllers:
+
+Enter "Get-Aduser -Filter * -Properties Passwordnotrequired |FT Name, Passwordnotrequired, Enabled".
+
+Exclude disabled accounts (e.g., DefaultAccount, Guest) and Trusted Domain Objects (TDOs).
+
+If "Passwordnotrequired" is "True" or blank for any enabled user account, this is a finding.
+
+Member servers and standalone or nondomain-joined systems:
+
+Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordRequired=False and LocalAccount=True" | FT Name, PasswordRequired, Disabled, LocalAccount'.
+
+Exclude disabled accounts (e.g., DefaultAccount, Guest).
+
+If any enabled user accounts are returned with a "PasswordRequired" status of "False", this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254258">
+        <title>SRG-OS-000076-GPOS-00044</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254258r1000153_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000210</version>
+            <title>Windows Server 2022 passwords must be configured to expire.</title>
+            <description>&lt;VulnDiscussion&gt;Passwords that do not expire or are reused increase the exposure of a password with greater probability of being discovered or cracked.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004066</ident>
+            <fixtext fixref="F-57694r997807_fix">Configure all enabled user account passwords to expire.
+
+Uncheck "Password never expires" for all enabled user accounts in Active Directory Users and Computers for domain accounts and Users in Computer Management for member servers and standalone or nondomain-joined systems. Document any exceptions with the  information system security officer (ISSO).</fixtext>
+            <fix id="F-57694r997807_fix" />
+            <check system="C-57743r848588_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Review the password never expires status for enabled user accounts.
+
+Open "PowerShell".
+
+Domain Controllers:
+
+Enter "Search-ADAccount -PasswordNeverExpires -UsersOnly | FT Name, PasswordNeverExpires, Enabled".
+
+Exclude application accounts, disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account.
+
+If any enabled user accounts are returned with a "PasswordNeverExpires" status of "True", this is a finding.
+
+Member servers and standalone or nondomain-joined systems:
+
+Enter 'Get-CimInstance -Class Win32_Useraccount -Filter "PasswordExpires=False and LocalAccount=True" | FT Name, PasswordExpires, Disabled, LocalAccount'.
+
+Exclude application accounts and disabled accounts (e.g., DefaultAccount, Guest).
+
+If any enabled user accounts are returned with a "PasswordExpires" status of "False", this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254259">
+        <title>SRG-OS-000363-GPOS-00150</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254259r958794_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000220</version>
+            <title>Windows Server 2022 system files must be monitored for unauthorized changes.</title>
+            <description>&lt;VulnDiscussion&gt;Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code on 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;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001744</ident>
+            <fixtext fixref="F-57695r848592_fix">Monitor the system for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis. This can be done with the use of various monitoring tools.</fixtext>
+            <fix id="F-57695r848592_fix" />
+            <check system="C-57744r890537_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Determine whether the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis.
+
+If system files are not monitored for unauthorized changes, this is a finding.
+
+An approved and properly configured solution will contain both a list of baselines that includes all system file locations and a file comparison task that is scheduled to run at least weekly.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254260">
+        <title>SRG-OS-000138-GPOS-00069</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254260r958524_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000230</version>
+            <title>Windows Server 2022 nonsystem-created file shares must limit access to groups that require it.</title>
+            <description>&lt;VulnDiscussion&gt;Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to accounts that require it.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001090</ident>
+            <fixtext fixref="F-57696r848595_fix">If a nonsystem-created share is required on a system, configure the share and NTFS permissions to limit access to the specific groups or accounts that require it.
+
+Remove any unnecessary nonsystem-created shares.</fixtext>
+            <fix id="F-57696r848595_fix" />
+            <check system="C-57745r848594_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If only system-created shares such as "ADMIN$", "C$", and "IPC$" exist on the system, this is NA. (System-created shares will display a message that it has been shared for administrative purposes when "Properties" is selected.)
+
+Run "Computer Management".
+
+Navigate to System Tools &gt;&gt; Shared Folders &gt;&gt; Shares.
+
+Right-click any nonsystem-created shares.
+
+Select "Properties".
+
+Select the "Share Permissions" tab.
+
+If the file shares have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding.
+
+Select the "Security" tab.
+
+If the permissions have not been configured to restrict permissions to the specific groups or accounts that require access, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254261">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254261r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000240</version>
+            <title>Windows Server 2022 must have software certificate installation files removed.</title>
+            <description>&lt;VulnDiscussion&gt;Use of software certificates and their accompanying installation files for end users to access resources is less secure than the use of hardware-based certificates.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57697r848598_fix">Remove any certificate installation files (*.p12 and *.pfx) found on a system.
+
+Note: This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files.</fixtext>
+            <fix id="F-57697r848598_fix" />
+            <check system="C-57746r848597_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Search all drives for *.p12 and *.pfx files.
+
+If any files with these extensions exist, this is a finding.
+
+This does not apply to server-based applications that have a requirement for .p12 certificate files or Adobe PreFlight certificate files. Some applications create files with extensions of .p12 that are not certificate installation files. Removal of noncertificate installation files from systems is not required. These must be documented with the Information System Security Officer (ISSO).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254262">
+        <title>SRG-OS-000185-GPOS-00079</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254262r958552_rule" weight="10.0" severity="high">
+            <version>WN22-00-000250</version>
+            <title>Windows Server 2022 systems 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;This requirement addresses protection of user-generated data as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information.
+
+Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields).
+
+Satisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001199</ident>
+            <ident system="http://cyber.mil/cci">CCI-002475</ident>
+            <ident system="http://cyber.mil/cci">CCI-002476</ident>
+            <fixtext fixref="F-57698r848601_fix">Configure systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data to employ encryption to protect the confidentiality and integrity of all information at rest.</fixtext>
+            <fix id="F-57698r848601_fix" />
+            <check system="C-57747r848600_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify systems that require additional protections due to factors such as inadequate physical protection or sensitivity of the data employ encryption to protect the confidentiality and integrity of all information at rest.
+
+If they do not, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254263">
+        <title>SRG-OS-000425-GPOS-00189</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254263r958912_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000260</version>
+            <title>Windows Server 2022 must implement protection methods such as TLS, encrypted VPNs, or IPsec if the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process.</title>
+            <description>&lt;VulnDiscussion&gt;Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information.
+
+Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption.
+
+Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, encrypted VPNs, or IPsec.
+
+Satisfies: 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002420</ident>
+            <ident system="http://cyber.mil/cci">CCI-002422</ident>
+            <fixtext fixref="F-57699r848604_fix">Configure protection methods such as TLS, encrypted VPNs, or IPsec when the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process.</fixtext>
+            <fix id="F-57699r848604_fix" />
+            <check system="C-57748r848603_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, verify protection methods such as TLS, encrypted VPNs, or IPsec have been implemented.
+
+If protection methods have not been implemented, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254264">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254264r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000270</version>
+            <title>Windows Server 2022 must have the roles and features required by the system documented.</title>
+            <description>&lt;VulnDiscussion&gt;Unnecessary roles and features increase the attack surface of a system. Limiting roles and features of a system to only those necessary reduces this potential. The standard installation option (previously called Server Core) further reduces this when selected at installation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57700r848607_fix">Document the roles and features required for the system to operate. Uninstall any that are not required.</fixtext>
+            <fix id="F-57700r848607_fix" />
+            <check system="C-57749r848606_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Required roles and features will vary based on the function of the individual system.
+
+Roles and features specifically required to be disabled per the STIG are identified in separate requirements.
+
+If the organization has not documented the roles and features required for the system(s), this is a finding.
+
+The PowerShell command "Get-WindowsFeature" will list all roles and features with an "Install State".</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254265">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254265r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000280</version>
+            <title>Windows Server 2022 must have a host-based firewall installed and enabled.</title>
+            <description>&lt;VulnDiscussion&gt;A firewall provides a line of defense against attack, allowing or blocking inbound and outbound connections based on a set of rules.
+
+Satisfies: SRG-OS-000480-GPOS-00227, 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <ident system="http://cyber.mil/cci">CCI-002080</ident>
+            <fixtext fixref="F-57701r848610_fix">Install and enable a host-based firewall on the system.</fixtext>
+            <fix id="F-57701r848610_fix" />
+            <check system="C-57750r848609_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Determine if a host-based firewall is installed and enabled on the system.
+
+If a host-based firewall is not installed and enabled on the system, this is a finding.
+
+The configuration requirements will be determined by the applicable firewall STIG.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254266">
+        <title>SRG-OS-000191-GPOS-00080</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254266r1000154_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000290</version>
+            <title>Windows Server 2022 must employ automated mechanisms to determine the state of system components with regard to flaw remediation using the following frequency: continuously, where Endpoint Security Solution (ESS) is used; 30 days, for any additional internal network scans not covered by ESS; and annually, for external scans by Computer Network Defense Service Provider (CNDSP).</title>
+            <description>&lt;VulnDiscussion&gt;Without the use of automated mechanisms to scan for security flaws on a continuous and/or periodic basis, the operating system or other system components may remain vulnerable to the exploits presented by undetected software flaws. The operating system may have an integrated solution incorporating continuous scanning using ESS and periodic scanning using other 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57702r997810_fix">Install a DOD-approved ESS software and ensure it is operating continuously.</fixtext>
+            <fix id="F-57702r997810_fix" />
+            <check system="C-57751r997809_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify DOD-approved ESS software is installed and properly operating. Ask the site information system security manager (ISSM) for documentation of the ESS software installation and configuration.
+
+If the ISSM is not able to provide a documented configuration for an installed ESS or if the ESS software is not properly maintained or used, this is a finding.
+
+Note: Example of documentation can be a copy of the site's configuration control board (CCB)-approved software baseline with version of software noted or a memo from the ISSM stating current ESS software and version.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254267">
+        <title>SRG-OS-000002-GPOS-00002</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254267r958364_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000300</version>
+            <title>Windows Server 2022 must automatically remove or disable temporary user accounts after 72 hours.</title>
+            <description>&lt;VulnDiscussion&gt;If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation.
+
+Temporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation.
+
+If temporary accounts are used, the operating system must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours.
+
+To address access requirements, many operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000016</ident>
+            <fixtext fixref="F-57703r848616_fix">Configure temporary user accounts to automatically expire within 72 hours.
+
+Domain accounts can be configured with an account expiration date, under "Account" properties.
+
+Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where [username] is the name of the temporary user account.
+
+Delete any temporary user accounts that are no longer necessary.</fixtext>
+            <fix id="F-57703r848616_fix" />
+            <check system="C-57752r848615_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Review temporary user accounts for expiration dates.
+
+Determine if temporary user accounts are used and identify any that exist. If none exist, this is NA.
+
+Domain Controllers:
+
+Open "PowerShell".
+
+Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate".
+
+If "AccountExpirationDate" has not been defined within 72 hours for any temporary user account, this is a finding.
+
+Member servers and standalone or nondomain-joined systems:
+
+Open "Command Prompt".
+
+Run "Net user [username]", where [username] is the name of the temporary user account.
+
+If "Account expires" has not been defined within 72 hours for any temporary user account, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254268">
+        <title>SRG-OS-000123-GPOS-00064</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254268r958508_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000310</version>
+            <title>Windows Server 2022 must automatically remove or disable emergency accounts after the crisis is resolved or within 72 hours.</title>
+            <description>&lt;VulnDiscussion&gt;Emergency administrator accounts are privileged accounts established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability.
+
+Emergency administrator accounts are different from infrequently used accounts (i.e., local logon accounts used by system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account must be established for privileged users who need long-term maintenance accounts.
+
+To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001682</ident>
+            <fixtext fixref="F-57704r848619_fix">Remove emergency administrator accounts after a crisis has been resolved or configure the accounts to automatically expire within 72 hours.
+
+Domain accounts can be configured with an account expiration date, under "Account" properties.
+
+Local accounts can be configured to expire with the command "Net user [username] /expires:[mm/dd/yyyy]", where [username] is the name of the temporary user account.</fixtext>
+            <fix id="F-57704r848619_fix" />
+            <check system="C-57753r848618_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Determine if emergency administrator accounts are used and identify any that exist. If none exist, this is NA.
+
+If emergency administrator accounts cannot be configured with an expiration date due to an ongoing crisis, the accounts must be disabled or removed when the crisis is resolved.
+
+If emergency administrator accounts have not been configured with an expiration date or have not been disabled or removed following the resolution of a crisis, this is a finding.
+
+Domain Controllers:
+
+Open "PowerShell".
+
+Enter "Search-ADAccount -AccountExpiring | FT Name, AccountExpirationDate".
+
+If "AccountExpirationDate" has been defined and is not within 72 hours for an emergency administrator account, this is a finding.
+
+Member servers and standalone or nondomain-joined systems:
+
+Open "Command Prompt".
+
+Run "Net user [username]", where [username] is the name of the emergency account.
+
+If "Account expires" has been defined and is not within 72 hours for an emergency administrator account, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254269">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254269r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000320</version>
+            <title>Windows Server 2022 must not have the Fax Server role installed.</title>
+            <description>&lt;VulnDiscussion&gt;Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57705r848622_fix">Uninstall the "Fax Server" role.
+
+Start "Server Manager".
+
+Select the server with the role.
+
+Scroll down to "ROLES AND FEATURES" in the right pane.
+
+Select "Remove Roles and Features" from the drop-down "TASKS" list.
+
+Select the appropriate server on the "Server Selection" page and click "Next".
+
+Deselect "Fax Server" on the "Roles" page.
+
+Click "Next" and "Remove" as prompted.</fixtext>
+            <fix id="F-57705r848622_fix" />
+            <check system="C-57754r848621_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Open "PowerShell".
+
+Enter "Get-WindowsFeature | Where Name -eq Fax".
+
+If "Installed State" is "Installed", this is a finding.
+
+An Installed State of "Available" or "Removed" is not a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254270">
+        <title>SRG-OS-000096-GPOS-00050</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254270r958480_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000330</version>
+            <title>Windows Server 2022 must not have the Microsoft FTP service installed unless required by the organization.</title>
+            <description>&lt;VulnDiscussion&gt;Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000382</ident>
+            <fixtext fixref="F-57706r848625_fix">Uninstall the "FTP Server" role.
+
+Start "Server Manager".
+
+Select the server with the role.
+
+Scroll down to "ROLES AND FEATURES" in the right pane.
+
+Select "Remove Roles and Features" from the drop-down "TASKS" list.
+
+Select the appropriate server on the "Server Selection" page and click "Next".
+
+Deselect "FTP Server" under "Web Server (IIS)" on the "Roles" page.
+
+Click "Next" and "Remove" as prompted.</fixtext>
+            <fix id="F-57706r848625_fix" />
+            <check system="C-57755r848624_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the server has the role of an FTP server, this is NA.
+
+Open "PowerShell".
+
+Enter "Get-WindowsFeature | Where Name -eq Web-Ftp-Service".
+
+If "Installed State" is "Installed", this is a finding.
+
+An Installed State of "Available" or "Removed" is not a finding.
+
+If the system has the role of an FTP server, this must be documented with the Information System Security Officer (ISSO).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254271">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254271r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000340</version>
+            <title>Windows Server 2022 must not have the Peer Name Resolution Protocol installed.</title>
+            <description>&lt;VulnDiscussion&gt;Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57707r848628_fix">Uninstall the "Peer Name Resolution Protocol" feature.
+
+Start "Server Manager".
+
+Select the server with the feature.
+
+Scroll down to "ROLES AND FEATURES" in the right pane.
+
+Select "Remove Roles and Features" from the drop-down "TASKS" list.
+
+Select the appropriate server on the "Server Selection" page and click "Next".
+
+Deselect "Peer Name Resolution Protocol" on the "Features" page.
+
+Click "Next" and "Remove" as prompted.</fixtext>
+            <fix id="F-57707r848628_fix" />
+            <check system="C-57756r848627_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Open "PowerShell".
+
+Enter "Get-WindowsFeature | Where Name -eq PNRP".
+
+If "Installed State" is "Installed", this is a finding.
+
+An Installed State of "Available" or "Removed" is not a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254272">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254272r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000350</version>
+            <title>Windows Server 2022 must not have Simple TCP/IP Services installed.</title>
+            <description>&lt;VulnDiscussion&gt;Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57708r848631_fix">Uninstall the "Simple TCP/IP Services" feature.
+
+Start "Server Manager".
+
+Select the server with the feature.
+
+Scroll down to "ROLES AND FEATURES" in the right pane.
+
+Select "Remove Roles and Features" from the drop-down "TASKS" list.
+
+Select the appropriate server on the "Server Selection" page and click "Next".
+
+Deselect "Simple TCP/IP Services" on the "Features" page.
+
+Click "Next" and "Remove" as prompted.</fixtext>
+            <fix id="F-57708r848631_fix" />
+            <check system="C-57757r848630_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Open "PowerShell".
+
+Enter "Get-WindowsFeature | Where Name -eq Simple-TCPIP".
+
+If "Installed State" is "Installed", this is a finding.
+
+An Installed State of "Available" or "Removed" is not a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254273">
+        <title>SRG-OS-000096-GPOS-00050</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254273r958480_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000360</version>
+            <title>Windows Server 2022 must not have the Telnet Client installed.</title>
+            <description>&lt;VulnDiscussion&gt;Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000382</ident>
+            <fixtext fixref="F-57709r848634_fix">Uninstall the "Telnet Client" feature.
+
+Start "Server Manager".
+
+Select the server with the feature.
+
+Scroll down to "ROLES AND FEATURES" in the right pane.
+
+Select "Remove Roles and Features" from the drop-down "TASKS" list.
+
+Select the appropriate server on the "Server Selection" page and click "Next".
+
+Deselect "Telnet Client" on the "Features" page.
+
+Click "Next" and "Remove" as prompted.</fixtext>
+            <fix id="F-57709r848634_fix" />
+            <check system="C-57758r848633_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Open "PowerShell".
+
+Enter "Get-WindowsFeature | Where Name -eq Telnet-Client".
+
+If "Installed State" is "Installed", this is a finding.
+
+An Installed State of "Available" or "Removed" is not a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254274">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254274r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000370</version>
+            <title>Windows Server 2022 must not have the TFTP Client installed.</title>
+            <description>&lt;VulnDiscussion&gt;Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption or may provide unauthorized access to 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57710r848637_fix">Uninstall the "TFTP Client" feature.
+
+Start "Server Manager".
+
+Select the server with the feature.
+
+Scroll down to "ROLES AND FEATURES" in the right pane.
+
+Select "Remove Roles and Features" from the drop-down "TASKS" list.
+
+Select the appropriate server on the "Server Selection" page and click "Next".
+
+Deselect "TFTP Client" on the "Features" page.
+
+Click "Next" and "Remove" as prompted.</fixtext>
+            <fix id="F-57710r848637_fix" />
+            <check system="C-57759r848636_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Open "PowerShell".
+
+Enter "Get-WindowsFeature | Where Name -eq TFTP-Client".
+
+If "Installed State" is "Installed", this is a finding.
+
+An Installed State of "Available" or "Removed" is not a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254275">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254275r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000380</version>
+            <title>Windows Server 2022 must not the Server Message Block (SMB) v1 protocol installed.</title>
+            <description>&lt;VulnDiscussion&gt;SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks and is not FIPS compliant.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57711r848640_fix">Uninstall the SMBv1 protocol.
+
+Open "Windows PowerShell" with elevated privileges (run as administrator).
+
+Enter "Uninstall-WindowsFeature -Name FS-SMB1 -Restart".
+(Omit the Restart parameter if an immediate restart of the system cannot be done.)
+
+Alternately:
+
+Start "Server Manager".
+
+Select the server with the feature.
+
+Scroll down to "ROLES AND FEATURES" in the right pane.
+
+Select "Remove Roles and Features" from the drop-down "TASKS" list.
+
+Select the appropriate server on the "Server Selection" page and click "Next".
+
+Deselect "SMB 1.0/CIFS File Sharing Support" on the "Features" page.
+
+Click "Next" and "Remove" as prompted.</fixtext>
+            <fix id="F-57711r848640_fix" />
+            <check system="C-57760r848639_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Different methods are available to disable SMBv1 on Windows Server 2022. This is the preferred method, however if WN22-00-000390 and WN22-00-000400 are configured, this is NA.
+
+Open "Windows PowerShell" with elevated privileges (run as administrator).
+
+Enter "Get-WindowsFeature -Name FS-SMB1".
+
+If "Installed State" is "Installed", this is a finding.
+
+An Installed State of "Available" or "Removed" is not a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254276">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254276r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000390</version>
+            <title>Windows Server 2022 must have the Server Message Block (SMB) v1 protocol disabled on the SMB server.</title>
+            <description>&lt;VulnDiscussion&gt;SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57712r848643_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; MS Security Guide &gt;&gt; Configure SMBv1 Server to "Disabled".
+
+The system must be restarted for the change to take effect.
+
+This policy setting requires the installation of the SecGuide custom templates included with the STIG package. "SecGuide.admx" and "SecGuide.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.</fixtext>
+            <fix id="F-57712r848643_fix" />
+            <check system="C-57761r848642_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Different methods are available to disable SMBv1 on Windows Server 2022, if WN22-00-000380 is configured, this is NA.
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\
+
+Value Name: SMB1
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254277">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254277r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000400</version>
+            <title>Windows Server 2022 must have the Server Message Block (SMB) v1 protocol disabled on the SMB client.</title>
+            <description>&lt;VulnDiscussion&gt;SMBv1 is a legacy protocol that uses the MD5 algorithm as part of SMB. MD5 is known to be vulnerable to a number of attacks such as collision and preimage attacks as well as not being FIPS compliant.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57713r848646_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; MS Security Guide &gt;&gt; Configure SMBv1 client driver to "Enabled" with "Disable driver (recommended)" selected for "Configure MrxSmb10 driver".
+
+The system must be restarted for the changes to take effect.
+
+This policy setting requires the installation of the SecGuide custom templates included with the STIG package. "SecGuide.admx" and "SecGuide.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.</fixtext>
+            <fix id="F-57713r848646_fix" />
+            <check system="C-57762r848645_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Different methods are available to disable SMBv1 on Windows Server 2022, if WN22-00-000380 is configured, this is NA.
+
+If the following registry value is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SYSTEM\CurrentControlSet\Services\mrxsmb10\
+
+Value Name: Start
+
+Type: REG_DWORD
+Value: 0x00000004 (4)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254278">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254278r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000410</version>
+            <title>Windows Server 2022 must not have Windows PowerShell 2.0 installed.</title>
+            <description>&lt;VulnDiscussion&gt;Windows PowerShell 5.x added advanced logging features that can provide additional detail when malware has been run on a system. Disabling the Windows PowerShell 2.0 mitigates against a downgrade attack that evades the Windows PowerShell 5.x script block logging feature.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57714r848649_fix">Uninstall the "Windows PowerShell 2.0 Engine".
+
+Start "Server Manager".
+
+Select the server with the feature.
+
+Scroll down to "ROLES AND FEATURES" in the right pane.
+
+Select "Remove Roles and Features" from the drop-down "TASKS" list.
+
+Select the appropriate server on the "Server Selection" page and click "Next".
+
+Deselect "Windows PowerShell 2.0 Engine" under "Windows PowerShell" on the "Features" page.
+
+Click "Next" and "Remove" as prompted.</fixtext>
+            <fix id="F-57714r848649_fix" />
+            <check system="C-57763r848648_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Open "PowerShell".
+
+Enter "Get-WindowsFeature | Where Name -eq PowerShell-v2".
+
+If "Installed State" is "Installed", this is a finding.
+
+An Installed State of "Available" or "Removed" is not a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254279">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254279r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000420</version>
+            <title>Windows Server 2022 FTP servers must be configured to prevent anonymous logons.</title>
+            <description>&lt;VulnDiscussion&gt;The FTP service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult.
+
+Using accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57715r848652_fix">Configure the FTP service to prevent anonymous logons.
+
+Open "Internet Information Services (IIS) Manager".
+
+Select the server.
+
+Double-click "FTP Authentication".
+
+Select "Anonymous Authentication".
+
+Select "Disabled" under "Actions".</fixtext>
+            <fix id="F-57715r848652_fix" />
+            <check system="C-57764r848651_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If FTP is not installed on the system, this is NA.
+
+Open "Internet Information Services (IIS) Manager".
+
+Select the server.
+
+Double-click "FTP Authentication".
+
+If the "Anonymous Authentication" status is "Enabled", this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254280">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254280r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000430</version>
+            <title>Windows Server 2022 FTP servers must be configured to prevent access to the system drive.</title>
+            <description>&lt;VulnDiscussion&gt;The FTP service allows remote users to access shared files and directories that could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57716r848655_fix">Configure the FTP sites to allow access only to specific FTP shared resources. Do not allow access to other areas of the system.</fixtext>
+            <fix id="F-57716r848655_fix" />
+            <check system="C-57765r848654_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If FTP is not installed on the system, this is NA.
+
+Open "Internet Information Services (IIS) Manager".
+
+Select "Sites" under the server name.
+
+For any sites with a Binding that lists FTP, right-click the site and select "Explore".
+
+If the site is not defined to a specific folder for shared FTP resources, this is a finding.
+
+If the site includes any system areas such as root of the drive, Program Files, or Windows directories, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254281">
+        <title>SRG-OS-000355-GPOS-00143</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254281r1000155_rule" weight="10.0" severity="low">
+            <version>WN22-00-000440</version>
+            <title>The Windows Server 2022 time service must synchronize with an appropriate DOD time source.</title>
+            <description>&lt;VulnDiscussion&gt;The Windows Time Service controls time synchronization settings. Time synchronization is essential for authentication and auditing purposes. If the Windows Time Service is used, it must synchronize with a secure, authorized time source. Domain-joined systems are automatically configured to synchronize with domain controllers. If an NTP server is configured, it must synchronize with a secure, authorized time source.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004923</ident>
+            <fixtext fixref="F-57717r921939_fix">Configure the system to synchronize time with an appropriate DOD time source.
+
+Domain-joined systems use NT5DS to synchronize time from other systems in the domain by default.
+
+If the system needs to be configured to an NTP server, configure the system to point to an authorized time server by setting the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Windows Time Service &gt;&gt; Time Providers. Change "Configure Windows NTP Client" to "Enabled", and configure the "NtpServer" field to point to an appropriate DOD time server.
+
+The US Naval Observatory operates stratum 1 time servers, identified at https://www.cnmoc.usff.navy.mil/Our-Commands/United-States-Naval-Observatory/Precise-Time-Department/Network-Time-Protocol-NTP/. Time synchronization will occur through a hierarchy of time servers down to the local level. Clients and lower-level servers will synchronize with an authorized time server in the hierarchy.</fixtext>
+            <fix id="F-57717r921939_fix" />
+            <check system="C-57766r921938_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Review the Windows time service configuration.
+
+Open an elevated "Command Prompt" (run as administrator).
+
+Enter "W32tm /query /configuration".
+
+Domain-joined systems (excluding the domain controller with the PDC emulator role):
+
+If the value for "Type" under "NTP Client" is not "NT5DS", this is a finding.
+
+Other systems:
+
+If systems are configured with a "Type" of "NTP", including standalone or nondomain-joined systems and the domain controller with the PDC Emulator role, and do not have a DOD time server defined for "NTPServer", this is a finding.
+
+To determine the domain controller with the PDC Emulator role:
+
+Open "PowerShell".
+
+Enter "Get-ADDomain | FT PDCEmulator".</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254282">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254282r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000450</version>
+            <title>Windows Server 2022 must have orphaned security identifiers (SIDs) removed from user rights.</title>
+            <description>&lt;VulnDiscussion&gt;Accounts or groups given rights on a system may show up as unresolved SIDs for various reasons including deletion of the accounts or groups. If the account or group objects are reanimated, there is a potential they may still have rights no longer intended. Valid domain accounts or groups may also show up as unresolved SIDs if a connection to the domain cannot be 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57718r848661_fix">Remove any unresolved SIDs found in User Rights assignments and determined to not be for currently valid accounts or groups by removing the accounts or groups from the appropriate group policy.</fixtext>
+            <fix id="F-57718r848661_fix" />
+            <check system="C-57767r848660_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Review the effective User Rights setting in Local Group Policy Editor.
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+Review each User Right listed for any unresolved SIDs to determine whether they are valid, such as due to being temporarily disconnected from the domain. (Unresolved SIDs have the format that begins with "*S-1-".)
+
+If any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /export /areas USER_RIGHTS /cfg c:\path\UserRights.txt
+
+The results in the file identify user right assignments by SID instead of group name. Review the SIDs for unidentified ones. A list of typical SIDs \ Groups is below, search Microsoft for articles on well known SIDs for others. 
+
+If any unresolved SIDs exist and are not for currently valid accounts or groups, this is a finding.
+
+SID - Group
+S-1-5-11 - Authenticated Users
+S-1-5-113 - Local account
+S-1-5-114 - Local account and member of Administrators group
+S-1-5-19 - Local Service
+S-1-5-20 - Network Service
+S-1-5-32-544 - Administrators
+S-1-5-32-546 - Guests
+S-1-5-6 - Service
+S-1-5-9 - Enterprise Domain Controllers
+S-1-5-domain-512 - Domain Admins
+S-1-5-root domain-519 - Enterprise Admins
+S-1-5-80-3139157870-2983391045-3678747466-658725712-1809340420 - NT Service\WdiServiceHost</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254283">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254283r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000460</version>
+            <title>Windows Server 2022 systems must have Unified Extensible Firmware Interface (UEFI) firmware and be configured to run in UEFI mode, not Legacy BIOS.</title>
+            <description>&lt;VulnDiscussion&gt;UEFI provides additional security features in comparison to legacy BIOS firmware, including Secure Boot. UEFI is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. Systems with UEFI that are operating in "Legacy BIOS" mode will not support these security features.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57719r848664_fix">Configure UEFI firmware to run in "UEFI" mode, not "Legacy BIOS" mode.</fixtext>
+            <fix id="F-57719r848664_fix" />
+            <check system="C-57768r848663_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Devices that have UEFI firmware must run in "UEFI" mode.
+
+Verify the system firmware is configured to run in "UEFI" mode, not "Legacy BIOS".
+
+Run "System Information".
+
+Under "System Summary", if "BIOS Mode" does not display "UEFI", this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254284">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254284r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000470</version>
+            <title>Windows Server 2022 must have Secure Boot enabled.</title>
+            <description>&lt;VulnDiscussion&gt;Secure Boot is a standard that ensures systems boot only to a trusted operating system. Secure Boot is required to support additional security features in Windows, including Virtualization Based Security and Credential Guard. If Secure Boot is turned off, these security features will not function.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57720r848667_fix">Enable Secure Boot in the system firmware.</fixtext>
+            <fix id="F-57720r848667_fix" />
+            <check system="C-57769r848666_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Devices that have UEFI firmware must have Secure Boot enabled.
+
+Run "System Information".
+
+Under "System Summary", if "Secure Boot State" does not display "On", this is a finding.
+
+On server core installations, run the following PowerShell command:
+
+Confirm-SecureBootUEFI
+
+If a value of "True" is not returned, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254285">
+        <title>SRG-OS-000329-GPOS-00128</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254285r958736_rule" weight="10.0" severity="medium">
+            <version>WN22-AC-000010</version>
+            <title>Windows Server 2022 account lockout duration must be configured to 15 minutes or greater.</title>
+            <description>&lt;VulnDiscussion&gt;The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002238</ident>
+            <fixtext fixref="F-57721r848670_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Account Lockout Policy &gt;&gt; Account lockout duration to "15" minutes or greater.
+
+A value of "0" is also acceptable, requiring an administrator to unlock the account.</fixtext>
+            <fix id="F-57721r848670_fix" />
+            <check system="C-57770r848669_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Account Lockout Policy.
+
+If the "Account lockout duration" is less than "15" minutes (excluding "0"), this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt
+
+If "LockoutDuration" is less than "15" (excluding "0") in the file, this is a finding.
+
+Configuring this to "0", requiring an administrator to unlock the account, is more restrictive and is not a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254286">
+        <title>SRG-OS-000021-GPOS-00005</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254286r958388_rule" weight="10.0" severity="medium">
+            <version>WN22-AC-000020</version>
+            <title>Windows Server 2022 must have the number of allowed bad logon attempts configured to three or less.</title>
+            <description>&lt;VulnDiscussion&gt;The account lockout feature, when enabled, prevents brute-force password attacks on the system. The higher this value is, the less effective the account lockout feature will be in protecting the local system. The number of bad logon attempts must be reasonably small to minimize the possibility of a successful password attack while allowing for honest errors made during normal user 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000044</ident>
+            <fixtext fixref="F-57722r848673_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Account Lockout Policy &gt;&gt; Account lockout threshold to "3" or fewer invalid logon attempts (excluding "0", which is unacceptable).</fixtext>
+            <fix id="F-57722r848673_fix" />
+            <check system="C-57771r848672_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Account Lockout Policy.
+
+If the "Account lockout threshold" is "0" or more than "3" attempts, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt
+
+If "LockoutBadCount" equals "0" or is greater than "3" in the file, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254287">
+        <title>SRG-OS-000021-GPOS-00005</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254287r958388_rule" weight="10.0" severity="medium">
+            <version>WN22-AC-000030</version>
+            <title>Windows Server 2022 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater.</title>
+            <description>&lt;VulnDiscussion&gt;The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that must pass after failed logon attempts before the counter is reset to "0". The smaller this value is, the less effective the account lockout feature will be in protecting the local 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000044</ident>
+            <fixtext fixref="F-57723r848676_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Account Lockout Policy &gt;&gt; Reset account lockout counter after to at least "15" minutes.</fixtext>
+            <fix id="F-57723r848676_fix" />
+            <check system="C-57772r848675_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Account Lockout Policy.
+
+If the "Reset account lockout counter after" value is less than "15" minutes, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt
+
+If "ResetLockoutCount" is less than "15" in the file, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254288">
+        <title>SRG-OS-000077-GPOS-00045</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254288r1000156_rule" weight="10.0" severity="medium">
+            <version>WN22-AC-000040</version>
+            <title>Windows Server 2022 password history must be configured to 24 passwords remembered.</title>
+            <description>&lt;VulnDiscussion&gt;A system is more vulnerable to unauthorized access when system users recycle the same password several times without being required to change to a unique password on a regularly scheduled basis. This enables users to effectively negate the purpose of mandating periodic password changes. The default value is "24" for Windows domain systems. DOD has decided this is the appropriate value for all Windows systems.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004061</ident>
+            <fixtext fixref="F-57724r848679_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Password Policy &gt;&gt; Enforce password history to "24" passwords remembered.</fixtext>
+            <fix id="F-57724r848679_fix" />
+            <check system="C-57773r848678_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Password Policy.
+
+If the value for "Enforce password history" is less than "24" passwords remembered, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt
+
+If "PasswordHistorySize" is less than "24" in the file, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254289">
+        <title>SRG-OS-000076-GPOS-00044</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254289r1000157_rule" weight="10.0" severity="medium">
+            <version>WN22-AC-000050</version>
+            <title>Windows Server 2022 maximum password age must be configured to 60 days or less.</title>
+            <description>&lt;VulnDiscussion&gt;The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the passwords. Scheduled changing of passwords hinders the ability of unauthorized system users to crack passwords and gain 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;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004066</ident>
+            <fixtext fixref="F-57725r848682_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Password Policy &gt;&gt; Maximum password age to "60" days or less (excluding "0", which is unacceptable).</fixtext>
+            <fix id="F-57725r848682_fix" />
+            <check system="C-57774r848681_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Password Policy.
+
+If the value for the "Maximum password age" is greater than "60" days, this is a finding.
+
+If the value is set to "0" (never expires), this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt
+
+If "MaximumPasswordAge" is greater than "60" or equal to "0" in the file, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254290">
+        <title>SRG-OS-000075-GPOS-00043</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254290r1000158_rule" weight="10.0" severity="medium">
+            <version>WN22-AC-000060</version>
+            <title>Windows Server 2022 minimum password age must be configured to at least one day.</title>
+            <description>&lt;VulnDiscussion&gt;Permitting passwords to be changed in immediate succession within the same day allows users to cycle passwords through their history database. This enables users to effectively negate the purpose of mandating periodic password changes.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004066</ident>
+            <fixtext fixref="F-57726r848685_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Password Policy &gt;&gt; Minimum password age to at least "1" day.</fixtext>
+            <fix id="F-57726r848685_fix" />
+            <check system="C-57775r848684_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Password Policy.
+
+If the value for the "Minimum password age" is set to "0" days ("Password can be changed immediately"), this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt
+
+If "MinimumPasswordAge" equals "0" in the file, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254291">
+        <title>SRG-OS-000078-GPOS-00046</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254291r1000159_rule" weight="10.0" severity="medium">
+            <version>WN22-AC-000070</version>
+            <title>Windows Server 2022 minimum password length must be configured to 14 characters.</title>
+            <description>&lt;VulnDiscussion&gt;Information systems not protected with strong password schemes (including passwords of minimum length) provide the opportunity for anyone to crack the password, thus gaining access to the system and compromising the device, information, or the local 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004066</ident>
+            <fixtext fixref="F-57727r848688_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Password Policy &gt;&gt; "Minimum password length" to "14" characters.</fixtext>
+            <fix id="F-57727r848688_fix" />
+            <check system="C-57776r848687_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Password Policy.
+
+If the value for the "Minimum password length," is less than "14" characters, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt
+
+If "MinimumPasswordLength" is less than "14" in the file, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254292">
+        <title>SRG-OS-000069-GPOS-00037</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254292r1000160_rule" weight="10.0" severity="medium">
+            <version>WN22-AC-000080</version>
+            <title>Windows Server 2022 must have the built-in Windows password complexity policy enabled.</title>
+            <description>&lt;VulnDiscussion&gt;The use of complex passwords increases their strength against attack. The built-in Windows password complexity policy requires passwords to contain at least three of the four types of characters (numbers, uppercase and lowercase letters, and special characters) and prevents the inclusion of user names or parts of user names.
+
+Satisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000266-GPOS-00101&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004066</ident>
+            <fixtext fixref="F-57728r848691_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Password Policy &gt;&gt; Password must meet complexity requirements to "Enabled".</fixtext>
+            <fix id="F-57728r848691_fix" />
+            <check system="C-57777r848690_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Password Policy.
+
+If the value for "Password must meet complexity requirements" is not set to "Enabled", this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt
+
+If "PasswordComplexity" equals "0" in the file, this is a finding.
+
+Note: If an external password filter is in use that enforces all four character types and requires this setting to be set to "Disabled", this would not be considered a finding. If this setting does not affect the use of an external password filter, it must be enabled for fallback purposes.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254293">
+        <title>SRG-OS-000073-GPOS-00041</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254293r1000161_rule" weight="10.0" severity="high">
+            <version>WN22-AC-000090</version>
+            <title>Windows Server 2022 reversible password encryption must be disabled.</title>
+            <description>&lt;VulnDiscussion&gt;Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords, which are easily compromised. For this reason, this policy must never be enabled.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004062</ident>
+            <fixtext fixref="F-57729r848694_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Password Policy &gt;&gt; Store passwords using reversible encryption to "Disabled".</fixtext>
+            <fix id="F-57729r848694_fix" />
+            <check system="C-57778r848693_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Password Policy.
+
+If the value for "Store passwords using reversible encryption" is not set to "Disabled", this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt
+
+If "ClearTextPassword" equals "1" in the file, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254294">
+        <title>SRG-OS-000342-GPOS-00133</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254294r958754_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000010</version>
+            <title>Windows Server 2022 audit records must be backed up to a different system or media than the system being audited.</title>
+            <description>&lt;VulnDiscussion&gt;Protection of log data includes ensuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001851</ident>
+            <fixtext fixref="F-57730r848697_fix">Establish and implement a process for backing up log data to another system or media other than the system being audited.</fixtext>
+            <fix id="F-57730r848697_fix" />
+            <check system="C-57779r848696_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Determine if a process to back up log data to a different system or media than the system being audited has been implemented.
+
+If it has not, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254295">
+        <title>SRG-OS-000479-GPOS-00224</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254295r959008_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000020</version>
+            <title>Windows Server 2022 must, at a minimum, offload audit records of interconnected systems in real time and offload standalone or nondomain-joined systems weekly.</title>
+            <description>&lt;VulnDiscussion&gt;Protection of log data includes assuring the log data is not accidentally lost or deleted. Audit information stored in one location is vulnerable to accidental or incidental deletion or alteration.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001851</ident>
+            <fixtext fixref="F-57731r848700_fix">Configure the system to, at a minimum, offload audit records of interconnected systems in real time and offload standalone or nondomain-joined systems weekly.</fixtext>
+            <fix id="F-57731r848700_fix" />
+            <check system="C-57780r848699_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the audit records, at a minimum, are offloaded for interconnected systems in real time and offloaded for standalone or nondomain-joined systems weekly. 
+
+If they are not, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254296">
+        <title>SRG-OS-000057-GPOS-00027</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254296r958434_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000030</version>
+            <title>Windows Server 2022 permissions for the Application event log must prevent access by nonprivileged accounts.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The Application event log may be susceptible to tampering if proper permissions are not applied.
+
+Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000162</ident>
+            <ident system="http://cyber.mil/cci">CCI-000163</ident>
+            <ident system="http://cyber.mil/cci">CCI-000164</ident>
+            <fixtext fixref="F-57732r848703_fix">Configure the permissions on the Application event log file (Application.evtx) to prevent access by nonprivileged accounts. The default permissions listed below satisfy this requirement:
+
+Eventlog - Full Control
+SYSTEM - Full Control
+Administrators - Full Control
+
+The default location is the "%SystemRoot%\System32\winevt\Logs" folder.
+
+If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".</fixtext>
+            <fix id="F-57732r848703_fix" />
+            <check system="C-57781r848702_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Navigate to the Application event log file.
+
+The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder.
+
+If the permissions for the "Application.evtx" file are not as restrictive as the default permissions listed below, this is a finding:
+
+Eventlog - Full Control
+SYSTEM - Full Control
+Administrators - Full Control</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254297">
+        <title>SRG-OS-000057-GPOS-00027</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254297r958434_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000040</version>
+            <title>Windows Server 2022 permissions for the Security event log must prevent access by nonprivileged accounts.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The Security event log may disclose sensitive information or be susceptible to tampering if proper permissions are not applied.
+
+Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000162</ident>
+            <ident system="http://cyber.mil/cci">CCI-000163</ident>
+            <ident system="http://cyber.mil/cci">CCI-000164</ident>
+            <fixtext fixref="F-57733r848706_fix">Configure the permissions on the Security event log file (Security.evtx) to prevent access by nonprivileged accounts. The default permissions listed below satisfy this requirement:
+
+Eventlog - Full Control
+SYSTEM - Full Control
+Administrators - Full Control
+
+The default location is the "%SystemRoot%\System32\winevt\Logs" folder.
+
+If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".</fixtext>
+            <fix id="F-57733r848706_fix" />
+            <check system="C-57782r848705_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Navigate to the Security event log file.
+
+The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder.
+
+If the permissions for the "Security.evtx" file are not as restrictive as the default permissions listed below, this is a finding:
+
+Eventlog - Full Control
+SYSTEM - Full Control
+Administrators - Full Control</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254298">
+        <title>SRG-OS-000057-GPOS-00027</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254298r958434_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000050</version>
+            <title>Windows Server 2022 permissions for the System event log must prevent access by nonprivileged accounts.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The System event log may be susceptible to tampering if proper permissions are not applied.
+
+Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000162</ident>
+            <ident system="http://cyber.mil/cci">CCI-000163</ident>
+            <ident system="http://cyber.mil/cci">CCI-000164</ident>
+            <fixtext fixref="F-57734r848709_fix">Configure the permissions on the System event log file (System.evtx) to prevent access by nonprivileged accounts. The default permissions listed below satisfy this requirement:
+
+Eventlog - Full Control
+SYSTEM - Full Control
+Administrators - Full Control
+
+The default location is the "%SystemRoot%\System32\winevt\Logs" folder.
+
+If the location of the logs has been changed, when adding Eventlog to the permissions, it must be entered as "NT Service\Eventlog".</fixtext>
+            <fix id="F-57734r848709_fix" />
+            <check system="C-57783r848708_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Navigate to the System event log file.
+
+The default location is the "%SystemRoot%\System32\winevt\Logs" folder. However, the logs may have been moved to another folder.
+
+If the permissions for the "System.evtx" file are not as restrictive as the default permissions listed below, this is a finding:
+
+Eventlog - Full Control
+SYSTEM - Full Control
+Administrators - Full Control</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254299">
+        <title>SRG-OS-000257-GPOS-00098</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254299r991558_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000060</version>
+            <title>Windows Server 2022 Event Viewer must be protected from unauthorized modification and deletion.</title>
+            <description>&lt;VulnDiscussion&gt;Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information.
+
+Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys to make access decisions regarding the modification or deletion of audit tools.
+
+Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001494</ident>
+            <ident system="http://cyber.mil/cci">CCI-001495</ident>
+            <fixtext fixref="F-57735r848712_fix">Configure the permissions on the "Eventvwr.exe" file to prevent modification by any groups or accounts other than TrustedInstaller. The default permissions listed below satisfy this requirement:
+
+TrustedInstaller - Full Control
+Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read &amp; Execute
+
+The default location is the "%SystemRoot%\System32" folder.</fixtext>
+            <fix id="F-57735r848712_fix" />
+            <check system="C-57784r951103_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This is not applicable for Windows Core Edition.
+
+Navigate to "%SystemRoot%\System32".
+
+View the permissions on "Eventvwr.exe".
+
+If any groups or accounts other than TrustedInstaller have "Full control" or "Modify" permissions, this is a finding.
+
+The default permissions below satisfy this requirement:
+
+TrustedInstaller - Full Control
+Administrators, SYSTEM, Users, ALL APPLICATION PACKAGES, ALL RESTRICTED APPLICATION PACKAGES - Read &amp; Execute</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254300">
+        <title>SRG-OS-000470-GPOS-00214</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254300r991578_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000070</version>
+            <title>Windows Server 2022 must be configured to audit Account Logon - Credential Validation successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Credential Validation records events related to validation tests on credentials for a user account 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <fixtext fixref="F-57736r848715_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Account Logon &gt;&gt; Audit Credential Validation with "Success" selected.</fixtext>
+            <fix id="F-57736r848715_fix" />
+            <check system="C-57785r848714_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Account Logon &gt;&gt; Credential Validation - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254301">
+        <title>SRG-OS-000470-GPOS-00214</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254301r991578_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000080</version>
+            <title>Windows Server 2022 must be configured to audit Account Logon - Credential Validation failures.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Credential Validation records events related to validation tests on credentials for a user account 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <fixtext fixref="F-57737r848718_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Account Logon &gt;&gt; Audit Credential Validation with "Failure" selected.</fixtext>
+            <fix id="F-57737r848718_fix" />
+            <check system="C-57786r848717_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Account Logon &gt;&gt; Credential Validation - Failure</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254302">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254302r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000090</version>
+            <title>Windows Server 2022 must be configured to audit Account Management - Other Account Management Events successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Other Account Management Events records events such as the access of a password hash or the Password Policy Checking API being called.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57738r848721_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Account Management &gt;&gt; Audit Other Account Management Events with "Success" selected.</fixtext>
+            <fix id="F-57738r848721_fix" />
+            <check system="C-57787r848720_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding:
+
+Account Management &gt;&gt; Other Account Management Events - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254303">
+        <title>SRG-OS-000004-GPOS-00004</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254303r958368_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000100</version>
+            <title>Windows Server 2022 must be configured to audit Account Management - Security Group Management successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Security Group Management records events such as creating, deleting, or changing security groups, including changes in group members.
+
+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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000018</ident>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-001403</ident>
+            <ident system="http://cyber.mil/cci">CCI-001404</ident>
+            <ident system="http://cyber.mil/cci">CCI-001405</ident>
+            <ident system="http://cyber.mil/cci">CCI-002130</ident>
+            <fixtext fixref="F-57739r848724_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Account Management &gt;&gt;  Audit Security Group Management with "Success" selected.</fixtext>
+            <fix id="F-57739r848724_fix" />
+            <check system="C-57788r848723_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Account Management &gt;&gt; Security Group Management - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254304">
+        <title>SRG-OS-000004-GPOS-00004</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254304r958368_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000110</version>
+            <title>Windows Server 2022 must be configured to audit Account Management - User Account Management successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts.
+
+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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000018</ident>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-001403</ident>
+            <ident system="http://cyber.mil/cci">CCI-001404</ident>
+            <ident system="http://cyber.mil/cci">CCI-001405</ident>
+            <ident system="http://cyber.mil/cci">CCI-002130</ident>
+            <fixtext fixref="F-57740r848727_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Account Management &gt;&gt; Audit User Account Management with "Success" selected.</fixtext>
+            <fix id="F-57740r848727_fix" />
+            <check system="C-57789r848726_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Account Management &gt;&gt; User Account Management - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254305">
+        <title>SRG-OS-000004-GPOS-00004</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254305r958368_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000120</version>
+            <title>Windows Server 2022 must be configured to audit Account Management - User Account Management failures.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+User Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts.
+
+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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000018</ident>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-001403</ident>
+            <ident system="http://cyber.mil/cci">CCI-001404</ident>
+            <ident system="http://cyber.mil/cci">CCI-001405</ident>
+            <ident system="http://cyber.mil/cci">CCI-002130</ident>
+            <fixtext fixref="F-57741r848730_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Account Management &gt;&gt; Audit User Account Management with "Failure" selected.</fixtext>
+            <fix id="F-57741r848730_fix" />
+            <check system="C-57790r848729_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Account Management &gt;&gt; User Account Management - Failure</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254306">
+        <title>SRG-OS-000474-GPOS-00219</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254306r991583_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000130</version>
+            <title>Windows Server 2022 must be configured to audit Detailed Tracking - Plug and Play Events successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Plug and Play activity records events related to the successful connection of external devices.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <fixtext fixref="F-57742r848733_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Detailed Tracking &gt;&gt; Audit PNP Activity with "Success" selected.</fixtext>
+            <fix id="F-57742r848733_fix" />
+            <check system="C-57791r848732_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Detailed Tracking &gt;&gt; Plug and Play Events - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254307">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254307r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000140</version>
+            <title>Windows Server 2022 must be configured to audit Detailed Tracking - Process Creation successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Process Creation records events related to the creation of a process and the source.
+
+Satisfies: SRG-OS-000327-GPOS-00127, 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57743r848736_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Detailed Tracking &gt;&gt; Audit Process Creation with "Success" selected.</fixtext>
+            <fix id="F-57743r848736_fix" />
+            <check system="C-57792r848735_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Detailed Tracking &gt;&gt; Process Creation - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254309">
+        <title>SRG-OS-000240-GPOS-00090</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254309r991552_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000160</version>
+            <title>Windows Server 2022 must be configured to audit Logon/Logoff - Account Lockout failures.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Account Lockout events can be used to identify potentially malicious logon attempts.
+
+Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-001404</ident>
+            <fixtext fixref="F-57745r848742_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Logon/Logoff &gt;&gt; Audit Account Lockout with "Failure" selected.</fixtext>
+            <fix id="F-57745r848742_fix" />
+            <check system="C-57794r848741_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Logon/Logoff &gt;&gt; Account Lockout - Failure</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254310">
+        <title>SRG-OS-000470-GPOS-00214</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254310r991578_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000170</version>
+            <title>Windows Server 2022 must be configured to audit Logon/Logoff - Group Membership successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Audit Group Membership records information related to the group membership of a user's logon token.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <fixtext fixref="F-57746r848745_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Logon/Logoff &gt;&gt; Audit Group Membership with "Success" selected.</fixtext>
+            <fix id="F-57746r848745_fix" />
+            <check system="C-57795r848744_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Logon/Logoff &gt;&gt; Group Membership - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254311">
+        <title>SRG-OS-000472-GPOS-00217</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254311r991581_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000180</version>
+            <title>Windows Server 2022 must be configured to audit logoff successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Logoff records user logoffs. If this is an interactive logoff, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <fixtext fixref="F-57747r848748_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Logon/Logoff &gt;&gt; Audit Logoff with "Success" selected.</fixtext>
+            <fix id="F-57747r848748_fix" />
+            <check system="C-57796r848747_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Logon/Logoff &gt;&gt; Logoff - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254312">
+        <title>SRG-OS-000032-GPOS-00013</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254312r958406_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000190</version>
+            <title>Windows Server 2022 must be configured to audit logon successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Logon records user logons. If this is an interactive logon, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.
+
+Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000067</ident>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <fixtext fixref="F-57748r848751_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Logon/Logoff &gt;&gt; Audit Logon with "Success" selected.</fixtext>
+            <fix id="F-57748r848751_fix" />
+            <check system="C-57797r848750_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Logon/Logoff &gt;&gt; Logon - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254313">
+        <title>SRG-OS-000032-GPOS-00013</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254313r958406_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000200</version>
+            <title>Windows Server 2022 must be configured to audit logon failures.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Logon records user logons. If this is an interactive logon, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.
+
+Satisfies: SRG-OS-000032-GPOS-00013, SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000067</ident>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <fixtext fixref="F-57749r848754_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Logon/Logoff &gt;&gt; Audit Logon with "Failure" selected.</fixtext>
+            <fix id="F-57749r848754_fix" />
+            <check system="C-57798r848753_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Logon/Logoff &gt;&gt; Logon - Failure</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254314">
+        <title>SRG-OS-000470-GPOS-00214</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254314r991578_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000210</version>
+            <title>Windows Server 2022 must be configured to audit Logon/Logoff - Special Logon successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Special Logon records special logons that have administrative privileges and can be used to elevate processes.
+
+Satisfies: SRG-OS-000470-GPOS-00214, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000475-GPOS-00220&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <fixtext fixref="F-57750r848757_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Logon/Logoff &gt;&gt; Audit Special Logon with "Success" selected.</fixtext>
+            <fix id="F-57750r848757_fix" />
+            <check system="C-57799r848756_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Logon/Logoff &gt;&gt; Special Logon - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254315">
+        <title>SRG-OS-000470-GPOS-00214</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254315r991578_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000220</version>
+            <title>Windows Server 2022 must be configured to audit Object Access - Other Object Access Events successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <fixtext fixref="F-57751r848760_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Object Access &gt;&gt; Audit Other Object Access Events with "Success" selected.</fixtext>
+            <fix id="F-57751r848760_fix" />
+            <check system="C-57800r848759_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective.
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Object Access &gt;&gt; Other Object Access Events - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254316">
+        <title>SRG-OS-000470-GPOS-00214</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254316r991578_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000230</version>
+            <title>Windows Server 2022 must be configured to audit Object Access - Other Object Access Events failures.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Auditing for other object access records events related to the management of task scheduler jobs and COM+ objects.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <fixtext fixref="F-57752r848763_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Object Access &gt;&gt; Audit Other Object Access Events with "Failure" selected.</fixtext>
+            <fix id="F-57752r848763_fix" />
+            <check system="C-57801r848762_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective.
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Object Access &gt;&gt; Other Object Access Events - Failure</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254317">
+        <title>SRG-OS-000474-GPOS-00219</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254317r991583_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000240</version>
+            <title>Windows Server 2022 must be configured to audit Object Access - Removable Storage successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Removable Storage auditing under Object Access records events related to access attempts on file system objects on removable storage devices.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <fixtext fixref="F-57753r848766_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Object Access &gt;&gt; Audit Removable Storage with "Success" selected.</fixtext>
+            <fix id="F-57753r848766_fix" />
+            <check system="C-57802r848765_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Object Access &gt;&gt; Removable Storage - Success
+
+Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254318">
+        <title>SRG-OS-000474-GPOS-00219</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254318r991583_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000250</version>
+            <title>Windows Server 2022 must be configured to audit Object Access - Removable Storage failures.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Removable Storage auditing under Object Access records events related to access attempts on file system objects on removable storage devices.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <fixtext fixref="F-57754r848769_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Object Access &gt;&gt; Audit Removable Storage with "Failure" selected.</fixtext>
+            <fix id="F-57754r848769_fix" />
+            <check system="C-57803r848768_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Object Access &gt;&gt; Removable Storage - Failure
+
+Virtual machines or systems that use network attached storage may generate excessive audit events for secondary virtual drives or the network attached storage when this setting is enabled. This may be set to Not Configured in such cases and would not be a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254319">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254319r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000260</version>
+            <title>Windows Server 2022 must be configured to audit Policy Change - Audit Policy Change successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Audit Policy Change records events related to changes in audit policy.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57755r848772_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Policy Change &gt;&gt; Audit Audit Policy Change with "Success" selected.</fixtext>
+            <fix id="F-57755r848772_fix" />
+            <check system="C-57804r848771_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Policy Change &gt;&gt; Audit Audit Policy Change - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254320">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254320r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000270</version>
+            <title>Windows Server 2022 must be configured to audit Policy Change - Audit Policy Change failures.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Audit Policy Change records events related to changes in audit policy.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57756r848775_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Policy Change &gt;&gt; Audit Audit Policy Change with "Failure" selected.</fixtext>
+            <fix id="F-57756r848775_fix" />
+            <check system="C-57805r848774_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Policy Change &gt;&gt; Audit Audit Policy Change - Failure</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254321">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254321r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000280</version>
+            <title>Windows Server 2022 must be configured to audit Policy Change - Authentication Policy Change successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Authentication Policy Change records events related to changes in authentication policy, including Kerberos policy and Trust changes.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57757r848778_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Policy Change &gt;&gt; Audit Authentication Policy Change with "Success" selected.</fixtext>
+            <fix id="F-57757r848778_fix" />
+            <check system="C-57806r848777_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Policy Change &gt;&gt; Authentication Policy Change - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254322">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254322r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000290</version>
+            <title>Windows Server 2022 must be configured to audit Policy Change - Authorization Policy Change successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Authorization Policy Change records events related to changes in user rights, such as "Create a token object".
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57758r848781_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Policy Change &gt;&gt; Audit Authorization Policy Change with "Success" selected.</fixtext>
+            <fix id="F-57758r848781_fix" />
+            <check system="C-57807r848780_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Policy Change &gt;&gt; Authorization Policy Change - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254323">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254323r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000300</version>
+            <title>Windows Server 2022 must be configured to audit Privilege Use - Sensitive Privilege Use successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Sensitive Privilege Use records events related to use of sensitive privileges, such as "Act as part of the operating system" or "Debug programs".
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57759r848784_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Privilege Use &gt;&gt; Audit Sensitive Privilege Use with "Success" selected.</fixtext>
+            <fix id="F-57759r848784_fix" />
+            <check system="C-57808r848783_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Privilege Use &gt;&gt; Sensitive Privilege Use - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254324">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254324r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000310</version>
+            <title>Windows Server 2022 must be configured to audit Privilege Use - Sensitive Privilege Use failures.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Sensitive Privilege Use records events related to use of sensitive privileges, such as "Act as part of the operating system" or "Debug programs".
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206, SRG-OS-000466-GPOS-00210&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57760r848787_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Privilege Use &gt;&gt; Audit Sensitive Privilege Use with "Failure" selected.</fixtext>
+            <fix id="F-57760r848787_fix" />
+            <check system="C-57809r848786_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Privilege Use &gt;&gt; Sensitive Privilege Use - Failure</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254325">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254325r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000320</version>
+            <title>Windows Server 2022 must be configured to audit System - IPsec Driver successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+IPsec Driver records events related to the IPsec Driver, such as dropped packets.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57761r848790_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; System &gt;&gt; Audit IPsec Driver with "Success" selected.</fixtext>
+            <fix id="F-57761r848790_fix" />
+            <check system="C-57810r848789_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+System &gt;&gt; IPsec Driver - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254326">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254326r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000330</version>
+            <title>Windows Server 2022 must be configured to audit System - IPsec Driver failures.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+IPsec Driver records events related to the IPsec Driver, such as dropped packets.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57762r848793_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; System &gt;&gt; Audit IPsec Driver with "Failure" selected.</fixtext>
+            <fix id="F-57762r848793_fix" />
+            <check system="C-57811r848792_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+System &gt;&gt; IPsec Driver - Failure</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254327">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254327r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000340</version>
+            <title>Windows Server 2022 must be configured to audit System - Other System Events successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57763r848796_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; System &gt;&gt; Audit Other System Events with "Success" selected.</fixtext>
+            <fix id="F-57763r848796_fix" />
+            <check system="C-57812r848795_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+System &gt;&gt; Other System Events - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254328">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254328r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000350</version>
+            <title>Windows Server 2022 must be configured to audit System - Other System Events failures.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Audit Other System Events records information related to cryptographic key operations and the Windows Firewall service.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57764r848799_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; System &gt;&gt; Audit Other System Events with "Failure" selected.</fixtext>
+            <fix id="F-57764r848799_fix" />
+            <check system="C-57813r848798_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+System &gt;&gt; Other System Events - Failure</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254329">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254329r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000360</version>
+            <title>Windows Server 2022 must be configured to audit System - Security State Change successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Security State Change records events related to changes in the security state, such as startup and shutdown of the system.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57765r848802_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; System &gt;&gt; Audit Security State Chang with "Success" selected.</fixtext>
+            <fix id="F-57765r848802_fix" />
+            <check system="C-57814r848801_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+System &gt;&gt; Security State Change - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254330">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254330r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000370</version>
+            <title>Windows Server 2022 must be configured to audit System - Security System Extension successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Security System Extension records events related to extension code being loaded by the security subsystem.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57766r848805_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; System &gt;&gt; Audit Security System Extension with "Success" selected.</fixtext>
+            <fix id="F-57766r848805_fix" />
+            <check system="C-57815r848804_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+System &gt;&gt; Security System Extension - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254331">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254331r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000380</version>
+            <title>Windows Server 2022 must be configured to audit System - System Integrity successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+System Integrity records events related to violations of integrity to the security subsystem.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57767r848808_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; System &gt;&gt; Audit System Integrity with "Success" selected.</fixtext>
+            <fix id="F-57767r848808_fix" />
+            <check system="C-57816r848807_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+System &gt;&gt; System Integrity - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254332">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254332r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-AU-000390</version>
+            <title>Windows Server 2022 must be configured to audit System - System Integrity failures.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+System Integrity records events related to violations of integrity to the security subsystem.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000477-GPOS-00222&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57768r848811_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; System &gt;&gt; Audit System Integrity with "Failure" selected.</fixtext>
+            <fix id="F-57768r848811_fix" />
+            <check system="C-57817r848810_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+System &gt;&gt; System Integrity - Failure</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254333">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254333r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000010</version>
+            <title>Windows Server 2022 must prevent the display of slide shows on the lock screen.</title>
+            <description>&lt;VulnDiscussion&gt;Slide shows that are displayed on the lock screen could display sensitive information to unauthorized personnel. Turning off this feature will limit access to the information to a logged-on 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57769r848814_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Control Panel &gt;&gt; Personalization &gt;&gt; Prevent enabling lock screen slide show to "Enabled".</fixtext>
+            <fix id="F-57769r848814_fix" />
+            <check system="C-57818r848813_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the registry value below. 
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Personalization\
+
+Value Name: NoLockScreenSlideshow
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254334">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254334r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000020</version>
+            <title>Windows Server 2022 must have WDigest Authentication disabled.</title>
+            <description>&lt;VulnDiscussion&gt;When the WDigest Authentication protocol is enabled, plain-text passwords are stored in the Local Security Authority Subsystem Service (LSASS), exposing them to theft. WDigest is disabled by default in Windows Server 2022. This setting ensures this is enforced.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57770r848817_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; MS Security Guide . Set "WDigest Authentication (disabling may require KB2871997)" to "Disabled".
+
+This policy setting requires the installation of the SecGuide custom templates included with the STIG package. "SecGuide.admx" and " SecGuide.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.</fixtext>
+            <fix id="F-57770r848817_fix" />
+            <check system="C-57819r848816_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive:  HKEY_LOCAL_MACHINE
+Registry Path:  \SYSTEM\CurrentControlSet\Control\SecurityProviders\Wdigest\
+
+Value Name:  UseLogonCredential
+
+Type:  REG_DWORD
+Value:  0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254335">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254335r991589_rule" weight="10.0" severity="low">
+            <version>WN22-CC-000030</version>
+            <title>Windows Server 2022 Internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing.</title>
+            <description>&lt;VulnDiscussion&gt;Configuring the system to disable IPv6 source routing protects against spoofing.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57771r848820_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; MSS (Legacy) &gt;&gt; MSS: (DisableIPSourceRouting IPv6) IP source routing protection level (protects against packet spoofing) to "Enabled" with "Highest protection, source routing is completely disabled" selected.
+
+This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.</fixtext>
+            <fix id="F-57771r848820_fix" />
+            <check system="C-57820r848819_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
+
+Value Name: DisableIPSourceRouting
+
+Type: REG_DWORD
+Value: 0x00000002 (2)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254336">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254336r991589_rule" weight="10.0" severity="low">
+            <version>WN22-CC-000040</version>
+            <title>Windows Server 2022 source routing must be configured to the highest protection level to prevent Internet Protocol (IP) source routing.</title>
+            <description>&lt;VulnDiscussion&gt;Configuring the system to disable IP source routing protects against spoofing.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57772r848823_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; MSS (Legacy) &gt;&gt; MSS: (DisableIPSourceRouting) IP source routing protection level (protects against packet spoofing) to "Enabled" with "Highest protection, source routing is completely disabled" selected.
+
+This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.</fixtext>
+            <fix id="F-57772r848823_fix" />
+            <check system="C-57821r848822_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
+
+Value Name: DisableIPSourceRouting
+
+Value Type: REG_DWORD
+Value: 0x00000002 (2)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254337">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254337r991589_rule" weight="10.0" severity="low">
+            <version>WN22-CC-000050</version>
+            <title>Windows Server 2022 must be configured to prevent Internet Control Message Protocol (ICMP) redirects from overriding Open Shortest Path First (OSPF)-generated routes.</title>
+            <description>&lt;VulnDiscussion&gt;Allowing ICMP redirect of routes can lead to traffic not being routed properly. When disabled, this forces ICMP to be routed via the shortest path first.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57773r848826_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; MSS (Legacy) &gt;&gt; MSS: (EnableICMPRedirect) Allow ICMP redirects to override OSPF generated routes to "Disabled".
+
+This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.</fixtext>
+            <fix id="F-57773r848826_fix" />
+            <check system="C-57822r848825_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
+
+Value Name: EnableICMPRedirect
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254338">
+        <title>SRG-OS-000420-GPOS-00186</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254338r958902_rule" weight="10.0" severity="low">
+            <version>WN22-CC-000060</version>
+            <title>Windows Server 2022 must be configured to ignore NetBIOS name release requests except from WINS servers.</title>
+            <description>&lt;VulnDiscussion&gt;Configuring the system to ignore name release requests, except from WINS servers, prevents a denial of service (DoS) attack. The DoS consists of sending a NetBIOS name release request to the server for each entry in the server's cache, causing a response delay in the normal operation of the server's WINS resolution 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002385</ident>
+            <fixtext fixref="F-57774r848829_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; MSS (Legacy) &gt;&gt; MSS: (NoNameReleaseOnDemand) Allow the computer to ignore NetBIOS name release requests except from WINS servers to "Enabled".
+
+This policy setting requires the installation of the MSS-Legacy custom templates included with the STIG package. "MSS-Legacy.admx" and "MSS-Legacy.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.</fixtext>
+            <fix id="F-57774r848829_fix" />
+            <check system="C-57823r848828_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive:  HKEY_LOCAL_MACHINE
+Registry Path:  \SYSTEM\CurrentControlSet\Services\Netbt\Parameters\
+
+Value Name:  NoNameReleaseOnDemand
+
+Value Type:  REG_DWORD
+Value:  0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254339">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254339r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000070</version>
+            <title>Windows Server 2022 insecure logons to an SMB server must be disabled.</title>
+            <description>&lt;VulnDiscussion&gt;Insecure guest logons allow unauthenticated access to shared folders. Shared resources on a system must require authentication to establish proper 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57775r848832_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Network &gt;&gt; Lanman Workstation &gt;&gt; Enable insecure guest logons to "Disabled".</fixtext>
+            <fix id="F-57775r848832_fix" />
+            <check system="C-57824r848831_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation\
+
+Value Name: AllowInsecureGuestAuth
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254340">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254340r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000080</version>
+            <title>Windows Server 2022 hardened Universal Naming Convention (UNC) paths must be defined to require mutual authentication and integrity for at least the \\*\SYSVOL and \\*\NETLOGON shares.</title>
+            <description>&lt;VulnDiscussion&gt;Additional security requirements are applied to UNC paths specified in hardened UNC paths before allowing access to them. This aids in preventing tampering with or spoofing of connections to these paths.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57776r848835_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Network &gt;&gt; Network Provider &gt;&gt; Hardened UNC Paths" to "Enabled" with at least the following configured in "Hardened UNC Paths" (click the "Show" button to display):
+
+Value Name: \\*\SYSVOL
+Value: RequireMutualAuthentication=1, RequireIntegrity=1
+
+Value Name: \\*\NETLOGON
+Value: RequireMutualAuthentication=1, RequireIntegrity=1</fixtext>
+            <fix id="F-57776r848835_fix" />
+            <check system="C-57825r848834_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This requirement is applicable to domain-joined systems. For standalone or nondomain-joined systems, this is NA.
+
+If the following registry values do not exist or are not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\
+
+Value Name: \\*\NETLOGON
+Value Type: REG_SZ
+Value: RequireMutualAuthentication=1, RequireIntegrity=1
+
+Value Name: \\*\SYSVOL
+Value Type: REG_SZ
+Value: RequireMutualAuthentication=1, RequireIntegrity=1
+
+Additional entries would not be a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254341">
+        <title>SRG-OS-000042-GPOS-00020</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254341r958422_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000090</version>
+            <title>Windows Server 2022 command line data must be included in process creation events.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Enabling "Include command line data for process creation events" will record the command line information with the process creation events in the log. This can provide additional detail when malware has run on 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;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000135</ident>
+            <fixtext fixref="F-57777r848838_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Audit Process Creation &gt;&gt; Include command line in process creation events to "Enabled".</fixtext>
+            <fix id="F-57777r848838_fix" />
+            <check system="C-57826r848837_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit\
+
+Value Name: ProcessCreationIncludeCmdLine_Enabled
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254342">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254342r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000100</version>
+            <title>Windows Server 2022 must be configured to enable Remote host allows delegation of nonexportable credentials.</title>
+            <description>&lt;VulnDiscussion&gt;An exportable version of credentials is provided to remote hosts when using credential delegation which exposes them to theft on the remote host. Restricted Admin mode or Remote Credential Guard allow delegation of nonexportable credentials providing additional protection of the credentials. Enabling this configures the host to support Restricted Admin mode or Remote Credential Guard.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57778r848841_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Credentials Delegation &gt;&gt; Remote host allows delegation of nonexportable credentials to "Enabled".</fixtext>
+            <fix id="F-57778r848841_fix" />
+            <check system="C-57827r848840_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\
+
+Value Name: AllowProtectedCreds
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254343">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254343r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000110</version>
+            <title>Windows Server 2022 virtualization-based security must be enabled with the platform security level configured to Secure Boot or Secure Boot with DMA Protection.</title>
+            <description>&lt;VulnDiscussion&gt;Virtualization Based Security (VBS) provides the platform for the additional security features Credential Guard and virtualization-based protection of code integrity. Secure Boot is the minimum security level, with DMA protection providing additional memory protection. DMA Protection requires a CPU that supports input/output memory management unit (IOMMU).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57779r848844_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Device Guard &gt;&gt; Turn On Virtualization Based Security to "Enabled" with "Secure Boot" or "Secure Boot and DMA Protection" selected.
+
+A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link:
+
+https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard</fixtext>
+            <fix id="F-57779r848844_fix" />
+            <check system="C-57828r848843_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>For standalone or nondomain-joined systems, this is NA.
+
+Open "PowerShell" with elevated privileges (run as administrator).
+
+Enter the following:
+
+"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard"
+
+If "RequiredSecurityProperties" does not include a value of "2" indicating "Secure Boot" (e.g., "{1, 2}"), this is a finding.
+
+If "Secure Boot and DMA Protection" is configured, "3" will also be displayed in the results (e.g., "{1, 2, 3}").
+
+If "VirtualizationBasedSecurityStatus" is not a value of "2" indicating "Running", this is a finding.
+
+Alternately:
+
+Run "System Information".
+
+Under "System Summary", verify the following:
+
+If "Device Guard Virtualization based security" does not display "Running", this is a finding.
+
+If "Device Guard Required Security Properties" does not display "Base Virtualization Support, Secure Boot", this is a finding.
+
+If "Secure Boot and DMA Protection" is configured, "DMA Protection" will also be displayed (e.g., "Base Virtualization Support, Secure Boot, DMA Protection").
+
+The policy settings referenced in the Fix section will configure the following registry values; however, due to hardware requirements, the registry values alone do not ensure proper function.
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\
+
+Value Name: EnableVirtualizationBasedSecurity
+Value Type: REG_DWORD
+Value: 0x00000001 (1)
+
+Value Name: RequirePlatformSecurityFeatures
+Value Type: REG_DWORD
+Value: 0x00000001 (1) (Secure Boot only) or 0x00000003 (3) (Secure Boot and DMA Protection)
+
+A Microsoft TechNet article on Credential Guard, including system requirement details, can be found at the following link:
+
+https://technet.microsoft.com/itpro/windows/keep-secure/credential-guard</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254344">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254344r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000130</version>
+            <title>Windows Server 2022 Early Launch Antimalware, Boot-Start Driver Initialization Policy must prevent boot drivers identified as bad.</title>
+            <description>&lt;VulnDiscussion&gt;Compromised boot drivers can introduce malware prior to protection mechanisms that load after initialization. The Early Launch Antimalware driver can limit allowed drivers based on classifications determined by the malware protection application. At a minimum, drivers determined to be bad must not be allowed.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57780r848847_fix">The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad").
+
+If this needs to be corrected or a more secure setting is desired, configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Early Launch Antimalware &gt;&gt; Boot-Start Driver Initialization Policy to "Not Configured" or "Enabled" with any option other than "All" selected.</fixtext>
+            <fix id="F-57780r848847_fix" />
+            <check system="C-57829r848846_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy to enforce "Good, unknown and bad but critical" (preventing "bad").
+
+If the registry value name below does not exist, this is not a finding.
+
+If it exists and is configured with a value of "0x00000007 (7)", this is a finding.
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SYSTEM\CurrentControlSet\Policies\EarlyLaunch\
+
+Value Name: DriverLoadPolicy
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1), 0x00000003 (3), or 0x00000008 (8) (or if the Value Name does not exist)
+
+Possible values for this setting are:
+8 - Good only
+1 - Good and unknown
+3 - Good, unknown and bad but critical
+7 - All (which includes "bad" and would be a finding)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254345">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254345r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000140</version>
+            <title>Windows Server 2022 group policy objects must be reprocessed even if they have not changed.</title>
+            <description>&lt;VulnDiscussion&gt;Registry entries for group policy settings can potentially be changed from the required configuration. This could occur as part of troubleshooting or by a malicious process on a compromised system. Enabling this setting and then selecting the "Process even if the Group Policy objects have not changed" option ensures the policies will be reprocessed even if none have been changed. This way, any unauthorized changes are forced to match the domain-based group policy settings again.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57781r848850_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Group Policy &gt;&gt; Configure registry policy processing to "Enabled" with the option "Process even if the Group Policy objects have not changed" selected.</fixtext>
+            <fix id="F-57781r848850_fix" />
+            <check system="C-57830r848849_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}\
+
+Value Name: NoGPOListChanges
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254346">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254346r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000150</version>
+            <title>Windows Server 2022 downloading print driver packages over HTTP must be turned off.</title>
+            <description>&lt;VulnDiscussion&gt;Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and will prevent uncontrolled updates to the system. 
+
+This setting prevents the computer from downloading print driver packages over HTTP.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57782r848853_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Internet Communication Management &gt;&gt; Internet Communication settings &gt;&gt; Turn off downloading of print drivers over HTTP to "Enabled".</fixtext>
+            <fix id="F-57782r848853_fix" />
+            <check system="C-57831r848852_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\
+
+Value Name: DisableWebPnPDownload
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254347">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254347r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000160</version>
+            <title>Windows Server 2022 printing over HTTP must be turned off.</title>
+            <description>&lt;VulnDiscussion&gt;Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and will prevent uncontrolled updates to the system.
+
+This setting prevents the client computer from printing over HTTP, which allows the computer to print to printers on the intranet as well as the internet.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57783r848856_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Internet Communication Management &gt;&gt; Internet Communication settings &gt;&gt; Turn off printing over HTTP to "Enabled".</fixtext>
+            <fix id="F-57783r848856_fix" />
+            <check system="C-57832r848855_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Printers\
+
+Value Name: DisableHTTPPrinting
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254348">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254348r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000170</version>
+            <title>Windows Server 2022 network selection user interface (UI) must not be displayed on the logon screen.</title>
+            <description>&lt;VulnDiscussion&gt;Enabling interaction with the network selection UI allows users to change connections to available networks without signing in to Windows.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57784r848859_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Logon &gt;&gt; Do not display network selection UI to "Enabled".</fixtext>
+            <fix id="F-57784r848859_fix" />
+            <check system="C-57833r848858_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the registry value below. If it does not exist or is not configured as specified, this is a finding.
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\
+
+Value Name: DontDisplayNetworkSelectionUI
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254349">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254349r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000180</version>
+            <title>Windows Server 2022 users must be prompted to authenticate when the system wakes from sleep (on battery).</title>
+            <description>&lt;VulnDiscussion&gt;A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes from sleep (on battery).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57785r848862_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Power Management &gt;&gt; Sleep Settings &gt;&gt; Require a password when a computer wakes (on battery) to "Enabled".</fixtext>
+            <fix id="F-57785r848862_fix" />
+            <check system="C-57834r848861_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\
+
+Value Name: DCSettingIndex
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254350">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254350r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000190</version>
+            <title>Windows Server 2022 users must be prompted to authenticate when the system wakes from sleep (plugged in).</title>
+            <description>&lt;VulnDiscussion&gt;A system that does not require authentication when resuming from sleep may provide access to unauthorized users. Authentication must always be required when accessing a system. This setting ensures users are prompted for a password when the system wakes from sleep (plugged in).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57786r848865_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Power Management &gt;&gt; Sleep Settings &gt;&gt; Require a password when a computer wakes (plugged in) to "Enabled".</fixtext>
+            <fix id="F-57786r848865_fix" />
+            <check system="C-57835r848864_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Power\PowerSettings\0e796bdb-100d-47d6-a2d5-f7d2daa51f51\
+
+Value Name: ACSettingIndex
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254351">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254351r958478_rule" weight="10.0" severity="low">
+            <version>WN22-CC-000200</version>
+            <title>Windows Server 2022 Application Compatibility Program Inventory must be prevented from collecting data and sending the information to Microsoft.</title>
+            <description>&lt;VulnDiscussion&gt;Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and will prevent uncontrolled updates to the system.
+
+This setting will prevent the Program Inventory from collecting data about a system and sending the information to Microsoft.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57787r848868_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Application Compatibility &gt;&gt; Turn off Inventory Collector to "Enabled".</fixtext>
+            <fix id="F-57787r848868_fix" />
+            <check system="C-57836r848867_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\AppCompat\
+
+Value Name: DisableInventory
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254352">
+        <title>SRG-OS-000368-GPOS-00154</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254352r958804_rule" weight="10.0" severity="high">
+            <version>WN22-CC-000210</version>
+            <title>Windows Server 2022 Autoplay must be turned off for nonvolume devices.</title>
+            <description>&lt;VulnDiscussion&gt;Allowing AutoPlay to execute may introduce malicious code to a system. AutoPlay begins reading from a drive as soon as media is inserted into the drive. As a result, the setup file of programs or music on audio media may start. This setting will disable AutoPlay for nonvolume devices, such as Media Transfer Protocol (MTP) devices.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001764</ident>
+            <fixtext fixref="F-57788r848871_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; AutoPlay Policies &gt;&gt; Disallow Autoplay for nonvolume devices to "Enabled".</fixtext>
+            <fix id="F-57788r848871_fix" />
+            <check system="C-57837r848870_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\
+
+Value Name: NoAutoplayfornonVolume
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254353">
+        <title>SRG-OS-000368-GPOS-00154</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254353r958804_rule" weight="10.0" severity="high">
+            <version>WN22-CC-000220</version>
+            <title>Windows Server 2022 default AutoRun behavior must be configured to prevent AutoRun commands.</title>
+            <description>&lt;VulnDiscussion&gt;Allowing AutoRun commands to execute may introduce malicious code to a system. Configuring this setting prevents AutoRun commands from executing.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001764</ident>
+            <fixtext fixref="F-57789r848874_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; AutoPlay Policies &gt;&gt; Set the default behavior for AutoRun to "Enabled" with "Do not execute any autorun commands" selected.</fixtext>
+            <fix id="F-57789r848874_fix" />
+            <check system="C-57838r848873_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\
+
+Value Name: NoAutorun
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254354">
+        <title>SRG-OS-000368-GPOS-00154</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254354r958804_rule" weight="10.0" severity="high">
+            <version>WN22-CC-000230</version>
+            <title>Windows Server 2022 AutoPlay must be disabled for all drives.</title>
+            <description>&lt;VulnDiscussion&gt;Allowing AutoPlay to execute may introduce malicious code to a system. AutoPlay begins reading from a drive as soon media is inserted into the drive. As a result, the setup file of programs or music on audio media may start. By default, AutoPlay is disabled on removable drives, such as the floppy disk drive (but not the CD-ROM drive) and on network drives. Enabling this policy disables AutoPlay on all drives.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001764</ident>
+            <fixtext fixref="F-57790r848877_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; AutoPlay Policies &gt;&gt; Turn off AutoPlay to "Enabled" with "All Drives" selected.</fixtext>
+            <fix id="F-57790r848877_fix" />
+            <check system="C-57839r848876_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path:  \SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\
+
+Value Name: NoDriveTypeAutoRun
+
+Type: REG_DWORD
+Value: 0x000000ff (255)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254355">
+        <title>SRG-OS-000134-GPOS-00068</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254355r958518_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000240</version>
+            <title>Windows Server 2022 administrator accounts must not be enumerated during elevation.</title>
+            <description>&lt;VulnDiscussion&gt;Enumeration of administrator accounts when elevating can provide part of the logon information to an unauthorized user. This setting configures the system to always require users to type in a username and password to elevate a running application.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001084</ident>
+            <fixtext fixref="F-57791r848880_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Credential User Interface &gt;&gt; Enumerate administrator accounts on elevation to "Disabled".</fixtext>
+            <fix id="F-57791r848880_fix" />
+            <check system="C-57840r848879_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI\
+
+Value Name: EnumerateAdministrators
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254356">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254356r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000250</version>
+            <title>Windows Server 2022 Diagnostic Data must be configured to send "required diagnostic data" or "optional diagnostic data".</title>
+            <description>&lt;VulnDiscussion&gt;Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Limiting this capability will prevent potentially sensitive information from being sent outside the enterprise. The "send required diagnostic data" option for Allow Diagnostic Data configures the lowest amount of data, effectively none outside of the Malicious Software Removal Tool (MSRT), Defender, and Diagnostic Data client settings. "Optional Diagnostic Data" sends basic diagnostic and usage data and may be required to support some Microsoft 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57792r902887_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Data Collection and Preview Build &gt;&gt; Allow Diagnostic Data to "Enabled" with "Send required diagnostic data" selected or "Send optional diagnostic data".</fixtext>
+            <fix id="F-57792r902887_fix" />
+            <check system="C-57841r916219_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DataCollection\
+
+Value Name: AllowTelemetry
+
+Type: REG_DWORD
+Value:  0x00000001 (1), 0x00000003 (3)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254357">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254357r991589_rule" weight="10.0" severity="low">
+            <version>WN22-CC-000260</version>
+            <title>Windows Server 2022 Windows Update must not obtain updates from other PCs on the internet.</title>
+            <description>&lt;VulnDiscussion&gt;Windows Update can obtain updates from additional sources instead of Microsoft. In addition to Microsoft, updates can be obtained from and sent to PCs on the local network as well as on the internet. This is part of the Windows Update trusted process; however, to minimize outside exposure, obtaining updates from or sending to systems on the internet must be prevented.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57793r890544_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Delivery Optimization &gt;&gt; Download Mode to "Enabled" with any option except "Internet" selected.
+
+Acceptable selections include:
+
+HTTP only (0)
+LAN (1)
+Group (2)
+Internet (3)
+Simple (99)</fixtext>
+            <fix id="F-57793r890544_fix" />
+            <check system="C-57842r890543_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization\
+
+Value Name: DODownloadMode
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0) - No peering (HTTP Only)
+0x00000001 (1) - Peers on same NAT only (LAN)
+0x00000002 (2) - Local Network / Private group peering (Group)
+0x00000063 (99) - Simple download mode, no peering (Simple)
+
+A value of 0x00000003 (3), Internet, is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254358">
+        <title>SRG-OS-000341-GPOS-00132</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254358r958752_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000270</version>
+            <title>Windows Server 2022 Application event log size must be configured to 32768 KB or greater.</title>
+            <description>&lt;VulnDiscussion&gt;Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001849</ident>
+            <fixtext fixref="F-57794r848889_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Event Log Service &gt;&gt; Application &gt;&gt; Specify the maximum log file size (KB) to "Enabled" with a "Maximum Log Size (KB)" of "32768" or greater.</fixtext>
+            <fix id="F-57794r848889_fix" />
+            <check system="C-57843r848888_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the system is configured to write events directly to an audit server, this is NA.
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Application\
+
+Value Name: MaxSize
+
+Type: REG_DWORD
+Value: 0x00008000 (32768) (or greater)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254359">
+        <title>SRG-OS-000341-GPOS-00132</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254359r958752_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000280</version>
+            <title>Windows Server 2022 Security event log size must be configured to 196608 KB or greater.</title>
+            <description>&lt;VulnDiscussion&gt;Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001849</ident>
+            <fixtext fixref="F-57795r848892_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Event Log Service &gt;&gt; Security &gt;&gt; Specify the maximum log file size (KB) to "Enabled" with a "Maximum Log Size (KB)" of "196608" or greater.</fixtext>
+            <fix id="F-57795r848892_fix" />
+            <check system="C-57844r848891_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the system is configured to write events directly to an audit server, this is NA.
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\Security\
+
+Value Name: MaxSize
+
+Type: REG_DWORD
+Value: 0x00030000 (196608) (or greater)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254360">
+        <title>SRG-OS-000341-GPOS-00132</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254360r958752_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000290</version>
+            <title>Windows Server 2022 System event log size must be configured to 32768 KB or greater.</title>
+            <description>&lt;VulnDiscussion&gt;Inadequate log size will cause the log to fill up quickly. This may prevent audit events from being recorded properly and require frequent attention by administrative 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001849</ident>
+            <fixtext fixref="F-57796r848895_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Event Log Service &gt;&gt; System &gt;&gt; Specify the maximum log file size (KB) to "Enabled" with a "Maximum Log Size (KB)" of "32768" or greater.</fixtext>
+            <fix id="F-57796r848895_fix" />
+            <check system="C-57845r848894_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the system is configured to write events directly to an audit server, this is NA.
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\EventLog\System\
+
+Value Name: MaxSize
+
+Type: REG_DWORD
+Value: 0x00008000 (32768) (or greater)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254361">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254361r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000300</version>
+            <title>Windows Server 2022 Microsoft Defender antivirus SmartScreen must be enabled.</title>
+            <description>&lt;VulnDiscussion&gt;Microsoft Defender antivirus SmartScreen helps protect systems from programs downloaded from the internet that may be malicious. Enabling SmartScreen can block potentially malicious programs or warn 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57797r848898_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; File Explorer &gt;&gt; Configure Windows Defender SmartScreen to "Enabled" with either option "Warn" or "Warn and prevent bypass" selected.
+
+Windows Server 2022 includes duplicate policies for this setting. It can also be configured under Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows Defender SmartScreen &gt;&gt; Explorer.</fixtext>
+            <fix id="F-57797r848898_fix" />
+            <check system="C-57846r848897_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This is applicable to unclassified systems; for other systems, this is NA.
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\
+
+Value Name: EnableSmartScreen
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254362">
+        <title>SRG-OS-000433-GPOS-00192</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254362r958928_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000310</version>
+            <title>Windows Server 2022 Explorer Data Execution Prevention must be enabled.</title>
+            <description>&lt;VulnDiscussion&gt;Data Execution Prevention provides additional protection by performing checks on memory to help prevent malicious code from running. This setting will prevent Data Execution Prevention from being turned off for File Explorer.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002824</ident>
+            <fixtext fixref="F-57798r848901_fix">The default behavior is for data execution prevention to be turned on for File Explorer.
+
+If this needs to be corrected, configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; File Explorer &gt;&gt; Turn off Data Execution Prevention for Explorer to "Not Configured" or "Disabled".</fixtext>
+            <fix id="F-57798r848901_fix" />
+            <check system="C-57847r848900_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>The default behavior is for Data Execution Prevention to be turned on for File Explorer.
+
+If the registry value name below does not exist, this is not a finding.
+
+If it exists and is configured with a value of "0", this is not a finding.
+
+If it exists and is configured with a value of "1", this is a finding.
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\
+
+Value Name: NoDataExecutionPrevention
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0) (or if the Value Name does not exist)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254363">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254363r991589_rule" weight="10.0" severity="low">
+            <version>WN22-CC-000320</version>
+            <title>Windows Server 2022 Turning off File Explorer heap termination on corruption must be disabled.</title>
+            <description>&lt;VulnDiscussion&gt;Legacy plug-in applications may continue to function when a File Explorer session has become corrupt. Disabling this feature will prevent this.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57799r848904_fix">The default behavior is for File Explorer heap termination on corruption to be disabled.
+
+If this needs to be corrected, configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; File Explorer &gt;&gt; Turn off heap termination on corruption to "Not Configured" or "Disabled".</fixtext>
+            <fix id="F-57799r848904_fix" />
+            <check system="C-57848r848903_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>The default behavior is for File Explorer heap termination on corruption to be enabled.
+
+If the registry Value Name below does not exist, this is not a finding.
+
+If it exists and is configured with a value of "0", this is not a finding.
+
+If it exists and is configured with a value of "1", this is a finding.
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Explorer\
+
+Value Name: NoHeapTerminationOnCorruption
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0) (or if the Value Name does not exist)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254364">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254364r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000330</version>
+            <title>Windows Server 2022 File Explorer shell protocol must run in protected mode.</title>
+            <description>&lt;VulnDiscussion&gt;The shell protocol will limit the set of folders that applications can open when run in protected mode. Restricting files an application can open to a limited set of folders increases the security of Windows.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57800r848907_fix">The default behavior is for shell protected mode to be turned on for File Explorer.
+
+If this needs to be corrected, configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; File Explorer &gt;&gt; Turn off shell protocol protected mode to "Not Configured" or "Disabled".</fixtext>
+            <fix id="F-57800r848907_fix" />
+            <check system="C-57849r848906_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>The default behavior is for shell protected mode to be turned on for File Explorer.
+
+If the registry value name below does not exist, this is not a finding.
+
+If it exists and is configured with a value of "0", this is not a finding.
+
+If it exists and is configured with a value of "1", this is a finding.
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\
+
+Value Name: PreXPSP2ShellProtocolBehavior
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0) (or if the Value Name does not exist)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254365">
+        <title>SRG-OS-000373-GPOS-00156</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254365r1000162_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000340</version>
+            <title>Windows Server 2022 must not save passwords in the Remote Desktop Client.</title>
+            <description>&lt;VulnDiscussion&gt;Saving passwords in the Remote Desktop Client could allow an unauthorized user to establish a remote desktop session to another system. The system must be configured to prevent users from saving passwords in the Remote Desktop Client.
+
+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004895</ident>
+            <fixtext fixref="F-57801r848910_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Remote Desktop Services &gt;&gt; Remote Desktop Connection Client &gt;&gt; Do not allow passwords to be saved to "Enabled".</fixtext>
+            <fix id="F-57801r848910_fix" />
+            <check system="C-57850r848909_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\
+
+Value Name: DisablePasswordSaving
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254366">
+        <title>SRG-OS-000138-GPOS-00069</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254366r958524_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000350</version>
+            <title>Windows Server 2022 Remote Desktop Services must prevent drive redirection.</title>
+            <description>&lt;VulnDiscussion&gt;Preventing users from sharing the local drives on their client computers with Remote Session Hosts that they access helps reduce possible exposure of sensitive data.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001090</ident>
+            <fixtext fixref="F-57802r848913_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Remote Desktop Services &gt;&gt; Remote Desktop Session Host &gt;&gt; Device and Resource Redirection &gt;&gt; Do not allow drive redirection to "Enabled".</fixtext>
+            <fix id="F-57802r848913_fix" />
+            <check system="C-57851r848912_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\
+
+Value Name: fDisableCdm
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254367">
+        <title>SRG-OS-000373-GPOS-00156</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254367r1000163_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000360</version>
+            <title>Windows Server 2022 Remote Desktop Services must always prompt a client for passwords upon connection.</title>
+            <description>&lt;VulnDiscussion&gt;This setting controls the ability of users to supply passwords automatically as part of their remote desktop connection. Disabling this setting would allow anyone to use the stored credentials in a connection item to connect to the terminal server.
+
+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004895</ident>
+            <fixtext fixref="F-57803r848916_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Remote Desktop Services &gt;&gt; Remote Desktop Session Host &gt;&gt; Security &gt;&gt; Always prompt for password upon connection to "Enabled".</fixtext>
+            <fix id="F-57803r848916_fix" />
+            <check system="C-57852r848915_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\
+
+Value Name: fPromptForPassword
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254368">
+        <title>SRG-OS-000033-GPOS-00014</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254368r958408_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000370</version>
+            <title>Windows Server 2022 Remote Desktop Services must require secure Remote Procedure Call (RPC) communications.</title>
+            <description>&lt;VulnDiscussion&gt;Allowing unsecure RPC communication exposes the system to man-in-the-middle attacks and data disclosure attacks. A man-in-the-middle attack occurs when an intruder captures packets between a client and server and modifies them before allowing the packets to be exchanged. Usually the attacker will modify the information in the packets in an attempt to cause either the client or server to reveal sensitive information.
+
+Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000068</ident>
+            <ident system="http://cyber.mil/cci">CCI-001453</ident>
+            <fixtext fixref="F-57804r848919_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Remote Desktop Services &gt;&gt; Remote Desktop Session Host &gt;&gt; Security &gt;&gt; Require secure RPC communication to "Enabled".</fixtext>
+            <fix id="F-57804r848919_fix" />
+            <check system="C-57853r848918_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\
+
+Value Name: fEncryptRPCTraffic
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254369">
+        <title>SRG-OS-000033-GPOS-00014</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254369r958408_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000380</version>
+            <title>Windows Server 2022 Remote Desktop Services must be configured with the client connection encryption set to High Level.</title>
+            <description>&lt;VulnDiscussion&gt;Remote connections must be encrypted to prevent interception of data or sensitive information. Selecting "High Level" will ensure encryption of Remote Desktop Services sessions in both directions.
+
+Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000068</ident>
+            <ident system="http://cyber.mil/cci">CCI-001453</ident>
+            <fixtext fixref="F-57805r848922_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Remote Desktop Services &gt;&gt; Remote Desktop Session Host &gt;&gt; Security &gt;&gt; Set client connection encryption level to "Enabled" with "High Level" selected.</fixtext>
+            <fix id="F-57805r848922_fix" />
+            <check system="C-57854r848921_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\
+
+Value Name: MinEncryptionLevel
+
+Type: REG_DWORD
+Value: 0x00000003 (3)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254370">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254370r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000390</version>
+            <title>Windows Server 2022 must prevent attachments from being downloaded from RSS feeds.</title>
+            <description>&lt;VulnDiscussion&gt;Attachments from RSS feeds may not be secure. This setting will prevent attachments from being downloaded from RSS feeds.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57806r848925_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; RSS Feeds &gt;&gt; Prevent downloading of enclosures to "Enabled".</fixtext>
+            <fix id="F-57806r848925_fix" />
+            <check system="C-57855r848924_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\
+
+Value Name: DisableEnclosureDownload
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254371">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254371r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000400</version>
+            <title>Windows Server 2022 must disable Basic authentication for RSS feeds over HTTP.</title>
+            <description>&lt;VulnDiscussion&gt;Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57807r848928_fix">The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections.
+
+If this needs to be corrected, configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; RSS Feeds &gt;&gt; Turn on Basic feed authentication over HTTP to "Not Configured" or "Disabled".</fixtext>
+            <fix id="F-57807r848928_fix" />
+            <check system="C-57856r848927_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>The default behavior is for the Windows RSS platform to not use Basic authentication over HTTP connections.
+
+If the registry value name below does not exist, this is not a finding.
+
+If it exists and is configured with a value of "0", this is not a finding.
+
+If it exists and is configured with a value of "1", this is a finding.
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Internet Explorer\Feeds\
+
+Value Name: AllowBasicAuthInClear
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0) (or if the Value Name does not exist)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254372">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254372r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000410</version>
+            <title>Windows Server 2022 must prevent Indexing of encrypted files.</title>
+            <description>&lt;VulnDiscussion&gt;Indexing of encrypted files may expose sensitive data. This setting prevents encrypted files from being indexed.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57808r848931_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Search &gt;&gt; Allow indexing of encrypted files to "Disabled".</fixtext>
+            <fix id="F-57808r848931_fix" />
+            <check system="C-57857r848930_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Windows Search\
+
+Value Name: AllowIndexingEncryptedStoresOrItems
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254373">
+        <title>SRG-OS-000362-GPOS-00149</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254373r1000164_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000420</version>
+            <title>Windows Server 2022 must prevent users from changing installation options.</title>
+            <description>&lt;VulnDiscussion&gt;Installation options for applications are typically controlled by administrators. This setting prevents users from changing installation options that may bypass security features.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-003980</ident>
+            <fixtext fixref="F-57809r848934_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows Installer &gt;&gt; Allow user control over installs to "Disabled".</fixtext>
+            <fix id="F-57809r848934_fix" />
+            <check system="C-57858r848933_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\
+
+Value Name: EnableUserControl
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254374">
+        <title>SRG-OS-000362-GPOS-00149</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254374r1000165_rule" weight="10.0" severity="high">
+            <version>WN22-CC-000430</version>
+            <title>Windows Server 2022 must disable the Windows Installer Always install with elevated privileges option.</title>
+            <description>&lt;VulnDiscussion&gt;Standard user accounts must not be granted elevated privileges. Enabling Windows Installer to elevate privileges when installing applications can allow malicious persons and applications to gain full control of 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;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-003980</ident>
+            <fixtext fixref="F-57810r848937_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows Installer &gt;&gt; Always install with elevated privileges to "Disabled".</fixtext>
+            <fix id="F-57810r848937_fix" />
+            <check system="C-57859r848936_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\
+
+Value Name: AlwaysInstallElevated
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254375">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254375r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000440</version>
+            <title>Windows Server 2022 users must be notified if a web-based program attempts to install software.</title>
+            <description>&lt;VulnDiscussion&gt;Web-based programs may attempt to install malicious software on a system. Ensuring users are notified if a web-based program attempts to install software allows them to refuse the installation.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57811r848940_fix">The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system.
+
+If this needs to be corrected, configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows Installer &gt;&gt; Prevent Internet Explorer security prompt for Windows Installer scripts to "Not Configured" or "Disabled".</fixtext>
+            <fix id="F-57811r848940_fix" />
+            <check system="C-57860r848939_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>The default behavior is for Internet Explorer to warn users and select whether to allow or refuse installation when a web-based program attempts to install software on the system.
+
+If the registry value name below does not exist, this is not a finding.
+
+If it exists and is configured with a value of "0", this is not a finding.
+
+If it exists and is configured with a value of "1", this is a finding.
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\Installer\
+
+Value Name: SafeForScripting
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0) (or if the Value Name does not exist)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254376">
+        <title>SRG-OS-000480-GPOS-00229</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254376r991591_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000450</version>
+            <title>Windows Server 2022 must disable automatically signing in the last interactive user after a system-initiated restart.</title>
+            <description>&lt;VulnDiscussion&gt;Windows can be configured to automatically sign the user back in after a Windows Update restart. Some protections are in place to help ensure this is done in a secure fashion; however, disabling this will prevent the caching of credentials for this purpose and also ensure the user is aware of the restart.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57812r848943_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows Logon Options &gt;&gt; Sign-in and lock last interactive user automatically after a restart to "Disabled".</fixtext>
+            <fix id="F-57812r848943_fix" />
+            <check system="C-57861r848942_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the registry value below. If it does not exist or is not configured as specified, this is a finding.
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
+
+Value Name: DisableAutomaticRestartSignOn
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254377">
+        <title>SRG-OS-000042-GPOS-00020</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254377r958422_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000460</version>
+            <title>Windows Server 2022 PowerShell script block logging must be enabled.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Enabling PowerShell script block logging will record detailed information from the processing of PowerShell commands and scripts. This can provide additional detail when malware has run on 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;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000135</ident>
+            <fixtext fixref="F-57813r848946_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows PowerShell &gt;&gt; Turn on PowerShell Script Block Logging to "Enabled".</fixtext>
+            <fix id="F-57813r848946_fix" />
+            <check system="C-57862r848945_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging\
+
+Value Name: EnableScriptBlockLogging
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254378">
+        <title>SRG-OS-000125-GPOS-00065</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254378r958510_rule" weight="10.0" severity="high">
+            <version>WN22-CC-000470</version>
+            <title>Windows Server 2022 Windows Remote Management (WinRM) client must not use Basic authentication.</title>
+            <description>&lt;VulnDiscussion&gt;Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000877</ident>
+            <fixtext fixref="F-57814r848949_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows Remote Management (WinRM) &gt;&gt; WinRM Client &gt;&gt; Allow Basic authentication to "Disabled".</fixtext>
+            <fix id="F-57814r848949_fix" />
+            <check system="C-57863r848948_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\
+
+Value Name: AllowBasic
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254379">
+        <title>SRG-OS-000393-GPOS-00173</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254379r958848_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000480</version>
+            <title>Windows Server 2022 Windows Remote Management (WinRM) client must not allow unencrypted traffic.</title>
+            <description>&lt;VulnDiscussion&gt;Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this.
+
+Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002890</ident>
+            <ident system="http://cyber.mil/cci">CCI-003123</ident>
+            <fixtext fixref="F-57815r848952_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows Remote Management (WinRM) &gt;&gt; WinRM Client &gt;&gt; Allow unencrypted traffic to "Disabled".</fixtext>
+            <fix id="F-57815r848952_fix" />
+            <check system="C-57864r848951_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\
+
+Value Name: AllowUnencryptedTraffic
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254380">
+        <title>SRG-OS-000125-GPOS-00065</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254380r958510_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000490</version>
+            <title>Windows Server 2022 Windows Remote Management (WinRM) client must not use Digest authentication.</title>
+            <description>&lt;VulnDiscussion&gt;Digest authentication is not as strong as other options and may be subject to man-in-the-middle attacks. Disallowing Digest authentication will reduce this potential.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000877</ident>
+            <fixtext fixref="F-57816r848955_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows Remote Management (WinRM) &gt;&gt; WinRM Client &gt;&gt; Disallow Digest authentication to "Enabled".</fixtext>
+            <fix id="F-57816r848955_fix" />
+            <check system="C-57865r848954_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client\
+
+Value Name: AllowDigest
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254381">
+        <title>SRG-OS-000125-GPOS-00065</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254381r958510_rule" weight="10.0" severity="high">
+            <version>WN22-CC-000500</version>
+            <title>Windows Server 2022 Windows Remote Management (WinRM) service must not use Basic authentication.</title>
+            <description>&lt;VulnDiscussion&gt;Basic authentication uses plain-text passwords that could be used to compromise a system. Disabling Basic authentication will reduce this potential.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000877</ident>
+            <fixtext fixref="F-57817r848958_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows Remote Management (WinRM) &gt;&gt; WinRM Service &gt;&gt; Allow Basic authentication to "Disabled".</fixtext>
+            <fix id="F-57817r848958_fix" />
+            <check system="C-57866r848957_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\
+
+Value Name: AllowBasic
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254382">
+        <title>SRG-OS-000393-GPOS-00173</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254382r958848_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000510</version>
+            <title>Windows Server 2022 Windows Remote Management (WinRM) service must not allow unencrypted traffic.</title>
+            <description>&lt;VulnDiscussion&gt;Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this.
+
+Satisfies: SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002890</ident>
+            <ident system="http://cyber.mil/cci">CCI-003123</ident>
+            <fixtext fixref="F-57818r848961_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows Remote Management (WinRM) &gt;&gt; WinRM Service &gt;&gt; Allow unencrypted traffic to "Disabled".</fixtext>
+            <fix id="F-57818r848961_fix" />
+            <check system="C-57867r848960_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\
+
+Value Name: AllowUnencryptedTraffic
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254383">
+        <title>SRG-OS-000373-GPOS-00156</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254383r1000166_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000520</version>
+            <title>Windows Server 2022 Windows Remote Management (WinRM) service must not store RunAs credentials.</title>
+            <description>&lt;VulnDiscussion&gt;Storage of administrative credentials could allow unauthorized access. Disallowing the storage of RunAs credentials for Windows Remote Management will prevent them from being used with plug-ins.
+
+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004895</ident>
+            <fixtext fixref="F-57819r848964_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows Remote Management (WinRM) &gt;&gt; WinRM Service &gt;&gt; Disallow WinRM from storing RunAs credentials to "Enabled".</fixtext>
+            <fix id="F-57819r848964_fix" />
+            <check system="C-57868r848963_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Service\
+
+Value Name: DisableRunAs
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254384">
+        <title>SRG-OS-000041-GPOS-00019</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254384r958420_rule" weight="10.0" severity="medium">
+            <version>WN22-CC-000530</version>
+            <title>Windows Server 2022 must have PowerShell Transcription enabled.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Enabling PowerShell Transcription will record detailed information from the processing of PowerShell commands and scripts. This can provide additional detail when malware has run on 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;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000134</ident>
+            <fixtext fixref="F-57820r848967_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Windows PowerShell &gt;&gt; "Turn on PowerShell Transcription" to "Enabled".
+
+Specify the Transcript output directory to point to a Central Log Server or another secure location to prevent user access.</fixtext>
+            <fix id="F-57820r848967_fix" />
+            <check system="C-57869r848966_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\PowerShell\Transcription\
+
+Value Name: EnableTranscripting
+
+Value Type: REG_DWORD
+Value: 1</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254385">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254385r958726_rule" weight="10.0" severity="high">
+            <version>WN22-DC-000010</version>
+            <title>Windows Server 2022 must only allow administrators responsible for the domain controller to have Administrator rights on the system.</title>
+            <description>&lt;VulnDiscussion&gt;An account that does not have Administrator duties must not have Administrator rights. Such rights would allow the account to bypass or modify required security restrictions on that machine and make it vulnerable to attack.
+
+System administrators must log on to systems using only accounts with the minimum level of authority necessary. 
+
+Standard user accounts must not be members of the built-in Administrators 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57821r848970_fix">Configure the Administrators group to include only administrator groups or accounts that are responsible for the system.
+
+Remove any standard user accounts.</fixtext>
+            <fix id="F-57821r848970_fix" />
+            <check system="C-57870r848969_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. A separate version applies to other systems.
+
+Review the Administrators group. Only the appropriate administrator groups or accounts responsible for administration of the system may be members of the group.
+
+Standard user accounts must not be members of the local administrator group.
+
+If prohibited accounts are members of the local administrators group, this is a finding.
+
+If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254386">
+        <title>SRG-OS-000112-GPOS-00057</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254386r1000167_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000020</version>
+            <title>Windows Server 2022 Kerberos user logon restrictions must be enforced.</title>
+            <description>&lt;VulnDiscussion&gt;This policy setting determines whether the Kerberos Key Distribution Center (KDC) validates every request for a session ticket against the user rights policy of the target computer. The policy is enabled by default, which is the most secure setting for validating that access to target resources is not circumvented.
+
+Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001941</ident>
+            <fixtext fixref="F-57822r848973_fix">Configure the policy value in the Default Domain Policy for Computer Configuration &gt;&gt; Policies &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Kerberos Policy &gt;&gt; Enforce user logon restrictions to "Enabled".</fixtext>
+            <fix id="F-57822r848973_fix" />
+            <check system="C-57871r848972_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Verify the following is configured in the Default Domain Policy:
+
+Open "Group Policy Management".
+
+Navigate to "Group Policy Objects" in the Domain being reviewed (Forest &gt;&gt; Domains &gt;&gt; Domain). 
+
+Right-click on the "Default Domain Policy".
+
+Select "Edit".
+
+Navigate to Computer Configuration &gt;&gt; Policies &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Kerberos Policy.
+
+If the "Enforce user logon restrictions" is not set to "Enabled", this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254387">
+        <title>SRG-OS-000112-GPOS-00057</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254387r1000168_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000030</version>
+            <title>Windows Server 2022 Kerberos service ticket maximum lifetime must be limited to 600 minutes or less.</title>
+            <description>&lt;VulnDiscussion&gt;This setting determines the maximum amount of time (in minutes) that a granted session ticket can be used to access a particular service. Session tickets are used only to authenticate new connections with servers. Ongoing operations are not interrupted if the session ticket used to authenticate the connection expires during the connection.
+
+Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001941</ident>
+            <fixtext fixref="F-57823r848976_fix">Configure the policy value in the Default Domain Policy for Computer Configuration &gt;&gt; Policies &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Kerberos Policy &gt;&gt; Maximum lifetime for service ticket to a maximum of "600" minutes, but not "0", which equates to "Ticket doesn't expire".</fixtext>
+            <fix id="F-57823r848976_fix" />
+            <check system="C-57872r848975_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Verify the following is configured in the Default Domain Policy:
+
+Open "Group Policy Management".
+
+Navigate to "Group Policy Objects" in the Domain being reviewed (Forest &gt;&gt; Domains &gt;&gt; Domain). 
+
+Right-click on the "Default Domain Policy".
+
+Select "Edit".
+
+Navigate to Computer Configuration &gt;&gt; Policies &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Kerberos Policy.
+
+If the value for "Maximum lifetime for service ticket" is "0" or greater than "600" minutes, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254388">
+        <title>SRG-OS-000112-GPOS-00057</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254388r1000169_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000040</version>
+            <title>Windows Server 2022 Kerberos user ticket lifetime must be limited to 10 hours or less.</title>
+            <description>&lt;VulnDiscussion&gt;In Kerberos, there are two types of tickets: Ticket Granting Tickets (TGTs) and Service Tickets. Kerberos tickets have a limited lifetime so the time an attacker has to implement an attack is limited. This policy controls how long TGTs can be renewed. With Kerberos, the user's initial authentication to the domain controller results in a TGT, which is then used to request Service Tickets to resources. Upon startup, each computer gets a TGT before requesting a service ticket to the domain controller and any other computers it needs to access. For services that start up under a specified user account, users must always get a TGT first and then get Service Tickets to all computers and services accessed.
+
+Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001941</ident>
+            <fixtext fixref="F-57824r848979_fix">Configure the policy value in the Default Domain Policy for Computer Configuration &gt;&gt; Policies &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Kerberos Policy &gt;&gt; Maximum lifetime for user ticket to a maximum of "10" hours but not "0", which equates to "Ticket doesn't expire".</fixtext>
+            <fix id="F-57824r848979_fix" />
+            <check system="C-57873r848978_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Verify the following is configured in the Default Domain Policy:
+
+Open "Group Policy Management".
+
+Navigate to "Group Policy Objects" in the Domain being reviewed (Forest &gt;&gt; Domains &gt;&gt; Domain).
+
+Right-click on the "Default Domain Policy".
+
+Select "Edit".
+
+Navigate to Computer Configuration &gt;&gt; Policies &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Kerberos Policy.
+
+If the value for "Maximum lifetime for user ticket" is "0" or greater than "10" hours, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254389">
+        <title>SRG-OS-000112-GPOS-00057</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254389r1000170_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000050</version>
+            <title>Windows Server 2022 Kerberos policy user ticket renewal maximum lifetime must be limited to seven days or less.</title>
+            <description>&lt;VulnDiscussion&gt;This setting determines the period of time (in days) during which a user's Ticket Granting Ticket (TGT) may be renewed. This security configuration limits the amount of time an attacker has to crack the TGT and gain access.
+
+Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001941</ident>
+            <fixtext fixref="F-57825r848982_fix">Configure the policy value in the Default Domain Policy for Computer Configuration &gt;&gt; Policies &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Kerberos Policy &gt;&gt; Maximum lifetime for user ticket renewal to a maximum of "7" days or less.</fixtext>
+            <fix id="F-57825r848982_fix" />
+            <check system="C-57874r848981_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Verify the following is configured in the Default Domain Policy:
+
+Open "Group Policy Management".
+
+Navigate to "Group Policy Objects" in the Domain being reviewed (Forest &gt;&gt; Domains &gt;&gt; Domain).
+ 
+Right-click on the "Default Domain Policy".
+
+Select "Edit".
+
+Navigate to Computer Configuration &gt;&gt; Policies &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Kerberos Policy.
+
+If the "Maximum lifetime for user ticket renewal" is greater than "7" days, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254390">
+        <title>SRG-OS-000112-GPOS-00057</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254390r1000171_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000060</version>
+            <title>Windows Server 2022 computer clock synchronization tolerance must be limited to five minutes or less.</title>
+            <description>&lt;VulnDiscussion&gt;This setting determines the maximum time difference (in minutes) that Kerberos will tolerate between the time on a client's clock and the time on a server's clock while still considering the two clocks synchronous. To prevent replay attacks, Kerberos uses timestamps as part of its protocol definition. For timestamps to work properly, the clocks of the client and the server need to be in sync as much as possible.
+
+Satisfies: SRG-OS-000112-GPOS-00057, SRG-OS-000113-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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001941</ident>
+            <fixtext fixref="F-57826r848985_fix">Configure the policy value in the Default Domain Policy for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Kerberos Policy &gt;&gt; Maximum tolerance for computer clock synchronization to a maximum of "5" minutes or less.</fixtext>
+            <fix id="F-57826r848985_fix" />
+            <check system="C-57875r848984_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Verify the following is configured in the Default Domain Policy:
+
+Open "Group Policy Management".
+
+Navigate to "Group Policy Objects" in the Domain being reviewed (Forest &gt;&gt; Domains &gt;&gt; Domain).
+ 
+Right-click on the "Default Domain Policy".
+
+Select "Edit".
+
+Navigate to Computer Configuration &gt;&gt; Policies &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Account Policies &gt;&gt; Kerberos Policy.
+
+If the "Maximum tolerance for computer clock synchronization" is greater than "5" minutes, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254391">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254391r958726_rule" weight="10.0" severity="high">
+            <version>WN22-DC-000070</version>
+            <title>Windows Server 2022 permissions on the Active Directory data files must only allow System and Administrators access.</title>
+            <description>&lt;VulnDiscussion&gt;Improper access permissions for directory data-related files could allow unauthorized users to read, modify, or delete directory data or audit trails.
+
+Satisfies: SRG-OS-000324-GPOS-00125, SRG-OS-000206-GPOS-00084&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001314</ident>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57827r848988_fix">Maintain the permissions on NTDS database and log files as follows:
+
+NT AUTHORITY\SYSTEM:(I)(F)
+BUILTIN\Administrators:(I)(F)
+
+(I) - permission inherited from parent container
+(F) - full access</fixtext>
+            <fix id="F-57827r848988_fix" />
+            <check system="C-57876r848987_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Run "Regedit".
+
+Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters".
+
+Note the directory locations in the values for:
+
+Database log files path
+DSA Database file
+
+By default, they will be \Windows\NTDS.
+
+If the locations are different, the following will need to be run for each.
+
+Open "Command Prompt (Admin)".
+
+Navigate to the NTDS directory (\Windows\NTDS by default).
+
+Run "icacls *.*".
+
+If the permissions on each file are not as restrictive as the following, this is a finding:
+
+NT AUTHORITY\SYSTEM:(I)(F)
+BUILTIN\Administrators:(I)(F)
+
+(I) - permission inherited from parent container
+(F) - full access</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254392">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254392r958726_rule" weight="10.0" severity="high">
+            <version>WN22-DC-000080</version>
+            <title>Windows Server 2022 Active Directory SYSVOL directory must have the proper access control permissions.</title>
+            <description>&lt;VulnDiscussion&gt;Improper access permissions for directory data files could allow unauthorized users to read, modify, or delete directory data.
+
+The SYSVOL directory contains public files (to the domain) such as policies and logon scripts. Data in shared subdirectories are replicated to all domain controllers in a domain.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57828r848991_fix">Maintain the permissions on the SYSVOL directory. Do not allow greater than "Read &amp; execute" permissions for standard user accounts or groups. The defaults below meet this requirement:
+
+C:\Windows\SYSVOL
+Type - "Allow" for all
+Inherited from - "None" for all
+
+Principal - Access - Applies to
+
+Authenticated Users - Read &amp; execute - This folder, subfolder, and files
+Server Operators - Read &amp; execute- This folder, subfolder, and files
+Administrators - Special - This folder only (Special = Basic Permissions: all selected except Full control)
+CREATOR OWNER - Full control - Subfolders and files only
+Administrators - Full control - Subfolders and files only
+SYSTEM - Full control - This folder, subfolders, and files</fixtext>
+            <fix id="F-57828r848991_fix" />
+            <check system="C-57877r848990_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Open a command prompt.
+
+Run "net share".
+
+Make note of the directory location of the SYSVOL share.
+
+By default, this will be \Windows\SYSVOL\sysvol. For this requirement, permissions will be verified at the first SYSVOL directory level.
+
+If any standard user accounts or groups have greater than "Read &amp; execute" permissions, this is a finding. 
+
+The default permissions noted below meet this requirement:
+
+Open "Command Prompt".
+
+Run "icacls c:\Windows\SYSVOL".
+
+The following results must be displayed:
+
+NT AUTHORITY\Authenticated Users:(RX)
+NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(GR,GE)
+BUILTIN\Server Operators:(RX)
+BUILTIN\Server Operators:(OI)(CI)(IO)(GR,GE)
+BUILTIN\Administrators:(M,WDAC,WO)
+BUILTIN\Administrators:(OI)(CI)(IO)(F)
+NT AUTHORITY\SYSTEM:(F)
+NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
+CREATOR OWNER:(OI)(CI)(IO)(F)
+
+(RX) - Read &amp; execute 
+
+Run "icacls /help" to view definitions of other permission codes.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254393">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254393r958726_rule" weight="10.0" severity="high">
+            <version>WN22-DC-000090</version>
+            <title>Windows Server 2022 Active Directory Group Policy objects must have proper access control permissions.</title>
+            <description>&lt;VulnDiscussion&gt;When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems relying on the directory service.
+
+For Active Directory (AD), the Group Policy objects require special attention. In a distributed administration model (i.e., help desk), Group Policy objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for Group Policy objects, this could allow an intruder to change the security policy applied to all domain client computers (workstations and servers).&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57829r848994_fix">Maintain the permissions on Group Policy objects to not allow greater than "Read" and "Apply group policy" for standard user accounts or groups. The default permissions below meet this requirement:
+
+Authenticated Users - Read, Apply group policy, Special permissions
+
+The special permissions for Authenticated Users are for Read-type Properties.
+
+CREATOR OWNER - Special permissions
+SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions
+Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions
+Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions
+ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions
+
+Document any other access permissions that allow the objects to be updated with the ISSO.
+
+The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on created Group Policy objects.</fixtext>
+            <fix id="F-57829r848994_fix" />
+            <check system="C-57878r848993_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Review the permissions on Group Policy objects.
+
+Open "Group Policy Management" (available from various menus or run "gpmc.msc").
+
+Navigate to "Group Policy Objects" in the domain being reviewed (Forest &gt;&gt; Domains &gt;&gt; Domain).
+
+For each Group Policy object:
+
+Select the Group Policy object item in the left pane.
+
+Select the "Delegation" tab in the right pane.
+
+Select the "Advanced" button.
+
+Select each Group or user name.
+
+View the permissions.
+
+If any standard user accounts or groups have "Allow" permissions greater than "Read" and "Apply group policy", this is a finding.
+
+Other access permissions that allow the objects to be updated are considered findings unless specifically documented by the Information System Security Officer (ISSO).
+
+The default permissions noted below satisfy this requirement. 
+
+The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the next "Advanced" button, the desired Permission entry, and the "Edit" button.
+
+Authenticated Users - Read, Apply group policy, Special permissions
+
+The special permissions for Authenticated Users are for Read-type Properties. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding.
+
+The special permissions for the following default groups are not the focus of this requirement and may include a wide range of permissions and properties:
+
+CREATOR OWNER - Special permissions
+SYSTEM - Read, Write, Create all child objects, Delete all child objects, Special permissions
+Domain Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions
+Enterprise Admins - Read, Write, Create all child objects, Delete all child objects, Special permissions
+ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions
+
+The Domain Admins and Enterprise Admins will not have the "Delete all child objects" permission on the two default Group Policy objects: Default Domain Policy and Default Domain Controllers Policy. They will have this permission on organization created Group Policy objects.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254394">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254394r958726_rule" weight="10.0" severity="high">
+            <version>WN22-DC-000100</version>
+            <title>Windows Server 2022 Active Directory Domain Controllers Organizational Unit (OU) object must have the proper access control permissions.</title>
+            <description>&lt;VulnDiscussion&gt;When Active Directory objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service.
+
+The Domain Controllers OU object requires special attention as the Domain Controllers are central to the configuration and management of the domain. Inappropriate access permissions defined for the Domain Controllers OU could allow an intruder or unauthorized personnel to make changes that could lead to the compromise of the domain.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57830r848997_fix">Limit the permissions on the Domain Controllers OU to restrict changes to System, Domain Admins, Enterprise Admins and Administrators.
+
+The default permissions listed below satisfy this requirement.
+
+Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions.
+
+CREATOR OWNER - Special permissions
+
+SELF - Special permissions
+
+Authenticated Users - Read, Special permissions
+
+The special permissions for Authenticated Users are Read types.
+
+SYSTEM - Full Control
+
+Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions
+
+Enterprise Admins - Full Control
+
+Key Admins - Special permissions
+
+Enterprise Key Admins - Special permissions
+
+Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions
+
+Pre-Windows 2000 Compatible Access - Special permissions
+
+The special permissions for Pre-Windows 2000 Compatible Access are Read types.
+
+ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions</fixtext>
+            <fix id="F-57830r848997_fix" />
+            <check system="C-57879r848996_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Review the permissions on the Domain Controllers OU.
+
+Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Select "Advanced Features" in the "View" menu if not previously selected.
+
+Select the "Domain Controllers" OU (folder in folder icon).
+
+Right-click and select "Properties".
+
+Select the "Security" tab.
+
+If the permissions on the Domain Controllers OU do not restrict changes to System, Domain Admins, Enterprise Admins and Administrators, this is a finding.
+
+The default permissions listed below satisfy this requirement.
+
+Domains supporting Microsoft Exchange will have additional Exchange related permissions on the Domain Controllers OU. These may include some change related permissions and are not a finding.
+
+The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "View" or "Edit" button.
+
+Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement.
+
+CREATOR OWNER - Special permissions
+
+SELF - Special permissions
+
+Authenticated Users - Read, Special permissions
+
+The special permissions for Authenticated Users are Read types.
+
+If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding.
+
+SYSTEM - Full Control
+
+Domain Admins - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions
+
+Enterprise Admins - Full Control
+
+Key Admins - Special permissions
+
+Enterprise Key Admins - Special permissions
+
+Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions
+
+Pre-Windows 2000 Compatible Access - Special permissions
+
+The Special permissions for Pre-Windows 2000 Compatible Access are Read types.
+
+If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding.
+
+ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254395">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254395r958726_rule" weight="10.0" severity="high">
+            <version>WN22-DC-000110</version>
+            <title>Windows Server 2022 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions.</title>
+            <description>&lt;VulnDiscussion&gt;When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service.
+
+For Active Directory, the OU objects require special attention. In a distributed administration model (i.e., help desk), OU objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for OU objects, it could allow an intruder to add or delete users in the OU. This could result in unauthorized access to data or a denial of service (DoS) to authorized 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57831r849000_fix">Maintain the Allow type permissions on domain-defined OUs to be at least as restrictive as the defaults below.
+
+Document any additional permissions above Read with the ISSO if an approved distributed administration model (help desk or other user support staff) is implemented.
+
+CREATOR OWNER - Special permissions
+
+Self - Special permissions
+
+Authenticated Users - Read, Special permissions
+
+The special permissions for Authenticated Users are Read type.
+
+SYSTEM - Full Control
+
+Domain Admins - Full Control
+
+Enterprise Admins - Full Control
+
+Key Admins - Special permissions
+
+Enterprise Key Admins - Special permissions
+
+Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions
+
+Pre-Windows 2000 Compatible Access - Special permissions
+
+The special permissions for Pre-Windows 2000 Compatible Access are for Read types.
+
+ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions</fixtext>
+            <fix id="F-57831r849000_fix" />
+            <check system="C-57880r848999_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Review the permissions on domain-defined OUs.
+
+Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Ensure "Advanced Features" is selected in the "View" menu.
+
+For each OU that is defined (folder in folder icon) excluding the Domain Controllers OU:
+
+Right-click the OU and select "Properties".
+
+Select the "Security" tab.
+
+If the Allow type permissions on the OU are not at least as restrictive as those below, this is a finding.
+
+The permissions shown are at the summary level. More detailed permissions can be viewed by selecting the "Advanced" button, the desired Permission entry, and the "Edit" or "View" button.
+
+Except where noted otherwise, the special permissions may include a wide range of permissions and properties and are acceptable for this requirement.
+
+CREATOR OWNER - Special permissions
+
+Self - Special permissions
+
+Authenticated Users - Read, Special permissions
+
+The Special permissions for Authenticated Users are Read type. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding.
+
+SYSTEM - Full Control
+
+Domain Admins - Full Control
+
+Enterprise Admins - Full Control
+
+Key Admins - Special permissions
+
+Enterprise Key Admins - Special permissions
+
+Administrators - Read, Write, Create all child objects, Generate resultant set of policy (logging), Generate resultant set of policy (planning), Special permissions
+
+Pre-Windows 2000 Compatible Access - Special permissions
+
+The Special permissions for Pre-Windows 2000 Compatible Access are for Read types. If detailed permissions include any Create, Delete, Modify, or Write Permissions or Properties, this is a finding.
+
+ENTERPRISE DOMAIN CONTROLLERS - Read, Special permissions
+
+If an Information System Security Officer (ISSO)-approved distributed administration model (help desk or other user support staff) is implemented, permissions above Read may be allowed for groups documented by the ISSO.
+
+If any OU with improper permissions includes identification or authentication data (e.g., accounts, passwords, or password hash data) used by systems to determine access control, the severity is CAT I (e.g., OUs that include user accounts, including service/application accounts).
+
+If an OU with improper permissions does not include identification and authentication data used by systems to determine access control, the severity is CAT II (e.g., Workstation, Printer OUs).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254396">
+        <title>SRG-OS-000138-GPOS-00069</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254396r958524_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000120</version>
+            <title>Windows Server 2022 data files owned by users must be on a different logical partition from the directory server data files.</title>
+            <description>&lt;VulnDiscussion&gt;When directory service data files, especially for directories used for identification, authentication, or authorization, reside on the same logical partition as user-owned files, the directory service data may be more vulnerable to unauthorized access or other availability compromises. Directory service and user-owned data files sharing a partition may be configured with less restrictive permissions in order to allow access to the user data. 
+
+The directory service may be vulnerable to a denial of service attack when user-owned files on a common partition are expanded to an extent preventing the directory service from acquiring more space for directory or audit data.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001090</ident>
+            <fixtext fixref="F-57832r849003_fix">Move shares used to store files owned by users to a different logical partition than the directory server data files.</fixtext>
+            <fix id="F-57832r849003_fix" />
+            <check system="C-57881r849002_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Run "Regedit".
+
+Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters".
+
+Note the directory locations in the values for "DSA Database file".
+
+Open "Command Prompt".
+
+Enter "net share".
+
+Note the logical drive(s) or file system partition for any organization-created data shares.
+
+Ignore system shares (e.g., NETLOGON, SYSVOL, and administrative shares ending in $). User shares that are hidden (ending with $) must not be ignored.
+
+If user shares are located on the same logical partition as the directory server data files, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254397">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254397r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000130</version>
+            <title>Windows Server 2022 domain controllers must run on a machine dedicated to that function.</title>
+            <description>&lt;VulnDiscussion&gt;Executing application servers on the same host machine with a directory server may substantially weaken the security of the directory server. Web or database server applications usually require the addition of many programs and accounts, increasing the attack surface of the computer. 
+
+Some applications require the addition of privileged accounts, providing potential sources of compromise. Some applications (such as Microsoft Exchange) may require the use of network ports or services conflicting with the directory server. In this case, nonstandard ports might be selected, and this could interfere with intrusion detection or prevention 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57833r849006_fix">Remove additional roles or applications such as web, database, and email from the domain controller.</fixtext>
+            <fix id="F-57833r849006_fix" />
+            <check system="C-57882r849005_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers, it is NA for other systems.
+
+Review the installed roles the domain controller is supporting.
+
+Start "Server Manager".
+
+Select "AD DS" in the left pane and the server name under "Servers" to the right.
+
+Select "Add (or Remove) Roles and Features" from "Tasks" in the "Roles and Features" section. (Cancel before any changes are made.)
+
+Determine if any additional server roles are installed. A basic domain controller setup will include the following:
+
+- Active Directory Domain Services
+- DNS Server
+- File and Storage Services
+
+If any roles not requiring installation on a domain controller are installed, this is a finding. 
+
+A Domain Name System (DNS) server integrated with the directory server (e.g., AD-integrated DNS) is an acceptable application. However, the DNS server must comply with the DNS STIG security requirements.
+
+Run "Programs and Features".
+
+Review installed applications.
+
+If any applications are installed that are not required for the domain controller, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254398">
+        <title>SRG-OS-000396-GPOS-00176</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254398r987791_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000140</version>
+            <title>Windows Server 2022 must use separate, NSA-approved (Type 1) cryptography to protect the directory data in transit for directory service implementations at a classified confidentiality level when replication data traverses a network cleared to a lower level than the data.</title>
+            <description>&lt;VulnDiscussion&gt;Directory data that is not appropriately encrypted is subject to compromise. Commercial-grade encryption does not provide adequate protection when the classification level of directory data in transit is higher than the level of 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002450</ident>
+            <fixtext fixref="F-57834r849009_fix">Configure NSA-approved (Type 1) cryptography to protect the directory data in transit for directory service implementations at a classified confidentiality level that transfer replication data through a network cleared to a lower level than the data.</fixtext>
+            <fix id="F-57834r849009_fix" />
+            <check system="C-57883r849008_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Review the organization network diagram(s) or documentation to determine the level of classification for the network(s) over which replication data is transmitted.
+
+Determine the classification level of the Windows domain controller.
+
+If the classification level of the Windows domain controller is higher than the level of the networks, review the organization network diagram(s) and directory implementation documentation to determine if NSA-approved encryption is used to protect the replication network traffic.
+
+If the classification level of the Windows domain controller is higher than the level of the network traversed and NSA-approved encryption is not used, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254399">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254399r991589_rule" weight="10.0" severity="high">
+            <version>WN22-DC-000150</version>
+            <title>Windows Server 2022 directory data (outside the root DSE) of a nonpublic directory must be configured to prevent anonymous access.</title>
+            <description>&lt;VulnDiscussion&gt;To the extent that anonymous access to directory data (outside the root DSE) is permitted, read access control of the data is effectively disabled. If other means of controlling access (such as network restrictions) are compromised, there may be nothing else to protect the confidentiality of sensitive directory data.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57835r849012_fix">Configure directory data (outside the root DSE) of a nonpublic directory to prevent anonymous access.
+
+For AD, there are multiple configuration items that could enable anonymous access.
+
+Changing the access permissions on the domain naming context object (from the secure defaults) could enable anonymous access. If the check procedures indicate this is the cause, the process that was used to change the permissions must be reversed. This could have been through the Windows Support Tools ADSI Edit console (adsiedit.msc).
+
+The dsHeuristics option is used. This is addressed in check V-8555 in the AD Forest STIG.</fixtext>
+            <fix id="F-57835r849012_fix" />
+            <check system="C-57884r849011_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Open "Command Prompt" (not elevated).
+
+Run "ldp.exe".
+
+From the "Connection menu", select "Bind".
+
+Clear the User, Password, and Domain fields.
+
+Select "Simple bind" for the Bind type and click "OK".
+
+Confirmation of anonymous access will be displayed at the end:
+
+res = ldap_simple_bind_s
+Authenticated as: 'NT AUTHORITY\ANONYMOUS LOGON'
+
+From the "Browse" menu, select "Search".
+
+In the Search dialog, enter the DN of the domain naming context (generally something like "dc=disaost,dc=mil") in the Base DN field.
+
+Clear the Attributes field and select "Run".
+
+Error messages must display related to Bind and user not authenticated.
+
+If attribute data is displayed, anonymous access is enabled to the domain naming context and this is a finding.
+
+The following network controls allow the finding severity to be downgraded to a CAT II since these measures lower the risk associated with anonymous access.
+
+Network hardware ports at the site are subject to 802.1x authentication or MAC address restrictions. 
+
+Premise firewall or host restrictions prevent access to ports 389, 636, 3268, and 3269 from client hosts not explicitly identified by domain (.mil) or IP address.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254400">
+        <title>SRG-OS-000163-GPOS-00072</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254400r970703_rule" weight="10.0" severity="low">
+            <version>WN22-DC-000160</version>
+            <title>Windows Server 2022 directory service must be configured to terminate LDAP-based network connections to the directory server after five minutes of inactivity.</title>
+            <description>&lt;VulnDiscussion&gt;The failure to terminate inactive network connections increases the risk of a successful attack on the directory server. The longer an established session is in progress, the more time an attacker has to hijack the session, implement a means to passively intercept data, or compromise any protections on client access. For example, if an attacker gains control of a client computer, an existing (already authenticated) session with the directory server could allow access to the directory. The lack of confidentiality protection in LDAP-based sessions increases exposure to this vulnerability.
+
+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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001133</ident>
+            <ident system="http://cyber.mil/cci">CCI-002361</ident>
+            <fixtext fixref="F-57836r849015_fix">Configure the directory service to terminate LDAP-based network connections to the directory server after 5 minutes of inactivity.
+
+Open an elevated "Command prompt" (run as administrator).
+
+Enter "ntdsutil".
+
+At the "ntdsutil:" prompt, enter "LDAP policies".
+
+At the "ldap policy:" prompt, enter "connections".
+
+At the "server connections:" prompt, enter "connect to server [host-name]" (where [host-name] is the computer name of the domain controller).
+
+At the "server connections:" prompt, enter "q".
+
+At the "ldap policy:" prompt, enter "Set MaxConnIdleTime to 300".
+
+Enter "Commit Changes" to save.
+
+Enter "Show values" to verify changes.
+
+Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit.</fixtext>
+            <fix id="F-57836r849015_fix" />
+            <check system="C-57885r849014_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Open an elevated "Command Prompt" (run as administrator).
+
+Enter "ntdsutil".
+
+At the "ntdsutil:" prompt, enter "LDAP policies".
+
+At the "ldap policy:" prompt, enter "connections".
+
+At the "server connections:" prompt, enter "connect to server [host-name]"
+(where [host-name] is the computer name of the domain controller).
+
+At the "server connections:" prompt, enter "q".
+
+At the "ldap policy:" prompt, enter "show values". 
+
+If the value for MaxConnIdleTime is greater than "300" (5 minutes) or is not specified, this is a finding.
+
+Enter "q" at the "ldap policy:" and "ntdsutil:" prompts to exit.
+
+Alternately, Dsquery can be used to display MaxConnIdleTime:
+
+Open "Command Prompt (Admin)".
+Enter the following command (on a single line).
+
+dsquery * "cn=Default Query Policy,cn=Query-Policies,cn=Directory Service, cn=Windows NT,cn=Services,cn=Configuration,dc=[forest-name]" -attr LDAPAdminLimits 
+
+The quotes are required and dc=[forest-name] is the fully qualified LDAP name of the domain being reviewed (e.g., dc=disaost,dc=mil).
+
+If the results do not specify a "MaxConnIdleTime" or it has a value greater than "300" (5 minutes), this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254401">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254401r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000170</version>
+            <title>Windows Server 2022 Active Directory Group Policy objects must be configured with proper audit settings.</title>
+            <description>&lt;VulnDiscussion&gt;When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. 
+
+For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes Group Policy objects. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57837r849018_fix">Configure the audit settings for Group Policy objects to include the following:
+
+This can be done at the Policy level in Active Directory to apply to all group policies.
+
+Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Select "Advanced Features" from the "View" Menu.
+
+Navigate to [Domain] &gt;&gt; System &gt;&gt; Policies in the left panel.
+
+Right-click "Policies", select "Properties".
+
+Select the "Security" tab.
+
+Select "Advanced".
+
+Select the "Auditing" tab.
+
+Type - Fail
+Principal - Everyone
+Access - Full Control
+Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects
+
+The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference.
+
+Type - Success
+Principal - Everyone
+Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected)
+Inherited from - Parent Object
+Applies to - Descendant groupPolicyContainer objects
+
+Two instances with the following summary information will be listed:
+
+Type - Success
+Principal - Everyone
+Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions)
+Inherited from - Parent Object
+Applies to - Descendant Organization Unit Objects</fixtext>
+            <fix id="F-57837r849018_fix" />
+            <check system="C-57886r849017_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Review the auditing configuration for all Group Policy objects.
+
+Open "Group Policy Management" (available from various menus or run "gpmc.msc").
+
+Navigate to "Group Policy Objects" in the domain being reviewed (Forest &gt;&gt; Domains &gt;&gt; Domain).
+
+For each Group Policy object:
+
+Select the Group Policy object item in the left pane.
+
+Select the "Delegation" tab in the right pane.
+
+Select "Advanced".
+
+Select "Advanced" again and then the "Auditing" tab.
+
+If the audit settings for any Group Policy object are not at least as inclusive as those below, this is a finding:
+
+Type - Fail
+Principal - Everyone
+Access - Full Control
+Applies to - This object and all descendant objects or Descendant groupPolicyContainer objects
+
+The three Success types listed below are defaults inherited from the Parent Object. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference.
+
+Type - Success
+Principal - Everyone
+Access - Special (Permissions: Write all properties, Modify permissions; Properties: all "Write" type selected)
+Inherited from - Parent Object
+Applies to - Descendant groupPolicyContainer objects
+
+Two instances with the following summary information will be listed:
+
+Type - Success
+Principal - Everyone
+Access - blank (Permissions: none selected; Properties: one instance - Write gPLink, one instance - Write gPOptions)
+Inherited from - Parent Object
+Applies to - Descendant Organization Unit Objects</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254402">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254402r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000180</version>
+            <title>Windows Server 2022 Active Directory Domain object must be configured with proper audit settings.</title>
+            <description>&lt;VulnDiscussion&gt;When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. 
+
+For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57838r849021_fix">Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Ensure "Advanced Features" is selected in the "View" menu.
+
+Select the domain being reviewed in the left pane.
+
+Right-click the domain name and select "Properties".
+
+Select the "Security" tab.
+
+Select "Advanced" and then the "Auditing" tab.
+
+Configure the audit settings for Domain object to include the following:
+
+Type - Fail
+Principal - Everyone
+Access - Full Control
+Inherited from - None
+Applies to - This object only
+
+The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default.
+
+Two instances with the following summary information will be listed:
+
+Type - Success
+Principal - Everyone
+Access - (blank)
+Inherited from - None
+Applies to - Special
+
+Type - Success
+Principal - Domain Users
+Access - All extended rights
+Inherited from - None
+Applies to - This object only
+
+Type - Success
+Principal - Administrators
+Access - All extended rights
+Inherited from - None
+Applies to - This object only
+
+Type - Success
+Principal - Everyone
+Access - Special
+Inherited from - None
+Applies to - This object only
+(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner.)</fixtext>
+            <fix id="F-57838r849021_fix" />
+            <check system="C-57887r849020_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Review the auditing configuration for the Domain object.
+
+Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Ensure "Advanced Features" is selected in the "View" menu.
+
+Select the domain being reviewed in the left pane.
+
+Right-click the domain name and select "Properties".
+
+Select the "Security" tab.
+
+Select "Advanced" and then the "Auditing" tab.
+
+If the audit settings on the Domain object are not at least as inclusive as those below, this is a finding:
+
+Type - Fail
+Principal - Everyone
+Access - Full Control
+Inherited from - None
+Applies to - This object only
+
+The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default.
+
+Two instances with the following summary information will be listed:
+
+Type - Success
+Principal - Everyone
+Access - (blank)
+Inherited from - None
+Applies to - Special
+
+Type - Success
+Principal - Domain Users
+Access - All extended rights
+Inherited from - None
+Applies to - This object only
+
+Type - Success
+Principal - Administrators
+Access - All extended rights
+Inherited from - None
+Applies to - This object only
+
+Type - Success
+Principal - Everyone
+Access - Special
+Inherited from - None
+Applies to - This object only
+(Access - Special = Permissions: Write all properties, Modify permissions, Modify owner)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254403">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254403r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000190</version>
+            <title>Windows Server 2022 Active Directory Infrastructure object must be configured with proper audit settings.</title>
+            <description>&lt;VulnDiscussion&gt;When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. 
+
+For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Infrastructure object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57839r849024_fix">Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Ensure "Advanced Features" is selected in the "View" menu.
+
+Select the domain being reviewed in the left pane.
+
+Right-click the "Infrastructure" object in the right pane and select "Properties".
+
+Select the "Security" tab.
+
+Select "Advanced" and then the "Auditing" tab.
+
+Configure the audit settings for Infrastructure object to include the following:
+
+Type - Fail
+Principal - Everyone
+Access - Full Control
+Inherited from - None
+
+The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default.
+
+Type - Success
+Principal - Everyone
+Access - Special
+Inherited from - None
+(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master)
+
+Two instances with the following summary information will be listed:
+
+Type - Success
+Principal - Everyone
+Access - (blank)
+Inherited from - (CN of domain)</fixtext>
+            <fix id="F-57839r849024_fix" />
+            <check system="C-57888r849023_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Review the auditing configuration for Infrastructure object.
+
+Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Ensure "Advanced Features" is selected in the "View" menu.
+
+Select the domain being reviewed in the left pane.
+
+Right-click the "Infrastructure" object in the right pane and select "Properties".
+
+Select the "Security" tab.
+
+Select "Advanced" and then the "Auditing" tab.
+
+If the audit settings on the Infrastructure object are not at least as inclusive as those below, this is a finding:
+
+Type - Fail
+Principal - Everyone
+Access - Full Control
+Inherited from - None
+
+The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default.
+
+Type - Success
+Principal - Everyone
+Access - Special
+Inherited from - None
+(Access - Special = Permissions: Write all properties, All extended rights, Change infrastructure master)
+
+Two instances with the following summary information will be listed:
+
+Type - Success
+Principal - Everyone
+Access - (blank)
+Inherited from - (CN of domain)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254404">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254404r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000200</version>
+            <title>Windows Server 2022 Active Directory Domain Controllers Organizational Unit (OU) object must be configured with proper audit settings.</title>
+            <description>&lt;VulnDiscussion&gt;When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. 
+
+For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain Controller OU object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57840r849027_fix">Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Ensure "Advanced Features" is selected in the "View" menu.
+
+Select the "Domain Controllers OU" under the domain being reviewed in the left pane.
+
+Right-click the "Domain Controllers OU" object and select "Properties".
+
+Select the "Security" tab.
+
+Select "Advanced" and then the "Auditing" tab.
+
+Configure the audit settings for Domain Controllers OU object to include the following:
+
+Type - Fail
+Principal - Everyone
+Access - Full Control
+Inherited from - None
+
+The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default.
+
+Type - Success
+Principal - Everyone
+Access - Special
+Inherited from - None
+Applies to - This object only
+(Access - Special = Permissions: all create, delete and modify permissions)
+
+Type - Success
+Principal - Everyone
+Access - Write all properties
+Inherited from - None
+Applies to - This object and all descendant objects
+
+Two instances with the following summary information will be listed:
+
+Type - Success
+Principal - Everyone
+Access - (blank)
+Inherited from - (CN of domain)
+Applies to - Descendant Organizational Unit objects</fixtext>
+            <fix id="F-57840r849027_fix" />
+            <check system="C-57889r849026_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Review the auditing configuration for the Domain Controller OU object.
+
+Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Ensure "Advanced Features" is selected in the "View" menu.
+
+Select the "Domain Controllers OU" under the domain being reviewed in the left pane.
+
+Right-click the "Domain Controllers OU" object and select "Properties".
+
+Select the "Security" tab.
+
+Select "Advanced" and then the "Auditing" tab.
+
+If the audit settings on the Domain Controllers OU object are not at least as inclusive as those below, this is a finding:
+
+Type - Fail
+Principal - Everyone
+Access - Full Control
+Inherited from - None
+Applies to - This object and all descendant objects
+
+The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default.
+
+Type - Success
+Principal - Everyone
+Access - Special
+Inherited from - None
+Applies to - This object only
+(Access - Special = Permissions: all create, delete and modify permissions)
+
+Type - Success
+Principal - Everyone
+Access - Write all properties
+Inherited from - None
+Applies to - This object and all descendant objects
+
+Two instances with the following summary information will be listed:
+
+Type - Success
+Principal - Everyone
+Access - (blank)
+Inherited from - (CN of domain)
+Applies to - Descendant Organizational Unit objects</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254405">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254405r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000210</version>
+            <title>Windows Server 2022 Active Directory AdminSDHolder object must be configured with proper audit settings.</title>
+            <description>&lt;VulnDiscussion&gt;When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. 
+
+For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the AdminSDHolder object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57841r849030_fix">Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Ensure "Advanced Features" is selected in the "View" menu.
+
+Select "System" under the domain being reviewed in the left pane.
+
+Right-click the "AdminSDHolder" object in the right pane and select "Properties".
+
+Select the "Security" tab.
+
+Select "Advanced" and then the "Auditing" tab.
+
+Configure the audit settings for AdminSDHolder object to include the following:
+
+Type - Fail
+Principal - Everyone
+Access - Full Control
+Inherited from - None
+Applies to - This object only
+
+The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default.
+
+Type - Success
+Principal - Everyone
+Access - Special
+Inherited from - None
+Applies to - This object only
+(Access - Special = Write all properties, Modify permissions, Modify owner)
+
+Two instances with the following summary information will be listed:
+
+Type - Success
+Principal - Everyone
+Access - (blank)
+Inherited from - (CN of domain)
+Applies to - Descendant Organizational Unit objects</fixtext>
+            <fix id="F-57841r849030_fix" />
+            <check system="C-57890r849029_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Review the auditing configuration for the "AdminSDHolder" object.
+
+Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Ensure "Advanced Features" is selected in the "View" menu.
+
+Select "System" under the domain being reviewed in the left pane.
+
+Right-click the "AdminSDHolder" object in the right pane and select "Properties".
+
+Select the "Security" tab.
+
+Select "Advanced" and then the "Auditing" tab.
+
+If the audit settings on the "AdminSDHolder" object are not at least as inclusive as those below, this is a finding:
+
+Type - Fail
+Principal - Everyone
+Access - Full Control
+Inherited from - None
+Applies to - This object only
+
+The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default.
+
+Type - Success
+Principal - Everyone
+Access - Special
+Inherited from - None
+Applies to - This object only
+(Access - Special = Write all properties, Modify permissions, Modify owner)
+
+Two instances with the following summary information will be listed:
+
+Type - Success
+Principal - Everyone
+Access - (blank)
+Inherited from - (CN of domain)
+Applies to - Descendant Organizational Unit objects</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254406">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254406r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000220</version>
+            <title>Windows Server 2022 Active Directory RID Manager$ object must be configured with proper audit settings.</title>
+            <description>&lt;VulnDiscussion&gt;When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. 
+
+For Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the RID Manager$ object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57842r849033_fix">Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Ensure "Advanced Features" is selected in the "View" menu.
+
+Select "System" under the domain being reviewed in the left pane.
+
+Right-click the "RID Manager$" object in the right pane and select "Properties".
+
+Select the "Security" tab.
+
+Select "Advanced" and then the "Auditing" tab.
+
+Configure the audit settings for RID Manager$ object to include the following:
+
+Type - Fail
+Principal - Everyone
+Access - Full Control
+Inherited from - None
+
+The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default.
+
+Type - Success
+Principal - Everyone
+Access - Special
+Inherited from - None
+ (Access - Special = Write all properties, All extended rights, Change RID master)
+
+Two instances with the following summary information will be listed:
+
+Type - Success
+Principal - Everyone
+Access - (blank)
+Inherited from - (CN of domain)</fixtext>
+            <fix id="F-57842r849033_fix" />
+            <check system="C-57891r849032_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Review the auditing configuration for the "RID Manager$" object.
+
+Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Ensure "Advanced Features" is selected in the "View" menu.
+
+Select "System" under the domain being reviewed in the left pane.
+
+Right-click the "RID Manager$" object in the right pane and select "Properties".
+
+Select the "Security" tab.
+
+Select "Advanced" and then the "Auditing" tab.
+
+If the audit settings on the "RID Manager$" object are not at least as inclusive as those below, this is a finding:
+
+Type - Fail
+Principal - Everyone
+Access - Full Control
+Inherited from - None
+
+The success types listed below are defaults. Where Special is listed in the summary screens for Access, detailed Permissions are provided for reference. Various Properties selections may also exist by default.
+
+Type - Success
+Principal - Everyone
+Access - Special
+Inherited from - None
+ (Access - Special = Write all properties, All extended rights, Change RID master)
+
+Two instances with the following summary information will be listed:
+
+Type - Success
+Principal - Everyone
+Access - (blank)
+Inherited from - (CN of domain)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254407">
+        <title>SRG-OS-000004-GPOS-00004</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254407r958368_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000230</version>
+            <title>Windows Server 2022 must be configured to audit Account Management - Computer Account Management successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Computer Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling computer accounts.
+
+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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000018</ident>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-001403</ident>
+            <ident system="http://cyber.mil/cci">CCI-001404</ident>
+            <ident system="http://cyber.mil/cci">CCI-001405</ident>
+            <ident system="http://cyber.mil/cci">CCI-002130</ident>
+            <fixtext fixref="F-57843r849036_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; Account Management &gt;&gt; Audit Computer Account Management with Success selected.</fixtext>
+            <fix id="F-57843r849036_fix" />
+            <check system="C-57892r849035_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+Account Management &gt;&gt; Computer Account Management - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254408">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254408r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000240</version>
+            <title>Windows Server 2022 must be configured to audit DS Access - Directory Service Access successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Audit Directory Service Access records events related to users accessing an Active Directory object.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57844r849039_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; DS Access &gt;&gt; Directory Service Access with Success selected.</fixtext>
+            <fix id="F-57844r849039_fix" />
+            <check system="C-57893r849038_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+DS Access &gt;&gt; Directory Service Access - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254409">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254409r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000250</version>
+            <title>Windows Server 2022 must be configured to audit DS Access - Directory Service Access failures.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Audit Directory Service Access records events related to users accessing an Active Directory object.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57845r849042_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; DS Access &gt;&gt; Directory Service Access with "Failure" selected.</fixtext>
+            <fix id="F-57845r849042_fix" />
+            <check system="C-57894r849041_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+DS Access &gt;&gt; Directory Service Access - Failure</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254410">
+        <title>SRG-OS-000327-GPOS-00127</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254410r958732_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000260</version>
+            <title>Windows Server 2022 must be configured to audit DS Access - Directory Service Changes successes.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.
+
+Audit Directory Service Changes records events related to changes made to objects in Active Directory Domain Services.
+
+Satisfies: SRG-OS-000327-GPOS-00127, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000468-GPOS-00212&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000172</ident>
+            <ident system="http://cyber.mil/cci">CCI-002234</ident>
+            <fixtext fixref="F-57846r849045_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Advanced Audit Policy Configuration &gt;&gt; System Audit Policies &gt;&gt; DS Access &gt;&gt; Directory Service Changes with "Success" selected.</fixtext>
+            <fix id="F-57846r849045_fix" />
+            <check system="C-57895r849044_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (WN22-SO-000050) for the detailed auditing subcategories to be effective. 
+
+Use the "AuditPol" tool to review the current Audit Policy configuration:
+
+Open "PowerShell" or a "Command Prompt" with elevated privileges ("Run as administrator").
+
+Enter "AuditPol /get /category:*"
+
+Compare the "AuditPol" settings with the following:
+
+If the system does not audit the following, this is a finding.
+
+DS Access &gt;&gt; Directory Service Changes - Success</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254412">
+        <title>SRG-OS-000066-GPOS-00034</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254412r958448_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000280</version>
+            <title>Windows Server 2022 domain controllers must have a PKI server certificate.</title>
+            <description>&lt;VulnDiscussion&gt;Domain controllers are part of the chain of trust for PKI authentications. Without the appropriate certificate, the authenticity of the domain controller cannot be verified. Domain controllers must have a server certificate to establish authenticity as part of PKI authentications in the domain.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000185</ident>
+            <fixtext fixref="F-57848r849051_fix">Obtain a server certificate for the domain controller.</fixtext>
+            <fix id="F-57848r849051_fix" />
+            <check system="C-57897r849050_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Run "MMC".
+
+Select "Add/Remove Snap-in" from the "File" menu.
+
+Select "Certificates" in the left pane and click "Add &gt;".
+
+Select "Computer Account" and click "Next".
+
+Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish".
+
+Click "OK".
+
+Select and expand the Certificates (Local Computer) entry in the left pane.
+
+Select and expand the Personal entry in the left pane.
+
+Select the Certificates entry in the left pane.
+
+If no certificate for the domain controller exists in the right pane, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254413">
+        <title>SRG-OS-000066-GPOS-00034</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254413r958448_rule" weight="10.0" severity="high">
+            <version>WN22-DC-000290</version>
+            <title>Windows Server 2022 domain Controller PKI certificates must be issued by the DoD PKI or an approved External Certificate Authority (ECA).</title>
+            <description>&lt;VulnDiscussion&gt;A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions. The use of multiple CAs from separate PKI implementations results in interoperability issues. If servers and clients do not have a common set of root CA certificates, they are not able to authenticate each other.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000185</ident>
+            <fixtext fixref="F-57849r849054_fix">Obtain a server certificate for the domain controller issued by the DoD PKI or an approved ECA.</fixtext>
+            <fix id="F-57849r849054_fix" />
+            <check system="C-57898r849053_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Run "MMC".
+
+Select "Add/Remove Snap-in" from the "File" menu.
+
+Select "Certificates" in the left pane and click "Add &gt;".
+
+Select "Computer Account" and click "Next".
+
+Select the appropriate option for "Select the computer you want this snap-in to manage" and click "Finish".
+
+Click "OK".
+
+Select and expand the Certificates (Local Computer) entry in the left pane.
+
+Select and expand the Personal entry in the left pane.
+
+Select the Certificates entry in the left pane.
+
+In the right pane, examine the "Issued By" field for the certificate to determine the issuing CA.
+
+If the "Issued By" field of the PKI certificate being used by the domain controller does not indicate the issuing CA is part of the DoD PKI or an approved ECA, this is a finding.
+
+If the certificates in use are issued by a CA authorized by the Component's CIO, this is a CAT II finding.
+
+There are multiple sources from which lists of valid DoD CAs and approved ECAs can be obtained: 
+
+The Global Directory Service (GDS) website provides an online source. The address for this site is https://crl.gds.disa.mil.
+
+DoD Public Key Enablement (PKE) Engineering Support maintains the InstallRoot utility to manage DoD supported root certificates on Windows computers, which includes a list of authorized CAs. The utility package can be downloaded from the PKI and PKE Tools page on Cyber Exchange:
+
+https://https://cyber.mil/pki-pke/</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254414">
+        <title>SRG-OS-000066-GPOS-00034</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254414r958448_rule" weight="10.0" severity="high">
+            <version>WN22-DC-000300</version>
+            <title>Windows Server 2022 PKI certificates associated with user accounts must be issued by a DoD PKI or an approved External Certificate Authority (ECA).</title>
+            <description>&lt;VulnDiscussion&gt;A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions.
+
+Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000185</ident>
+            <fixtext fixref="F-57850r849057_fix">Map user accounts to PKI certificates using the appropriate User Principal Name (UPN) for the network. See PKE documentation for details.</fixtext>
+            <fix id="F-57850r849057_fix" />
+            <check system="C-57899r849056_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Review user account mappings to PKI certificates.
+
+Open "Windows PowerShell".
+
+Enter "Get-ADUser -Filter * | FT Name, UserPrincipalName, Enabled".
+
+Exclude disabled accounts (e.g., DefaultAccount, Guest) and the krbtgt account.
+
+If the User Principal Name (UPN) is not in the format of an individual's identifier for the certificate type and for the appropriate domain suffix, this is a finding.
+
+For standard NIPRNet certificates, the individual's identifier is in the format of an Electronic Data Interchange - Personnel Identifier (EDI-PI).
+
+Alt Tokens and other certificates may use a different UPN format than the EDI-PI which vary by organization. Verified these with the organization.
+
+NIPRNet Example:
+
+Name - User Principal Name
+User1 - 1234567890@mil
+
+See PKE documentation for other network domain suffixes.
+
+If the mappings are to certificates issued by a CA authorized by the Component's CIO, this is a CAT II finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254415">
+        <title>SRG-OS-000105-GPOS-00052</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254415r1000172_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000310</version>
+            <title>Windows Server 2022 Active Directory user accounts, including administrators, must be configured to require the use of a Common Access Card (CAC), Personal Identity Verification (PIV)-compliant hardware token, or Alternate Logon Token (ALT) for user authentication.</title>
+            <description>&lt;VulnDiscussion&gt;Smart cards such as the CAC support a two-factor authentication technique. This provides a higher level of trust in the asserted identity than use of the username and password for authentication.
+
+Satisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000756</ident>
+            <ident system="http://cyber.mil/cci">CCI-000776</ident>
+            <ident system="http://cyber.mil/cci">CCI-000767</ident>
+            <ident system="http://cyber.mil/cci">CCI-000768</ident>
+            <ident system="http://cyber.mil/cci">CCI-001948</ident>
+            <fixtext fixref="F-57851r849060_fix">Configure all user accounts, including administrator accounts, in Active Directory to enable the option "Smart card is required for interactive logon".
+
+Run "Active Directory Users and Computers" (available from various menus or run "dsa.msc"):
+
+Select the OU where the user accounts are located. (By default this is the Users node; however, accounts may be under other organization-defined OUs.)
+
+Right-click the user account and select "Properties".
+
+Select the "Account" tab.
+
+Check "Smart card is required for interactive logon" in the "Account Options" area.</fixtext>
+            <fix id="F-57851r849060_fix" />
+            <check system="C-57900r849059_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Open "PowerShell".
+
+Enter the following:
+
+"Get-ADUser -Filter {(Enabled -eq $True) -and (SmartcardLogonRequired -eq $False)} | FT Name"
+("DistinguishedName" may be substituted for "Name" for more detailed output.)
+
+If any user accounts, including administrators, are listed, this is a finding.
+
+Alternately:
+
+To view sample accounts in "Active Directory Users and Computers" (available from various menus or run "dsa.msc"):
+
+Select the Organizational Unit (OU) where the user accounts are located. (By default, this is the Users node; however, accounts may be under other organization-defined OUs.)
+
+Right-click the sample user account and select "Properties".
+
+Select the "Account" tab.
+
+If any user accounts, including administrators, do not have "Smart card is required for interactive logon" checked in the "Account Options" area, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254416">
+        <title>SRG-OS-000423-GPOS-00187</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254416r958908_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000320</version>
+            <title>Windows Server 2022 domain controllers must require LDAP access signing.</title>
+            <description>&lt;VulnDiscussion&gt;Unsigned network traffic is susceptible to man-in-the-middle attacks, where an intruder captures packets between the server and the client and modifies them before forwarding them to the client. In the case of an LDAP server, this means that an attacker could cause a client to make decisions based on false records from the LDAP directory. The risk of an attacker pulling this off can be decreased by implementing strong physical security measures to protect the network infrastructure. Furthermore, implementing Internet Protocol security (IPsec) authentication header mode (AH), which performs mutual authentication and packet integrity for Internet Protocol (IP) traffic, can make all types of man-in-the-middle attacks extremely difficult.
+
+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002418</ident>
+            <ident system="http://cyber.mil/cci">CCI-002421</ident>
+            <fixtext fixref="F-57852r849063_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Domain controller: LDAP server signing requirements to "Require signing".</fixtext>
+            <fix id="F-57852r849063_fix" />
+            <check system="C-57901r849062_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\NTDS\Parameters\
+
+Value Name: LDAPServerIntegrity
+
+Value Type: REG_DWORD
+Value: 0x00000002 (2)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254417">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254417r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000330</version>
+            <title>Windows Server 2022 domain controllers must be configured to allow reset of machine account passwords.</title>
+            <description>&lt;VulnDiscussion&gt;Enabling this setting on all domain controllers in a domain prevents domain members from changing their computer account passwords. If these passwords are weak or compromised, the inability to change them may leave these computers vulnerable.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57853r849066_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Domain controller: Refuse machine account password changes to "Disabled".</fixtext>
+            <fix id="F-57853r849066_fix" />
+            <check system="C-57902r849065_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\
+
+Value Name: RefusePasswordChange
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254418">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254418r958472_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000340</version>
+            <title>Windows Server 2022 Access this computer from the network user right must only be assigned to the Administrators, Authenticated Users, and 
+Enterprise Domain Controllers groups on domain controllers.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Access this computer from the network" right may access resources on the system, and this right must be limited to those requiring it.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57854r849069_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Access this computer from the network to include only the following accounts or groups:
+
+- Administrators
+- Authenticated Users
+- Enterprise Domain Controllers</fixtext>
+            <fix id="F-57854r849069_fix" />
+            <check system="C-57903r849068_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Access this computer from the network" right, this is a finding.
+
+- Administrators
+- Authenticated Users
+- Enterprise Domain Controllers
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeNetworkLogonRight" user right, this is a finding.
+
+S-1-5-32-544 (Administrators)
+S-1-5-11 (Authenticated Users)
+S-1-5-9 (Enterprise Domain Controllers)
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254419">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254419r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000350</version>
+            <title>Windows Server 2022 Add workstations to domain user right must only be assigned to the Administrators group on domain controllers.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Add workstations to domain" right may add computers to a domain. This could result in unapproved or incorrectly configured systems being added to a domain.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57855r849072_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Add workstations to domain to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57855r849072_fix" />
+            <check system="C-57904r849071_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. It is NA for other systems.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Add workstations to domain" right, this is a finding.
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeMachineAccountPrivilege" user right, this is a finding.
+
+S-1-5-32-544 (Administrators)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254420">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254420r958472_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000360</version>
+            <title>Windows Server 2022 Allow log on through Remote Desktop Services user right must only be assigned to the Administrators group on domain controllers.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Allow log on through Remote Desktop Services" user right can access a system through Remote Desktop.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57856r849075_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Allow log on through Remote Desktop Services to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57856r849075_fix" />
+            <check system="C-57905r849074_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers, it is NA for other systems.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Allow log on through Remote Desktop Services" user right, this is a finding.
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeRemoteInteractiveLogonRight" user right, this is a finding.
+
+S-1-5-32-544 (Administrators)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254421">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254421r958472_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000370</version>
+            <title>Windows Server 2022 Deny access to this computer from the network user right on domain controllers must be configured to prevent unauthenticated access.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Deny access to this computer from the network" user right defines the accounts that are prevented from logging on from the network.
+
+The Guests group must be assigned this right to prevent unauthenticated 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57857r849078_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Deny access to this computer from the network to include the following:
+
+- Guests Group</fixtext>
+            <fix id="F-57857r849078_fix" />
+            <check system="C-57906r849077_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. A separate version applies to other systems.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If the following accounts or groups are not defined for the "Deny access to this computer from the network" user right, this is a finding:
+
+- Guests Group
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If the following SIDs are not defined for the "SeDenyNetworkLogonRight" user right, this is a finding.
+
+S-1-5-32-546 (Guests)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254422">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254422r958472_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000380</version>
+            <title>Windows Server 2022 Deny log on as a batch job user right on domain controllers must be configured to prevent unauthenticated access.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Deny log on as a batch job" user right defines accounts that are prevented from logging on to the system as a batch job, such as Task Scheduler.
+
+The Guests group must be assigned to prevent unauthenticated 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57858r849081_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Deny log on as a batch job to include the following:
+
+- Guests Group</fixtext>
+            <fix id="F-57858r849081_fix" />
+            <check system="C-57907r849080_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. A separate version applies to other systems.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If the following accounts or groups are not defined for the "Deny log on as a batch job" user right, this is a finding:
+
+- Guests Group
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If the following SID(s) are not defined for the "SeDenyBatchLogonRight" user right, this is a finding:
+
+S-1-5-32-546 (Guests)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254423">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254423r958472_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000390</version>
+            <title>Windows Server 2022 Deny log on as a service user right must be configured to include no accounts or groups (blank) on domain controllers.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Deny log on as a service" user right defines accounts that are denied logon as a service.
+
+Incorrect configurations could prevent services from starting and result in a denial of 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57859r849084_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Deny log on as a service to include no entries (blank).</fixtext>
+            <fix id="F-57859r849084_fix" />
+            <check system="C-57908r849083_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. A separate version applies to other systems.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups are defined for the "Deny log on as a service" user right, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs are granted the "SeDenyServiceLogonRight" user right, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254424">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254424r958472_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000400</version>
+            <title>Windows Server 2022 Deny log on locally user right on domain controllers must be configured to prevent unauthenticated access.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Deny log on locally" user right defines accounts that are prevented from logging on interactively.
+
+The Guests group must be assigned this right to prevent unauthenticated 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57860r849087_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Deny log on locally to include the following:
+
+- Guests Group</fixtext>
+            <fix id="F-57860r849087_fix" />
+            <check system="C-57909r849086_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. A separate version applies to other systems.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If the following accounts or groups are not defined for the "Deny log on locally" user right, this is a finding:
+
+- Guests Group
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If the following SID(s) are not defined for the "SeDenyInteractiveLogonRight" user right, this is a finding:
+
+S-1-5-32-546 (Guests)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254425">
+        <title>SRG-OS-000297-GPOS-00115</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254425r958672_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000410</version>
+            <title>Windows Server 2022 Deny log on through Remote Desktop Services user right on domain controllers must be configured to prevent unauthenticated access.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services.
+
+The Guests group must be assigned this right to prevent unauthenticated 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002314</ident>
+            <fixtext fixref="F-57861r849090_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Deny log on through Remote Desktop Services to include the following:
+
+- Guests Group</fixtext>
+            <fix id="F-57861r849090_fix" />
+            <check system="C-57910r849089_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. A separate version applies to other systems.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding:
+
+- Guests Group
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If the following SID(s) are not defined for the "SeDenyRemoteInteractiveLogonRight" user right, this is a finding.
+
+S-1-5-32-546 (Guests)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254426">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254426r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000420</version>
+            <title>Windows Server 2022 Enable computer and user accounts to be trusted for delegation user right must only be assigned to the Administrators group on domain controllers.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Enable computer and user accounts to be trusted for delegation" user right allows the "Trusted for Delegation" setting to be changed. This could allow unauthorized users to impersonate 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57862r849093_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Enable computer and user accounts to be trusted for delegation to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57862r849093_fix" />
+            <check system="C-57911r849092_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to domain controllers. A separate version applies to other systems.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Enable computer and user accounts to be trusted for delegation" user right, this is a finding.
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeEnableDelegationPrivilege" user right, this is a finding.
+
+S-1-5-32-544 (Administrators)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254427">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254427r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-DC-000430</version>
+            <title>The password for the krbtgt account on a domain must be reset at least every 180 days.</title>
+            <description>&lt;VulnDiscussion&gt;The krbtgt account acts as a service account for the Kerberos Key Distribution Center (KDC) service. The account and password are created when a domain is created and the password is typically not changed. If the krbtgt account is compromised, attackers can create valid Kerberos Ticket Granting Tickets (TGT).
+
+The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and the amount of time equal to or greater than the maximum Kerberos ticket lifetime, and changing again reduces the risk of issues.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57863r849096_fix">Reset the password for the krbtgt account a least every 180 days. The password must be changed twice to effectively remove the password history. Changing once, waiting for replication to complete and changing again reduces the risk of issues. Changing twice in rapid succession forces clients to re-authenticate (including application services) but is desired if a compromise is suspected.
+
+PowerShell scripts are available to accomplish this such as at the following link:
+
+https://gallery.technet.microsoft.com/Reset-the-krbtgt-account-581a9e51
+
+Open "Active Directory Users and Computers" (available from various menus or run "dsa.msc").
+
+Select "Advanced Features" in the "View" menu if not previously selected.
+
+Select the "Users" node.
+
+Right-click on the krbtgt account and select "Reset password".
+
+Enter a password that meets password complexity requirements.
+
+Clear the "User must change password at next logon" check box.
+
+The system will automatically change this to a system-generated complex password.</fixtext>
+            <fix id="F-57863r849096_fix" />
+            <check system="C-57912r849095_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This requirement is applicable to domain controllers; it is NA for other systems. 
+
+Open "Windows PowerShell".
+
+Enter "Get-ADUser krbtgt -Property PasswordLastSet".
+
+If the "PasswordLastSet" date is more than 180 days old, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254428">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254428r958726_rule" weight="10.0" severity="high">
+            <version>WN22-MS-000010</version>
+            <title>Windows Server 2022 must only allow administrators responsible for the member server or standalone or nondomain-joined system to have Administrator rights on the system.</title>
+            <description>&lt;VulnDiscussion&gt;An account that does not have Administrator duties must not have Administrator rights. Such rights would allow the account to bypass or modify required security restrictions on that machine and make it vulnerable to attack.
+
+System administrators must log on to systems using only accounts with the minimum level of authority necessary.
+
+For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group (see V-243468 in the Active Directory Domain STIG). Restricting highly privileged accounts from the local Administrators group helps mitigate the risk of privilege escalation resulting from credential theft attacks.
+
+Standard user accounts must not be members of the built-in Administrators 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57864r849099_fix">Configure the local "Administrators" group to include only administrator groups or accounts responsible for administration of the system.
+
+For domain-joined member servers, replace the Domain Admins group with a domain member server administrator group. 
+
+Remove any standard user accounts.</fixtext>
+            <fix id="F-57864r849099_fix" />
+            <check system="C-57913r849098_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.
+
+Open "Computer Management".
+
+Navigate to "Groups" under "Local Users and Groups".
+
+Review the local "Administrators" group.
+
+Only administrator groups or accounts responsible for administration of the system may be members of the group.
+
+For domain-joined member servers, the Domain Admins group must be replaced by a domain member server administrator group.
+
+Standard user accounts must not be members of the local Administrator group.
+
+If accounts that do not have responsibility for administration of the system are members of the local Administrators group, this is a finding.
+
+If the built-in Administrator account or other required administrative accounts are found on the system, this is not a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254429">
+        <title>SRG-OS-000134-GPOS-00068</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254429r958518_rule" weight="10.0" severity="medium">
+            <version>WN22-MS-000020</version>
+            <title>Windows Server 2022 local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain-joined member servers.</title>
+            <description>&lt;VulnDiscussion&gt;A compromised local administrator account can provide means for an attacker to move laterally between domain systems.
+
+With User Account Control enabled, filtering the privileged token for local administrator accounts will prevent the elevated privileges of these accounts from being used over the network.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001084</ident>
+            <fixtext fixref="F-57865r849102_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; MS Security Guide &gt;&gt; Apply UAC restrictions to local accounts on network logons to "Enabled".
+
+This policy setting requires the installation of the SecGuide custom templates included with the STIG package. "SecGuide.admx" and " SecGuide.adml" must be copied to the \Windows\PolicyDefinitions and \Windows\PolicyDefinitions\en-US directories respectively.</fixtext>
+            <fix id="F-57865r849102_fix" />
+            <check system="C-57914r849101_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers. For domain controllers and standalone or nondomain-joined systems, this is NA.
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive:  HKEY_LOCAL_MACHINE
+Registry Path:  \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
+
+Value Name:  LocalAccountTokenFilterPolicy
+
+Type:  REG_DWORD
+Value: 0x00000000 (0)
+
+This setting may cause issues with some network scanning tools if local administrative accounts are used remotely. Scans must use domain accounts where possible. If a local administrative account must be used, temporarily enabling the privileged token by configuring the registry value to "1" may be required.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254430">
+        <title>SRG-OS-000095-GPOS-00049</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254430r958478_rule" weight="10.0" severity="medium">
+            <version>WN22-MS-000030</version>
+            <title>Windows Server 2022 local users on domain-joined member servers must not be enumerated.</title>
+            <description>&lt;VulnDiscussion&gt;The username is one part of logon credentials that could be used to gain access to a system. Preventing the enumeration of users limits this information to 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000381</ident>
+            <fixtext fixref="F-57866r849105_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Logon &gt;&gt; Enumerate local users on domain-joined computers to "Disabled".</fixtext>
+            <fix id="F-57866r849105_fix" />
+            <check system="C-57915r849104_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers. For domain controllers and standalone or nondomain-joined systems, this is NA.
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\System\
+
+Value Name: EnumerateLocalUsers
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254431">
+        <title>SRG-OS-000379-GPOS-00164</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254431r971545_rule" weight="10.0" severity="medium">
+            <version>WN22-MS-000040</version>
+            <title>Windows Server 2022 must restrict unauthenticated Remote Procedure Call (RPC) clients from connecting to the RPC server on domain-joined member servers and standalone or nondomain-joined systems.</title>
+            <description>&lt;VulnDiscussion&gt;Unauthenticated RPC clients may allow anonymous access to sensitive information. Configuring RPC to restrict unauthenticated RPC clients from connecting to the RPC server will prevent anonymous 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001967</ident>
+            <fixtext fixref="F-57867r849108_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Remote Procedure Call &gt;&gt; Restrict Unauthenticated RPC clients to "Enabled" with "Authenticated" selected.</fixtext>
+            <fix id="F-57867r849108_fix" />
+            <check system="C-57916r849107_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers and standalone or nondomain-joined systems, it is NA for domain controllers.
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive:  HKEY_LOCAL_MACHINE
+Registry Path:  \SOFTWARE\Policies\Microsoft\Windows NT\Rpc\
+
+Value Name:  RestrictRemoteClients
+
+Type:  REG_DWORD
+Value:  0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254432">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254432r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-MS-000050</version>
+            <title>Windows Server 2022 must limit the caching of logon credentials to four or less on domain-joined member servers.</title>
+            <description>&lt;VulnDiscussion&gt;The default Windows configuration caches the last logon credentials for users who log on interactively to a system. This feature is provided for system availability reasons, such as the user's machine being disconnected from the network or domain controllers being unavailable. Even though the credential cache is well protected, if a system is attacked, an unauthorized individual may isolate the password to a domain user account using a password-cracking program and gain access to the domain.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57868r849111_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Interactive Logon: Number of previous logons to cache (in case Domain Controller is not available) to "4" logons or less.</fixtext>
+            <fix id="F-57868r849111_fix" />
+            <check system="C-57917r849110_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers. For domain controllers and standalone or nondomain-joined systems, this is NA.
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive:  HKEY_LOCAL_MACHINE
+Registry Path:  \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\
+
+Value Name:  CachedLogonsCount
+
+Value Type:  REG_SZ
+Value:  4 (or less)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254433">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254433r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-MS-000060</version>
+            <title>Windows Server 2022 must restrict remote calls to the Security Account Manager (SAM) to Administrators on domain-joined member servers and standalone or nondomain-joined systems.</title>
+            <description>&lt;VulnDiscussion&gt;The Windows SAM stores users' passwords. Restricting Remote Procedure Call (RPC) connections to the SAM to Administrators helps protect those credentials.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57869r849114_fix">Navigate to the policy Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network access: Restrict clients allowed to make remote calls to SAM. 
+
+Select "Edit Security" to configure the "Security descriptor:".
+
+Add "Administrators" in "Group or user names:" if it is not already listed (this is the default).
+
+Select "Administrators" in "Group or user names:".
+
+Select "Allow" for "Remote Access" in "Permissions for "Administrators".
+
+Click "OK".
+
+The "Security descriptor:" must be populated with "O:BAG:BAD:(A;;RC;;;BA) for the policy to be enforced.</fixtext>
+            <fix id="F-57869r849114_fix" />
+            <check system="C-57918r849113_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers and standalone or nondomain-joined systems; it is NA for domain controllers.
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\
+
+Value Name: RestrictRemoteSAM
+
+Value Type: REG_SZ
+Value: O:BAG:BAD:(A;;RC;;;BA)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254434">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254434r958472_rule" weight="10.0" severity="medium">
+            <version>WN22-MS-000070</version>
+            <title>Windows Server 2022 Access this computer from the network user right must only be assigned to the Administrators and Authenticated Users groups on domain-joined member servers and standalone or nondomain-joined systems.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Access this computer from the network" user right may access resources on the system, and this right must be limited to those requiring it.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57870r849117_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Access this computer from the network to include only the following accounts or groups:
+
+- Administrators
+- Authenticated Users</fixtext>
+            <fix id="F-57870r849117_fix" />
+            <check system="C-57919r849116_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Access this computer from the network" user right, this is a finding:
+
+- Administrators
+- Authenticated Users
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeNetworkLogonRight" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)
+S-1-5-11 (Authenticated Users)
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254435">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254435r958472_rule" weight="10.0" severity="medium">
+            <version>WN22-MS-000080</version>
+            <title>Windows Server 2022 Deny access to this computer from the network user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and local accounts and from unauthenticated access on all systems.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Deny access to this computer from the network" user right defines the accounts that are prevented from logging on from the network.
+
+In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain.
+
+Local accounts on domain-joined systems must also be assigned this right to decrease the risk of lateral movement resulting from credential theft attacks.
+
+The Guests group must be assigned this right to prevent unauthenticated 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57871r849120_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Deny access to this computer from the network to include the following:
+
+Domain Systems Only:
+- Enterprise Admins group
+- Domain Admins group
+- "Local account and member of Administrators group" or "Local account" (see Note below)
+
+All Systems:
+- Guests group
+
+Note: These are built-in security groups. "Local account" is more restrictive but may cause issues on servers such as systems that provide failover clustering.</fixtext>
+            <fix id="F-57871r849120_fix" />
+            <check system="C-57920r849119_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If the following accounts or groups are not defined for the "Deny access to this computer from the network" user right, this is a finding:
+
+Domain Systems Only:
+- Enterprise Admins group
+- Domain Admins group
+- "Local account and member of Administrators group" or "Local account" (see Note below)
+
+All Systems:
+- Guests group
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If the following SIDs are not defined for the "SeDenyNetworkLogonRight" user right, this is a finding.
+
+Domain Systems Only:
+S-1-5-root domain-519 (Enterprise Admins)
+S-1-5-domain-512 (Domain Admins)
+S-1-5-114 ("Local account and member of Administrators group") or S-1-5-113 ("Local account")
+
+All Systems:
+S-1-5-32-546 (Guests)
+
+Note: These are built-in security groups. "Local account" is more restrictive but may cause issues on servers such as systems that provide failover clustering.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254436">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254436r958472_rule" weight="10.0" severity="medium">
+            <version>WN22-MS-000090</version>
+            <title>Windows Server 2022 Deny log on as a batch job user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and from unauthenticated access on all systems.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Deny log on as a batch job" user right defines accounts that are prevented from logging on to the system as a batch job, such as Task Scheduler.
+
+In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain.
+
+The Guests group must be assigned to prevent unauthenticated 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57872r849123_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Deny log on as a batch job to include the following:
+
+Domain Systems Only:
+- Enterprise Admins Group
+- Domain Admins Group
+
+All Systems:
+- Guests Group</fixtext>
+            <fix id="F-57872r849123_fix" />
+            <check system="C-57921r849122_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If the following accounts or groups are not defined for the "Deny log on as a batch job" user right, this is a finding:
+
+Domain Systems Only:
+- Enterprise Admins Group
+- Domain Admins Group
+
+All Systems:
+- Guests Group
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If the following SIDs are not defined for the "SeDenyBatchLogonRight" user right, this is a finding.
+
+Domain Systems Only:
+S-1-5-root domain-519 (Enterprise Admins)
+S-1-5-domain-512 (Domain Admins)
+
+All Systems:
+S-1-5-32-546 (Guests)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254437">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254437r958472_rule" weight="10.0" severity="medium">
+            <version>WN22-MS-000100</version>
+            <title>Windows Server 2022 Deny log on as a service user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts. No other groups or accounts must be assigned this right.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Deny log on as a service" user right defines accounts that are denied logon as a service.
+
+In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain.
+
+Incorrect configurations could prevent services from starting and result in a denial of 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57873r849126_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Deny log on as a service to include the following:
+
+Domain systems:
+- Enterprise Admins Group
+- Domain Admins Group</fixtext>
+            <fix id="F-57873r849126_fix" />
+            <check system="C-57922r890546_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers. A separate version applies to domain controllers.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If the following accounts or groups are not defined for the "Deny log on as a service" user right on domain-joined systems, this is a finding:
+
+- Enterprise Admins Group
+- Domain Admins Group
+
+If any accounts or groups are defined for the "Deny log on as a service" user right on nondomain-joined systems, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If the following SIDs are not defined for the "SeDenyServiceLogonRight" user right on domain-joined systems, this is a finding:
+
+S-1-5-root domain-519 (Enterprise Admins)
+S-1-5-domain-512 (Domain Admins)
+
+If any SIDs are defined for the user right on nondomain-joined systems, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254438">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254438r958472_rule" weight="10.0" severity="medium">
+            <version>WN22-MS-000110</version>
+            <title>Windows Server 2022 Deny log on locally user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and from unauthenticated access on all systems.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Deny log on locally" user right defines accounts that are prevented from logging on interactively.
+
+In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain.
+
+The Guests group must be assigned this right to prevent unauthenticated 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57874r849129_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Deny log on locally to include the following:
+
+Domain Systems Only:
+- Enterprise Admins Group
+- Domain Admins Group
+
+All Systems:
+- Guests Group</fixtext>
+            <fix id="F-57874r849129_fix" />
+            <check system="C-57923r849128_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If the following accounts or groups are not defined for the "Deny log on locally" user right, this is a finding:
+
+Domain Systems Only:
+- Enterprise Admins Group
+- Domain Admins Group
+
+All Systems:
+- Guests Group
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If the following SIDs are not defined for the "SeDenyInteractiveLogonRight" user right, this is a finding:
+
+Domain Systems Only:
+S-1-5-root domain-519 (Enterprise Admins)
+S-1-5-domain-512 (Domain Admins)
+
+All Systems:
+S-1-5-32-546 (Guests)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254439">
+        <title>SRG-OS-000297-GPOS-00115</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254439r958672_rule" weight="10.0" severity="medium">
+            <version>WN22-MS-000120</version>
+            <title>Windows Server 2022 Deny log on through Remote Desktop Services user right on domain-joined member servers must be configured to prevent access from highly privileged domain accounts and all local accounts and from unauthenticated access on all systems.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Deny log on through Remote Desktop Services" user right defines the accounts that are prevented from logging on using Remote Desktop Services.
+
+In an Active Directory Domain, denying logons to the Enterprise Admins and Domain Admins groups on lower-trust systems helps mitigate the risk of privilege escalation from credential theft attacks, which could lead to the compromise of an entire domain.
+
+Local accounts on domain-joined systems must also be assigned this right to decrease the risk of lateral movement resulting from credential theft attacks.
+
+The Guests group must be assigned this right to prevent unauthenticated 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002314</ident>
+            <fixtext fixref="F-57875r849132_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Deny log on through Remote Desktop Services to include the following:
+
+Domain Systems Only:
+- Enterprise Admins group
+- Domain Admins group
+- Local account (see Note below)
+
+All Systems:
+- Guests group
+
+Note: "Local account" is referring to the Windows built-in security group.</fixtext>
+            <fix id="F-57875r849132_fix" />
+            <check system="C-57924r849131_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If the following accounts or groups are not defined for the "Deny log on through Remote Desktop Services" user right, this is a finding:
+
+Domain Systems Only:
+- Enterprise Admins group
+- Domain Admins group
+- Local account (see Note below)
+
+All Systems:
+- Guests group
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If the following SIDs are not defined for the "SeDenyRemoteInteractiveLogonRight" user right, this is a finding.
+
+Domain Systems Only:
+S-1-5-root domain-519 (Enterprise Admins)
+S-1-5-domain-512 (Domain Admins)
+S-1-5-113 ("Local account")
+
+All Systems:
+S-1-5-32-546 (Guests)
+
+Note: "Local account" is referring to the Windows built-in security group.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254440">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254440r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-MS-000130</version>
+            <title>Windows Server 2022 Enable computer and user accounts to be trusted for delegation user right must not be assigned to any groups or accounts on domain-joined member servers and standalone or nondomain-joined systems.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Enable computer and user accounts to be trusted for delegation" user right allows the "Trusted for Delegation" setting to be changed. This could allow unauthorized users to impersonate 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57876r849135_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Enable computer and user accounts to be trusted for delegation to be defined but containing no entries (blank).</fixtext>
+            <fix id="F-57876r849135_fix" />
+            <check system="C-57925r849134_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This applies to member servers and standalone or nondomain-joined systems. A separate version applies to domain controllers.
+
+Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups are granted the "Enable computer and user accounts to be trusted for delegation" user right, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs are granted the "SeEnableDelegationPrivilege" user right, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254441">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254441r991589_rule" weight="10.0" severity="high">
+            <version>WN22-MS-000140</version>
+            <title>Windows Server 2022 must be running Credential Guard on domain-joined member servers.</title>
+            <description>&lt;VulnDiscussion&gt;Credential Guard uses virtualization-based security to protect data that could be used in credential theft attacks if compromised. This authentication information, which was stored in the Local Security Authority (LSA) in previous versions of Windows, is isolated from the rest of operating system and can only be accessed by privileged 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57877r849138_fix">Configure the policy value for Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; Device Guard &gt;&gt; Turn On Virtualization Based Security to "Enabled" with "Enabled with UEFI lock" selected for "Credential Guard Configuration".
+
+A Microsoft article on Credential Guard system requirement can be found at the following link:
+
+https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements
+
+Severity Override Guidance: The AO can allow the severity override if they have reviewed the overall protection provided to the affected servers that are not capable of complying with the Credential Guard requirement. Items that must be reviewed/considered for compliance or mitigation for non-Credential Guard compliance are:
+
+The use of Microsoft Local Administrator Password Solution (LAPS) or similar products to control different local administrative passwords for all affected servers. This is to include a strict password change requirement (60 days or less).
+....
+Strict separation of roles and duties. Server administrator credentials cannot be used on Windows 10 desktop to administer it. Documentation of all exceptions must be supplied.
+....
+Use of a Privileged Access Workstation (PAW) and adherence to the Clean Source principle for administering affected servers. 
+....
+Boundary Protection that is currently in place to protect from vulnerabilities in the network/servers.
+....
+Windows Defender rule block credential stealing from LSASS.exe is applied. This rule can only be applied if Windows Defender is in use.
+....
+The overall number of vulnerabilities that are unmitigated on the network/servers.</fixtext>
+            <fix id="F-57877r849138_fix" />
+            <check system="C-57926r849137_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>For domain controllers and standalone or nondomain-joined systems, this is NA.
+
+Open "PowerShell" with elevated privileges (run as administrator).
+
+Enter the following:
+
+"Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard"
+
+If "SecurityServicesRunning" does not include a value of "1" (e.g., "{1, 2}"), this is a finding.
+
+Alternately:
+
+Run "System Information".
+
+Under "System Summary", verify the following:
+
+If "Device Guard Security Services Running" does not list "Credential Guard", this is a finding.
+
+The policy settings referenced in the Fix section will configure the following registry value. However, due to hardware requirements, the registry value alone does not ensure proper function.
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\
+
+Value Name: LsaCfgFlags
+Value Type: REG_DWORD
+Value: 0x00000001 (1) (Enabled with UEFI lock)
+
+A Microsoft article on Credential Guard system requirement can be found at the following link:
+
+https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254442">
+        <title>SRG-OS-000066-GPOS-00034</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254442r958448_rule" weight="10.0" severity="medium">
+            <version>WN22-PK-000010</version>
+            <title>Windows Server 2022 must have the DoD Root Certificate Authority (CA) certificates installed in the Trusted Root Store.</title>
+            <description>&lt;VulnDiscussion&gt;To ensure secure DoD websites and DoD-signed code are properly validated, the system must trust the DoD Root CAs. The DoD root certificates will ensure that the trust chain is established for server certificates issued from the DoD CAs.
+
+Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000185</ident>
+            <ident system="http://cyber.mil/cci">CCI-002470</ident>
+            <fixtext fixref="F-57878r921942_fix">Install the DoD Root CA certificates:
+
+DoD Root CA 3
+DoD Root CA 4
+DoD Root CA 5
+DoD Root CA 6
+
+The InstallRoot tool is available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. Certificate bundles published by the PKI can be found at https://crl.gds.disa.mil/.</fixtext>
+            <fix id="F-57878r921942_fix" />
+            <check system="C-57927r921941_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>The certificates and thumbprints referenced below apply to unclassified systems; refer to PKE documentation for other networks.
+
+Open "Windows PowerShell" as an administrator.
+
+Execute the following command:
+
+Get-ChildItem -Path Cert:Localmachine\root | Where Subject -Like "*DoD*" | FL Subject, Thumbprint, NotAfter
+
+If the following certificate "Subject" and "Thumbprint" information is not displayed, this is a finding. 
+
+Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US
+Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB
+NotAfter: 12/30/2029
+
+Subject: CN=DoD Root CA 4, OU=PKI, OU=DoD, O=U.S. Government, C=US
+Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026
+NotAfter: 7/25/2032
+
+Subject: CN=DoD Root CA 5, OU=PKI, OU=DoD, O=U.S. Government, C=US
+Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B
+NotAfter: 6/14/2041
+
+Subject: CN=DoD Root CA 6, OU=PKI, OU=DoD, O=U.S. Government, C=US 
+Thumbprint : D37ECF61C0B4ED88681EF3630C4E2FC787B37AEF
+NotAfter: 1/24/2053 11:36:17 AM
+
+Alternately, use the Certificates MMC snap-in:
+
+Run "MMC".
+
+Select "File", "Add/Remove Snap-in".
+
+Select "Certificates" and click "Add".
+
+Select "Computer account" and click "Next".
+
+Select "Local computer: (the computer this console is running on)" and click "Finish".
+
+Click "OK".
+
+Expand "Certificates" and navigate to "Trusted Root Certification Authorities &gt;&gt; Certificates".
+
+For each of the DoD Root CA certificates noted below:
+
+Right-click on the certificate and select "Open".
+
+Select the "Details" tab.
+
+Scroll to the bottom and select "Thumbprint".
+
+If the DoD Root CA certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding.
+
+DoD Root CA 3
+Thumbprint: D73CA91102A2204A36459ED32213B467D7CE97FB
+Valid to: Sunday, December 30, 2029
+
+DoD Root CA 4
+Thumbprint: B8269F25DBD937ECAFD4C35A9838571723F2D026
+Valid to: Sunday, July 25, 2032
+
+DoD Root CA 5
+Thumbprint: 4ECB5CC3095670454DA1CBD410FC921F46B8564B
+Valid to: Friday, June 14, 2041
+
+DoD Root CA 6
+Thumbprint: D37ECF61C0B4ED88681EF3630C4E2FC787B37AEFB
+Valid to: Friday, January 24, 2053</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254443">
+        <title>SRG-OS-000066-GPOS-00034</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254443r958448_rule" weight="10.0" severity="medium">
+            <version>WN22-PK-000020</version>
+            <title>Windows Server 2022 must have the DoD Interoperability Root Certificate Authority (CA) cross-certificates installed in the Untrusted Certificates Store on unclassified systems.</title>
+            <description>&lt;VulnDiscussion&gt;To ensure users do not experience denial of service when performing certificate-based authentication to DoD websites due to the system chaining to a root other than DoD Root CAs, the DoD Interoperability Root CA cross-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems.
+
+Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000185</ident>
+            <ident system="http://cyber.mil/cci">CCI-002470</ident>
+            <fixtext fixref="F-57879r890552_fix">Install the DoD Interoperability Root CA cross-certificates on unclassified systems.
+
+Issued To - Issued By - Thumbprint
+
+DoD Root CA 3- DoD Interoperability Root CA 2 - 49CBE933151872E17C8EAE7F0ABA97FB610F6477
+
+Administrators must run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user.
+
+The FBCA Cross-Certificate Remover Tool and User Guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. Certificate bundles published by the PKI can be found at https://crl.gds.disa.mil/.</fixtext>
+            <fix id="F-57879r890552_fix" />
+            <check system="C-57928r890551_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This is applicable to unclassified systems. It is NA for others.
+
+Open "PowerShell" as an administrator.
+
+Execute the following command:
+
+Get-ChildItem -Path Cert:Localmachine\disallowed | Where {$_.Issuer -Like "*DoD Interoperability*" -and $_.Subject -Like "*DoD*"} | FL Subject, Issuer, Thumbprint, NotAfter
+
+If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. 
+
+Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US
+Issuer: CN=DoD Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US
+Thumbprint: 49CBE933151872E17C8EAE7F0ABA97FB610F6477
+NotAfter: 11/16/2024 09:57:16 AM
+
+Alternately, use the Certificates MMC snap-in:
+
+Run "MMC".
+
+Select "File", "Add/Remove Snap-in".
+
+Select "Certificates" and click "Add".
+
+Select "Computer account" and click "Next".
+
+Select "Local computer: (the computer this console is running on)" and click "Finish".
+
+Click "OK".
+
+Expand "Certificates" and navigate to Untrusted Certificates &gt;&gt; Certificates.
+
+For each certificate with "DoD Root CA..." under "Issued To" and "DoD Interoperability Root CA..." under "Issued By":
+
+Right-click on the certificate and select "Open".
+
+Select the "Details" tab.
+
+Scroll to the bottom and select "Thumbprint".
+
+If the certificates below are not listed or the value for the "Thumbprint" field is not as noted, this is a finding.
+
+Issued To: DoD Root CA 3
+Issued By: DoD Interoperability Root CA 2
+Thumbprint: 49CBE933151872E17C8EAE7F0ABA97FB610F6477
+Valid to: Wednesday, November 16, 2024</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254444">
+        <title>SRG-OS-000066-GPOS-00034</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254444r958448_rule" weight="10.0" severity="medium">
+            <version>WN22-PK-000030</version>
+            <title>Windows Server 2022 must have the US DoD CCEB Interoperability Root CA cross-certificates in the Untrusted Certificates Store on unclassified systems.</title>
+            <description>&lt;VulnDiscussion&gt;To ensure users do not experience denial of service when performing certificate-based authentication to DoD websites due to the system chaining to a root other than DoD Root CAs, the US DoD CCEB Interoperability Root CA cross-certificates must be installed in the Untrusted Certificate Store. This requirement only applies to unclassified systems.
+
+Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000185</ident>
+            <ident system="http://cyber.mil/cci">CCI-002470</ident>
+            <fixtext fixref="F-57880r894342_fix">Install the US DoD CCEB Interoperability Root CA cross-certificate on unclassified systems.
+
+Issued To - Issued By - Thumbprint
+
+DoD Root CA 3 - US DoD CCEB Interoperability Root CA 2 - 9B74964506C7ED9138070D08D5F8B969866560C8
+
+Administrators must run the Federal Bridge Certification Authority (FBCA) Cross-Certificate Removal Tool once as an administrator and once as the current user.
+
+The FBCA Cross-Certificate Remover Tool and User Guide are available on Cyber Exchange at https://cyber.mil/pki-pke/tools-configuration-files. PKI can be found at https://crl.gds.disa.mil/.</fixtext>
+            <fix id="F-57880r894342_fix" />
+            <check system="C-57929r890554_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This is applicable to unclassified systems. It is NA for others.
+
+Open "PowerShell" as an administrator.
+
+Execute the following command:
+
+Get-ChildItem -Path Cert:Localmachine\disallowed | Where Issuer -Like "*CCEB Interoperability*" | FL Subject, Issuer, Thumbprint, NotAfter
+
+If the following certificate "Subject", "Issuer", and "Thumbprint" information is not displayed, this is a finding. 
+
+Subject: CN=DoD Root CA 3, OU=PKI, OU=DoD, O=U.S. Government, C=US
+Issuer: CN=US DoD CCEB Interoperability Root CA 2, OU=PKI, OU=DoD, O=U.S. Government, C=US
+Thumbprint: 9B74964506C7ED9138070D08D5F8B969866560C8
+NotAfter: 7/18/2025 9:56:22 AM
+
+Alternately, use the Certificates MMC snap-in:
+
+Run "MMC".
+
+Select "File", "Add/Remove Snap-in".
+
+Select "Certificates" and click "Add".
+
+Select "Computer account" and click "Next".
+
+Select "Local computer: (the computer this console is running on)" and click "Finish".
+
+Click "OK".
+
+Expand "Certificates" and navigate to Untrusted Certificates &gt;&gt; Certificates.
+
+For each certificate with "US DoD CCEB Interoperability Root CA ..." under "Issued By":
+
+Right-click on the certificate and select "Open".
+
+Select the "Details" tab.
+
+Scroll to the bottom and select "Thumbprint".
+
+If the certificate below is not listed or the value for the "Thumbprint" field is not as noted, this is a finding.
+
+Issued To: DoD Root CA 3
+Issued By: US DoD CCEB Interoperability Root CA 2
+Thumbprint: 9B74964506C7ED9138070D08D5F8B969866560C8
+NotAfter: 7/18/2025</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254445">
+        <title>SRG-OS-000121-GPOS-00062</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254445r958504_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000010</version>
+            <title>Windows Server 2022 must have the built-in guest account disabled.</title>
+            <description>&lt;VulnDiscussion&gt;A system faces an increased vulnerability threat if the built-in guest account is not disabled. This is a known account that exists on all Windows systems and cannot be deleted. This account is initialized during the installation of the operating system with no password assigned.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000804</ident>
+            <fixtext fixref="F-57881r849150_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Accounts: Guest account status to "Disabled".</fixtext>
+            <fix id="F-57881r849150_fix" />
+            <check system="C-57930r849149_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options.
+
+If the value for "Accounts: Guest account status" is not set to "Disabled", this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt
+
+If "EnableGuestAccount" equals "1" in the file, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254446">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254446r991589_rule" weight="10.0" severity="high">
+            <version>WN22-SO-000020</version>
+            <title>Windows Server 2022 must prevent local accounts with blank passwords from being used from the network.</title>
+            <description>&lt;VulnDiscussion&gt;An account without a password can allow unauthorized access to a system as only the username would be required. Password policies must prevent accounts with blank passwords from existing on a system. However, if a local account with a blank password does exist, enabling this setting will prevent network access, limiting the account to local console logon only.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57882r849153_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Accounts: Limit local account use of blank passwords to console logon only to "Enabled".</fixtext>
+            <fix id="F-57882r849153_fix" />
+            <check system="C-57931r849152_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\
+
+Value Name: LimitBlankPasswordUse
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254447">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254447r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000030</version>
+            <title>Windows Server 2022 built-in administrator account must be renamed.</title>
+            <description>&lt;VulnDiscussion&gt;The built-in administrator account is a well-known account subject to attack. Renaming this account to an unidentified name improves the protection of this account and 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57883r849156_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Accounts: Rename administrator account to a name other than "Administrator".</fixtext>
+            <fix id="F-57883r849156_fix" />
+            <check system="C-57932r849155_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options.
+
+If the value for "Accounts: Rename administrator account" is not set to a value other than "Administrator", this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt
+
+If "NewAdministratorName" is not something other than "Administrator" in the file, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254448">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254448r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000040</version>
+            <title>Windows Server 2022 built-in guest account must be renamed.</title>
+            <description>&lt;VulnDiscussion&gt;The built-in guest account is a well-known user account on all Windows systems and, as initially installed, does not require a password. This can allow access to system resources by unauthorized users. Renaming this account to an unidentified name improves the protection of this account and 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57884r849159_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Accounts: Rename guest account to a name other than "Guest".</fixtext>
+            <fix id="F-57884r849159_fix" />
+            <check system="C-57933r849158_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options.
+
+If the value for "Accounts: Rename guest account" is not set to a value other than "Guest", this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt
+
+If "NewGuestName" is not something other than "Guest" in the file, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254449">
+        <title>SRG-OS-000062-GPOS-00031</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254449r958442_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000050</version>
+            <title>Windows Server 2022 must force audit policy subcategory settings to override audit policy category settings.</title>
+            <description>&lt;VulnDiscussion&gt;Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. This setting allows administrators to enable more precise auditing capabilities.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000169</ident>
+            <fixtext fixref="F-57885r849162_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings to "Enabled".</fixtext>
+            <fix id="F-57885r849162_fix" />
+            <check system="C-57934r849161_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\
+
+Value Name: SCENoApplyLegacyAuditPolicy
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254450">
+        <title>SRG-OS-000423-GPOS-00187</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254450r958908_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000060</version>
+            <title>Windows Server 2022 setting Domain member: Digitally encrypt or sign secure channel data (always) must be configured to Enabled.</title>
+            <description>&lt;VulnDiscussion&gt;Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but not all information is encrypted. If this policy is enabled, outgoing secure channel traffic will be encrypted and signed.
+
+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002418</ident>
+            <ident system="http://cyber.mil/cci">CCI-002421</ident>
+            <fixtext fixref="F-57886r849165_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Domain member: Digitally encrypt or sign secure channel data (always) to "Enabled".</fixtext>
+            <fix id="F-57886r849165_fix" />
+            <check system="C-57935r849164_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\
+
+Value Name: RequireSignOrSeal
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254451">
+        <title>SRG-OS-000423-GPOS-00187</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254451r958908_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000070</version>
+            <title>Windows Server 2022 setting Domain member: Digitally encrypt secure channel data (when possible) must be configured to Enabled.</title>
+            <description>&lt;VulnDiscussion&gt;Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but not all information is encrypted. If this policy is enabled, outgoing secure channel traffic will be encrypted.
+
+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002418</ident>
+            <ident system="http://cyber.mil/cci">CCI-002421</ident>
+            <fixtext fixref="F-57887r849168_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Domain member: Digitally encrypt secure channel data (when possible) to "Enabled".</fixtext>
+            <fix id="F-57887r849168_fix" />
+            <check system="C-57936r849167_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\
+
+Value Name: SealSecureChannel
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254452">
+        <title>SRG-OS-000423-GPOS-00187</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254452r958908_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000080</version>
+            <title>Windows Server 2022 setting Domain member: Digitally sign secure channel data (when possible) must be configured to Enabled.</title>
+            <description>&lt;VulnDiscussion&gt;Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but the channel is not integrity checked. If this policy is enabled, outgoing secure channel traffic will be signed.
+
+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002418</ident>
+            <ident system="http://cyber.mil/cci">CCI-002421</ident>
+            <fixtext fixref="F-57888r849171_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Domain member: Digitally sign secure channel data (when possible) to "Enabled".</fixtext>
+            <fix id="F-57888r849171_fix" />
+            <check system="C-57937r849170_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\
+
+Value Name: SignSecureChannel
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254453">
+        <title>SRG-OS-000379-GPOS-00164</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254453r971545_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000090</version>
+            <title>Windows Server 2022 computer account password must not be prevented from being reset.</title>
+            <description>&lt;VulnDiscussion&gt;Computer account passwords are changed automatically on a regular basis. Disabling automatic password changes can make the system more vulnerable to malicious access. Frequent password changes can be a significant safeguard for the system. A new password for the computer account will be generated every 30 days.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001967</ident>
+            <fixtext fixref="F-57889r849174_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Domain member: Disable machine account password changes to "Disabled".</fixtext>
+            <fix id="F-57889r849174_fix" />
+            <check system="C-57938r849173_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\
+
+Value Name: DisablePasswordChange
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254454">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254454r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000100</version>
+            <title>Windows Server 2022 maximum age for machine account passwords must be configured to 30 days or less.</title>
+            <description>&lt;VulnDiscussion&gt;Computer account passwords are changed automatically on a regular basis. This setting controls the maximum password age that a machine account may have. This must be set to no more than 30 days, ensuring the machine changes its password monthly.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57890r849177_fix">This is the default configuration for this setting (30 days).
+
+Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Domain member: Maximum machine account password age to "30" or less (excluding "0", which is unacceptable).</fixtext>
+            <fix id="F-57890r849177_fix" />
+            <check system="C-57939r849176_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>This is the default configuration for this setting (30 days).
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\
+
+Value Name: MaximumPasswordAge
+
+Value Type: REG_DWORD
+Value: 0x0000001e (30) (or less, but not 0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254455">
+        <title>SRG-OS-000423-GPOS-00187</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254455r958908_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000110</version>
+            <title>Windows Server 2022 must be configured to require a strong session key.</title>
+            <description>&lt;VulnDiscussion&gt;A computer connecting to a domain controller will establish a secure channel. The secure channel connection may be subject to compromise, such as hijacking or eavesdropping, if strong session keys are not used to establish the connection. Requiring strong session keys enforces 128-bit encryption between systems.
+
+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002418</ident>
+            <ident system="http://cyber.mil/cci">CCI-002421</ident>
+            <fixtext fixref="F-57891r849180_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Domain member: Require strong (Windows 2000 or Later) session key to "Enabled".</fixtext>
+            <fix id="F-57891r849180_fix" />
+            <check system="C-57940r849179_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\
+
+Value Name: RequireStrongKey
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)
+ 
+This setting may prevent a system from being joined to a domain if not configured consistently between systems.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254456">
+        <title>SRG-OS-000028-GPOS-00009</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254456r958400_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000120</version>
+            <title>Windows Server 2022 machine inactivity limit must be set to 15 minutes or less, locking the system with the screen saver.</title>
+            <description>&lt;VulnDiscussion&gt;Unattended systems are susceptible to unauthorized use and must be locked when unattended. The screen saver must be set at a maximum of 15 minutes and be password protected. This protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.
+
+Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000029-GPOS-00010, SRG-OS-000031-GPOS-00012&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000056</ident>
+            <ident system="http://cyber.mil/cci">CCI-000057</ident>
+            <ident system="http://cyber.mil/cci">CCI-000060</ident>
+            <fixtext fixref="F-57892r849183_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Interactive logon: Machine inactivity limit to "900" seconds or less, excluding "0" which is effectively disabled.</fixtext>
+            <fix id="F-57892r849183_fix" />
+            <check system="C-57941r849182_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
+
+Value Name: InactivityTimeoutSecs
+
+Value Type: REG_DWORD
+Value: 0x00000384 (900) (or less, excluding "0" which is effectively disabled)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254457">
+        <title>SRG-OS-000023-GPOS-00006</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254457r958390_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000130</version>
+            <title>Windows Server 2022 required legal notice must be configured to display before console logon.</title>
+            <description>&lt;VulnDiscussion&gt;Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.
+
+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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000048</ident>
+            <ident system="http://cyber.mil/cci">CCI-000050</ident>
+            <ident system="http://cyber.mil/cci">CCI-001384</ident>
+            <ident system="http://cyber.mil/cci">CCI-001385</ident>
+            <ident system="http://cyber.mil/cci">CCI-001386</ident>
+            <ident system="http://cyber.mil/cci">CCI-001387</ident>
+            <ident system="http://cyber.mil/cci">CCI-001388</ident>
+            <fixtext fixref="F-57893r849186_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Interactive Logon: Message text for users attempting to log on to the following:
+
+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-57893r849186_fix" />
+            <check system="C-57942r849185_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
+
+Value Name: LegalNoticeText
+
+Value Type: REG_SZ
+Value: See message text below
+
+You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.
+
+By using this IS (which includes any device attached to this IS), you consent to the following conditions:
+
+-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
+
+-At any time, the USG may inspect and seize data stored on this IS.
+
+-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.
+
+-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.
+
+-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254458">
+        <title>SRG-OS-000023-GPOS-00006</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254458r958390_rule" weight="10.0" severity="low">
+            <version>WN22-SO-000140</version>
+            <title>Windows Server 2022 title for legal banner dialog box must be configured with the appropriate text.</title>
+            <description>&lt;VulnDiscussion&gt;Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.
+
+Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000048</ident>
+            <ident system="http://cyber.mil/cci">CCI-001384</ident>
+            <ident system="http://cyber.mil/cci">CCI-001385</ident>
+            <ident system="http://cyber.mil/cci">CCI-001386</ident>
+            <ident system="http://cyber.mil/cci">CCI-001387</ident>
+            <ident system="http://cyber.mil/cci">CCI-001388</ident>
+            <fixtext fixref="F-57894r849189_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Interactive Logon: Message title for users attempting to log on to "DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. 
+
+If an organization-defined title is used, it can in no case contravene or modify the language of the message text required in WN22-SO-000150.</fixtext>
+            <fix id="F-57894r849189_fix" />
+            <check system="C-57943r849188_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
+
+Value Name: LegalNoticeCaption
+
+Value Type: REG_SZ
+Value: See message title options below
+
+"DoD Notice and Consent Banner", "US Department of Defense Warning Statement", or an organization-defined equivalent. 
+
+If an organization-defined title is used, it can in no case contravene or modify the language of the banner text required in WN22-SO-000150.
+
+Automated tools may only search for the titles defined above. If an organization-defined title is used, a manual review will be required.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254459">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254459r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000150</version>
+            <title>Windows Server 2022 Smart Card removal option must be configured to Force Logoff or Lock Workstation.</title>
+            <description>&lt;VulnDiscussion&gt;Unattended systems are susceptible to unauthorized use and must be locked. Configuring a system to lock when a smart card is removed will ensure the system is inaccessible when unattended.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57895r849192_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Interactive logon: Smart card removal behavior to "Lock Workstation" or "Force Logoff".</fixtext>
+            <fix id="F-57895r849192_fix" />
+            <check system="C-57944r849191_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\
+ 
+Value Name: scremoveoption
+
+Value Type: REG_SZ
+Value: 1 (Lock Workstation) or 2 (Force Logoff)
+
+If configuring this on servers causes issues, such as terminating users' remote sessions, and the organization has a policy in place that any other sessions on the servers, such as administrative console logons, are manually locked or logged off when unattended or not in use, this would be acceptable. This must be documented with the Information System Security Officer (ISSO).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254460">
+        <title>SRG-OS-000423-GPOS-00187</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254460r958908_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000160</version>
+            <title>Windows Server 2022 setting Microsoft network client: Digitally sign communications (always) must be configured to Enabled.</title>
+            <description>&lt;VulnDiscussion&gt;The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB client will only communicate with an SMB server that performs SMB packet signing.
+
+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002418</ident>
+            <ident system="http://cyber.mil/cci">CCI-002421</ident>
+            <fixtext fixref="F-57896r849195_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Microsoft network client: Digitally sign communications (always) to "Enabled".</fixtext>
+            <fix id="F-57896r849195_fix" />
+            <check system="C-57945r849194_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\
+
+Value Name: RequireSecuritySignature
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254461">
+        <title>SRG-OS-000423-GPOS-00187</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254461r958908_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000170</version>
+            <title>Windows Server 2022 setting Microsoft network client: Digitally sign communications (if server agrees) must be configured to Enabled.</title>
+            <description>&lt;VulnDiscussion&gt;The server message block (SMB) protocol provides the basis for many network operations. If this policy is enabled, the SMB client will request packet signing when communicating with an SMB server that is enabled or required to perform SMB packet signing.
+
+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002418</ident>
+            <ident system="http://cyber.mil/cci">CCI-002421</ident>
+            <fixtext fixref="F-57897r849198_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Microsoft network client: Digitally sign communications (if server agrees) to "Enabled".</fixtext>
+            <fix id="F-57897r849198_fix" />
+            <check system="C-57946r849197_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\
+
+Value Name: EnableSecuritySignature
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254462">
+        <title>SRG-OS-000074-GPOS-00042</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254462r987796_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000180</version>
+            <title>Windows Server 2022 unencrypted passwords must not be sent to third-party Server Message Block (SMB) servers.</title>
+            <description>&lt;VulnDiscussion&gt;Some non-Microsoft SMB servers only support unencrypted (plain-text) password authentication. Sending plain-text passwords across the network when authenticating to an SMB server reduces the overall security of the environment. Check with the vendor of the SMB server to determine if there is a way to support encrypted password 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000197</ident>
+            <fixtext fixref="F-57898r849201_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Microsoft Network Client: Send unencrypted password to third-party SMB servers to "Disabled".</fixtext>
+            <fix id="F-57898r849201_fix" />
+            <check system="C-57947r849200_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive:  HKEY_LOCAL_MACHINE
+Registry Path:  \SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\
+
+Value Name:  EnablePlainTextPassword
+
+Value Type:  REG_DWORD
+Value:  0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254463">
+        <title>SRG-OS-000423-GPOS-00187</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254463r958908_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000190</version>
+            <title>Windows Server 2022 setting Microsoft network server: Digitally sign communications (always) must be configured to Enabled.</title>
+            <description>&lt;VulnDiscussion&gt;The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will only communicate with an SMB client that performs SMB packet signing.
+
+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002418</ident>
+            <ident system="http://cyber.mil/cci">CCI-002421</ident>
+            <fixtext fixref="F-57899r849204_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Microsoft network server: Digitally sign communications (always) to "Enabled".</fixtext>
+            <fix id="F-57899r849204_fix" />
+            <check system="C-57948r849203_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\
+
+Value Name: RequireSecuritySignature
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254464">
+        <title>SRG-OS-000423-GPOS-00187</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254464r958908_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000200</version>
+            <title>Windows Server 2022 setting Microsoft network server: Digitally sign communications (if client agrees) must be configured to Enabled.</title>
+            <description>&lt;VulnDiscussion&gt;The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will negotiate SMB packet signing as requested by the client.
+
+Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000424-GPOS-00188&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002418</ident>
+            <ident system="http://cyber.mil/cci">CCI-002421</ident>
+            <fixtext fixref="F-57900r849207_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Microsoft network server: Digitally sign communications (if client agrees) to "Enabled".</fixtext>
+            <fix id="F-57900r849207_fix" />
+            <check system="C-57949r849206_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\
+
+Value Name: EnableSecuritySignature
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254465">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254465r991589_rule" weight="10.0" severity="high">
+            <version>WN22-SO-000210</version>
+            <title>Windows Server 2022 must not allow anonymous SID/Name translation.</title>
+            <description>&lt;VulnDiscussion&gt;Allowing anonymous SID/Name translation can provide sensitive information for accessing a system. Only authorized users must be able to perform such translations.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57901r849210_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network access: Allow anonymous SID/Name translation to "Disabled".</fixtext>
+            <fix id="F-57901r849210_fix" />
+            <check system="C-57950r849209_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options.
+
+If the value for "Network access: Allow anonymous SID/Name translation" is not set to "Disabled", this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254466">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254466r991589_rule" weight="10.0" severity="high">
+            <version>WN22-SO-000220</version>
+            <title>Windows Server 2022 must not allow anonymous enumeration of Security Account Manager (SAM) accounts.</title>
+            <description>&lt;VulnDiscussion&gt;Anonymous enumeration of SAM accounts allows anonymous logon users (null session connections) to list all accounts names, thus providing a list of potential points to attack 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57902r849213_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network access: Do not allow anonymous enumeration of SAM accounts to "Enabled".</fixtext>
+            <fix id="F-57902r849213_fix" />
+            <check system="C-57951r849212_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\
+
+Value Name: RestrictAnonymousSAM
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254467">
+        <title>SRG-OS-000138-GPOS-00069</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254467r958524_rule" weight="10.0" severity="high">
+            <version>WN22-SO-000230</version>
+            <title>Windows Server 2022 must not allow anonymous enumeration of shares.</title>
+            <description>&lt;VulnDiscussion&gt;Allowing anonymous logon users (null session connections) to list all account names and enumerate all shared resources can provide a map of potential points to attack 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001090</ident>
+            <fixtext fixref="F-57903r849216_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network access: Do not allow anonymous enumeration of SAM accounts and shares to "Enabled".</fixtext>
+            <fix id="F-57903r849216_fix" />
+            <check system="C-57952r849215_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\
+
+Value Name: RestrictAnonymous
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254468">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254468r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000240</version>
+            <title>Windows Server 2022 must be configured to prevent anonymous users from having the same permissions as the Everyone group.</title>
+            <description>&lt;VulnDiscussion&gt;Access by anonymous users must be restricted. If this setting is enabled, anonymous users have the same rights and permissions as the built-in Everyone group. Anonymous users must not have these permissions or rights.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57904r849219_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network access: Let Everyone permissions apply to anonymous users to "Disabled".</fixtext>
+            <fix id="F-57904r849219_fix" />
+            <check system="C-57953r849218_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\
+
+Value Name: EveryoneIncludesAnonymous
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254469">
+        <title>SRG-OS-000138-GPOS-00069</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254469r958524_rule" weight="10.0" severity="high">
+            <version>WN22-SO-000250</version>
+            <title>Windows Server 2022 must restrict anonymous access to Named Pipes and Shares.</title>
+            <description>&lt;VulnDiscussion&gt;Allowing anonymous access to named pipes or shares provides the potential for unauthorized system access. This setting restricts access to those defined in "Network access: Named Pipes that can be accessed anonymously" and "Network access: Shares that can be accessed anonymously", both of which must be blank under other 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001090</ident>
+            <fixtext fixref="F-57905r849222_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network access: Restrict anonymous access to Named Pipes and Shares to "Enabled".</fixtext>
+            <fix id="F-57905r849222_fix" />
+            <check system="C-57954r849221_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\
+
+Value Name: RestrictNullSessAccess
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254470">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254470r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000260</version>
+            <title>Windows Server 2022 services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity instead of authenticating anonymously.</title>
+            <description>&lt;VulnDiscussion&gt;Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously versus using the computer identity.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57906r849225_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network security: Allow Local System to use computer identity for NTLM to "Enabled".</fixtext>
+            <fix id="F-57906r849225_fix" />
+            <check system="C-57955r849224_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\
+
+Value Name: UseMachineId
+
+Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254471">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254471r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000270</version>
+            <title>Windows Server 2022 must prevent NTLM from falling back to a Null session.</title>
+            <description>&lt;VulnDiscussion&gt;NTLM sessions that are allowed to fall back to Null (unauthenticated) sessions may gain unauthorized 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57907r849228_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network security: Allow LocalSystem NULL session fallback to "Disabled".</fixtext>
+            <fix id="F-57907r849228_fix" />
+            <check system="C-57956r849227_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\MSV1_0\
+
+Value Name: allownullsessionfallback
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254472">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254472r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000280</version>
+            <title>Windows Server 2022 must prevent PKU2U authentication using online identities.</title>
+            <description>&lt;VulnDiscussion&gt;PKU2U is a peer-to-peer authentication protocol. This setting prevents online identities from authenticating to domain-joined systems. Authentication will be centrally managed with Windows user accounts.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57908r849231_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network security: Allow PKU2U authentication requests to this computer to use online identities to "Disabled".</fixtext>
+            <fix id="F-57908r849231_fix" />
+            <check system="C-57957r849230_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SYSTEM\CurrentControlSet\Control\LSA\pku2u\
+
+Value Name: AllowOnlineID
+
+Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254473">
+        <title>SRG-OS-000120-GPOS-00061</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254473r971535_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000290</version>
+            <title>Windows Server 2022 Kerberos encryption types must be configured to prevent the use of DES and RC4 encryption suites.</title>
+            <description>&lt;VulnDiscussion&gt;Certain encryption types are no longer considered secure. The DES and RC4 encryption suites must not be used for Kerberos encryption.
+
+Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000803</ident>
+            <fixtext fixref="F-57909r849234_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network security: Configure encryption types allowed for Kerberos to "Enabled" with only the following selected:
+
+AES128_HMAC_SHA1
+AES256_HMAC_SHA1
+Future encryption types
+
+Note: Organizations with domain controllers running earlier versions of Windows where RC4 encryption is enabled, selecting "The other domain supports Kerberos AES Encryption" on domain trusts, may be required to allow client communication across the trust relationship.</fixtext>
+            <fix id="F-57909r849234_fix" />
+            <check system="C-57958r849233_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\
+
+Value Name: SupportedEncryptionTypes
+
+Value Type: REG_DWORD
+Value: 0x7ffffff8 (2147483640)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254474">
+        <title>SRG-OS-000073-GPOS-00041</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254474r1000173_rule" weight="10.0" severity="high">
+            <version>WN22-SO-000300</version>
+            <title>Windows Server 2022 must be configured to prevent the storage of the LAN Manager hash of passwords.</title>
+            <description>&lt;VulnDiscussion&gt;The LAN Manager hash uses a weak encryption algorithm and there are several tools available that use this hash to retrieve account passwords. This setting controls whether a LAN Manager hash of the password is stored in the SAM the next time the password is changed.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004062</ident>
+            <fixtext fixref="F-57910r849237_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network security: Do not store LAN Manager hash value on next password change to "Enabled".</fixtext>
+            <fix id="F-57910r849237_fix" />
+            <check system="C-57959r849236_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\
+
+Value Name: NoLMHash
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254475">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254475r991589_rule" weight="10.0" severity="high">
+            <version>WN22-SO-000310</version>
+            <title>Windows Server 2022 LAN Manager authentication level must be configured to send NTLMv2 response only and to refuse LM and NTLM.</title>
+            <description>&lt;VulnDiscussion&gt;The Kerberos v5 authentication protocol is the default for authentication of users who are logging on to domain accounts. NTLM, which is less secure, is retained in later Windows versions for compatibility with clients and servers that are running earlier versions of Windows or applications that still use it. It is also used to authenticate logons to standalone or nondomain-joined computers that are running later versions.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57911r849240_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network security: LAN Manager authentication level to "Send NTLMv2 response only. Refuse LM &amp; NTLM".</fixtext>
+            <fix id="F-57911r849240_fix" />
+            <check system="C-57960r849239_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\
+
+Value Name: LmCompatibilityLevel
+
+Value Type: REG_DWORD
+Value: 0x00000005 (5)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254476">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254476r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000320</version>
+            <title>Windows Server 2022 must be configured to at least negotiate signing for LDAP client signing.</title>
+            <description>&lt;VulnDiscussion&gt;This setting controls the signing requirements for LDAP clients. This must be set to "Negotiate signing" or "Require signing", depending on the environment and type of LDAP server in 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57912r849243_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network security: LDAP client signing requirements to "Negotiate signing" at a minimum.</fixtext>
+            <fix id="F-57912r849243_fix" />
+            <check system="C-57961r849242_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Services\LDAP\
+
+Value Name: LDAPClientIntegrity
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254477">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254477r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000330</version>
+            <title>Windows Server 2022 session security for NTLM SSP-based clients must be configured to require NTLMv2 session security and 128-bit encryption.</title>
+            <description>&lt;VulnDiscussion&gt;Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (RPC) sessions. All of the options must be enabled to ensure the maximum security 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57913r849246_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network security: Minimum session security for NTLM SSP based (including secure RPC) clients to "Require NTLMv2 session security" and "Require 128-bit encryption" (all options selected).</fixtext>
+            <fix id="F-57913r849246_fix" />
+            <check system="C-57962r849245_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\
+
+Value Name: NTLMMinClientSec
+
+Value Type: REG_DWORD
+Value: 0x20080000 (537395200)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254478">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254478r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000340</version>
+            <title>Windows Server 2022 session security for NTLM SSP-based servers must be configured to require NTLMv2 session security and 128-bit encryption.</title>
+            <description>&lt;VulnDiscussion&gt;Microsoft has implemented a variety of security support providers for use with Remote Procedure Call (RPC) sessions. All of the options must be enabled to ensure the maximum security 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57914r849249_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; Network security: Minimum session security for NTLM SSP based (including secure RPC) servers to "Require NTLMv2 session security" and "Require 128-bit encryption" (all options selected).</fixtext>
+            <fix id="F-57914r849249_fix" />
+            <check system="C-57963r849248_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\
+
+Value Name: NTLMMinServerSec
+
+Value Type: REG_DWORD
+Value: 0x20080000 (537395200)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254479">
+        <title>SRG-OS-000067-GPOS-00035</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254479r958450_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000350</version>
+            <title>Windows Server 2022 users must be required to enter a password to access private keys stored on the computer.</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 the private key is stolen, this will lead to the compromise of the authentication and nonrepudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user.
+
+Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000186</ident>
+            <fixtext fixref="F-57915r849252_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; System cryptography: Force strong key protection for user keys stored on the computer to "User must enter a password each time they use a key".</fixtext>
+            <fix id="F-57915r849252_fix" />
+            <check system="C-57964r849251_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive:  HKEY_LOCAL_MACHINE
+Registry Path:  \SOFTWARE\Policies\Microsoft\Cryptography\
+
+Value Name:  ForceKeyProtection
+
+Type:  REG_DWORD
+Value:  0x00000002 (2)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254480">
+        <title>SRG-OS-000478-GPOS-00223</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254480r959006_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000360</version>
+            <title>Windows Server 2022 must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing.</title>
+            <description>&lt;VulnDiscussion&gt;This setting ensures the system uses algorithms that are FIPS-compliant for encryption, hashing, and signing. FIPS-compliant algorithms meet specific standards established by the U.S. Government and must be the algorithms used for all OS encryption functions.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002450</ident>
+            <fixtext fixref="F-57916r849255_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing to "Enabled".</fixtext>
+            <fix id="F-57916r849255_fix" />
+            <check system="C-57965r849254_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SYSTEM\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\
+
+Value Name: Enabled
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)
+ 
+Clients with this setting enabled will not be able to communicate via digitally encrypted or signed protocols with servers that do not support these algorithms. Both the browser and web server must be configured to use TLS; otherwise the browser will not be able to connect to a secure site.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254481">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254481r991589_rule" weight="10.0" severity="low">
+            <version>WN22-SO-000370</version>
+            <title>Windows Server 2022 default permissions of global system objects must be strengthened.</title>
+            <description>&lt;VulnDiscussion&gt;Windows systems maintain a global list of shared system resources such as DOS device names, mutexes, and semaphores. Each type of object is created with a default Discretionary Access Control List (DACL) that specifies who can access the objects with what permissions. When this policy is enabled, the default DACL is stronger, allowing nonadministrative users to read shared objects but not to modify shared objects they did not create.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57917r849258_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; System objects: Strengthen default permissions of internal system objects (e.g., Symbolic Links) to "Enabled".</fixtext>
+            <fix id="F-57917r849258_fix" />
+            <check system="C-57966r849257_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SYSTEM\CurrentControlSet\Control\Session Manager\
+
+Value Name: ProtectionMode
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254482">
+        <title>SRG-OS-000373-GPOS-00156</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254482r1000174_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000380</version>
+            <title>Windows Server 2022 User Account Control (UAC) approval mode for the built-in Administrator must be enabled.</title>
+            <description>&lt;VulnDiscussion&gt;UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures the built-in Administrator account so that it runs in Admin Approval Mode.
+
+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004895</ident>
+            <fixtext fixref="F-57918r849261_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; User Account Control: Admin Approval Mode for the Built-in Administrator account to "Enabled".</fixtext>
+            <fix id="F-57918r849261_fix" />
+            <check system="C-57967r849260_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience).
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
+
+Value Name: FilterAdministratorToken
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254483">
+        <title>SRG-OS-000134-GPOS-00068</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254483r958518_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000390</version>
+            <title>Windows Server 2022 UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.</title>
+            <description>&lt;VulnDiscussion&gt;User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001084</ident>
+            <fixtext fixref="F-57919r849264_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop to "Disabled".</fixtext>
+            <fix id="F-57919r849264_fix" />
+            <check system="C-57968r849263_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience).
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
+
+Value Name: EnableUIADesktopToggle
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254484">
+        <title>SRG-OS-000134-GPOS-00068</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254484r958518_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000400</version>
+            <title>Windows Server 2022 User Account Control (UAC) must, at a minimum, prompt administrators for consent on the secure desktop.</title>
+            <description>&lt;VulnDiscussion&gt;UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures the elevation requirements for logged-on administrators to complete a task that requires raised 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001084</ident>
+            <fixtext fixref="F-57920r849267_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode to "Prompt for consent on the secure desktop".
+
+The more secure option for this setting, "Prompt for credentials on the secure desktop", would also be acceptable.</fixtext>
+            <fix id="F-57920r849267_fix" />
+            <check system="C-57969r849266_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>UAC requirements are NA for Server Core installations (this is default installation option for Windows Server 2022 versus Server with Desktop Experience).
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
+
+Value Name: ConsentPromptBehaviorAdmin
+
+Value Type: REG_DWORD
+Value: 0x00000002 (2) (Prompt for consent on the secure desktop)
+0x00000001 (1) (Prompt for credentials on the secure desktop)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254485">
+        <title>SRG-OS-000373-GPOS-00156</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254485r1000175_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000410</version>
+            <title>Windows Server 2022 User Account Control (UAC) must automatically deny standard user requests for elevation.</title>
+            <description>&lt;VulnDiscussion&gt;UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account.
+
+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004895</ident>
+            <fixtext fixref="F-57921r849270_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; User Account Control: Behavior of the elevation prompt for standard users to "Automatically deny elevation requests".</fixtext>
+            <fix id="F-57921r849270_fix" />
+            <check system="C-57970r849269_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience).
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
+
+Value Name: ConsentPromptBehaviorUser
+
+Value Type: REG_DWORD
+Value: 0x00000000 (0)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254486">
+        <title>SRG-OS-000134-GPOS-00068</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254486r958518_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000420</version>
+            <title>Windows Server 2022 User Account Control (UAC) must be configured to detect application installations and prompt for elevation.</title>
+            <description>&lt;VulnDiscussion&gt;UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting requires Windows to respond to application installation requests by prompting for credentials.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001084</ident>
+            <fixtext fixref="F-57922r849273_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; User Account Control: Detect application installations and prompt for elevation to "Enabled".</fixtext>
+            <fix id="F-57922r849273_fix" />
+            <check system="C-57971r849272_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience).
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
+
+Value Name: EnableInstallerDetection
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254487">
+        <title>SRG-OS-000134-GPOS-00068</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254487r958518_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000430</version>
+            <title>Windows Server 2022 User Account Control (UAC) must only elevate UIAccess applications that are installed in secure locations.</title>
+            <description>&lt;VulnDiscussion&gt;UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures Windows to only allow applications installed in a secure location on the file system, such as the Program Files or the Windows\System32 folders, to run with elevated 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001084</ident>
+            <fixtext fixref="F-57923r849276_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; User Account Control: Only elevate UIAccess applications that are installed in secure locations to "Enabled".</fixtext>
+            <fix id="F-57923r849276_fix" />
+            <check system="C-57972r849275_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience).
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
+
+Value Name: EnableSecureUIAPaths
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254488">
+        <title>SRG-OS-000373-GPOS-00156</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254488r1000176_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000440</version>
+            <title>Windows Server 2022 User Account Control (UAC) must run all administrators in Admin Approval Mode, enabling UAC.</title>
+            <description>&lt;VulnDiscussion&gt;UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting enables UAC.
+
+Satisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004895</ident>
+            <fixtext fixref="F-57924r849279_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; User Account Control: Run all administrators in Admin Approval Mode to "Enabled".</fixtext>
+            <fix id="F-57924r849279_fix" />
+            <check system="C-57973r849278_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience).
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
+
+Value Name: EnableLUA
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254489">
+        <title>SRG-OS-000134-GPOS-00068</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254489r958518_rule" weight="10.0" severity="medium">
+            <version>WN22-SO-000450</version>
+            <title>Windows Server 2022 User Account Control (UAC) must virtualize file and registry write failures to per-user locations.</title>
+            <description>&lt;VulnDiscussion&gt;UAC is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures non-UAC-compliant applications to run in virtualized file and registry entries in per-user locations, allowing them to run.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-001084</ident>
+            <fixtext fixref="F-57925r849282_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; Security Options &gt;&gt; User Account Control: Virtualize file and registry write failures to per-user locations to "Enabled".</fixtext>
+            <fix id="F-57925r849282_fix" />
+            <check system="C-57974r849281_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>UAC requirements are NA for Server Core installations (this is the default installation option for Windows Server 2022 versus Server with Desktop Experience).
+
+If the following registry value does not exist or is not configured as specified, this is a finding:
+
+Registry Hive: HKEY_LOCAL_MACHINE 
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\
+
+Value Name: EnableVirtualization
+
+Value Type: REG_DWORD
+Value: 0x00000001 (1)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254490">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254490r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-UC-000010</version>
+            <title>Windows Server 2022 must preserve zone information when saving attachments.</title>
+            <description>&lt;VulnDiscussion&gt;Attachments from outside sources may contain malicious code. Preserving zone of origin (internet, intranet, local, restricted) information on file attachments allows Windows to determine risk.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57926r849285_fix">The default behavior is for Windows to mark file attachments with their zone information.
+
+If this needs to be corrected, configure the policy value for User Configuration &gt;&gt; Administrative Templates &gt;&gt; Windows Components &gt;&gt; Attachment Manager &gt;&gt; Do not preserve zone information in file attachments to "Not Configured" or "Disabled".</fixtext>
+            <fix id="F-57926r849285_fix" />
+            <check system="C-57975r849284_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>The default behavior is for Windows to mark file attachments with their zone information.
+
+If the registry Value Name below does not exist, this is not a finding.
+
+If it exists and is configured with a value of "2", this is not a finding.
+
+If it exists and is configured with a value of "1", this is a finding.
+
+Registry Hive: HKEY_CURRENT_USER
+Registry Path: \SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Attachments\
+
+Value Name: SaveZoneInformation
+
+Value Type: REG_DWORD
+Value: 0x00000002 (2) (or if the Value Name does not exist)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254491">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254491r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000010</version>
+            <title>Windows Server 2022 Access Credential Manager as a trusted caller user right must not be assigned to any groups or accounts.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Access Credential Manager as a trusted caller" user right may be able to retrieve the credentials of other accounts from Credential Manager.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57927r849288_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Access Credential Manager as a trusted caller to be defined but containing no entries (blank).</fixtext>
+            <fix id="F-57927r849288_fix" />
+            <check system="C-57976r849287_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups are granted the "Access Credential Manager as a trusted caller" user right, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs are granted the "SeTrustedCredManAccessPrivilege" user right, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254492">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254492r958726_rule" weight="10.0" severity="high">
+            <version>WN22-UR-000020</version>
+            <title>Windows Server 2022 Act as part of the operating system user right must not be assigned to any groups or accounts.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Act as part of the operating system" user right can assume the identity of any user and gain access to resources that the user is authorized to access. Any accounts with this right can take complete control of 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;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57928r849291_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Act as part of the operating system to be defined but containing no entries (blank).</fixtext>
+            <fix id="F-57928r849291_fix" />
+            <check system="C-57977r849290_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups (to include administrators), are granted the "Act as part of the operating system" user right, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs are granted the "SeTcbPrivilege" user right, this is a finding.
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).
+
+Passwords for accounts with this user right must be protected as highly privileged accounts.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254493">
+        <title>SRG-OS-000080-GPOS-00048</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254493r958472_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000030</version>
+            <title>Windows Server 2022 Allow log on locally user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Allow log on locally" user right can log on interactively 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;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000213</ident>
+            <fixtext fixref="F-57929r849294_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Allow log on locally to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57929r849294_fix" />
+            <check system="C-57978r849293_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Allow log on locally" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeInteractiveLogonRight" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254494">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254494r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000040</version>
+            <title>Windows Server 2022 back up files and directories user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Back up files and directories" user right can circumvent file and directory permissions and could allow access to sensitive data.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57930r849297_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Back up files and directories to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57930r849297_fix" />
+            <check system="C-57979r849296_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Back up files and directories" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeBackupPrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254495">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254495r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000050</version>
+            <title>Windows Server 2022 create a pagefile user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Create a pagefile" user right can change the size of a pagefile, which could affect system performance.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57931r849300_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Create a pagefile to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57931r849300_fix" />
+            <check system="C-57980r849299_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Create a pagefile" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeCreatePagefilePrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254496">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254496r958726_rule" weight="10.0" severity="high">
+            <version>WN22-UR-000060</version>
+            <title>Windows Server 2022 create a token object user right must not be assigned to any groups or accounts.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Create a token object" user right allows a process to create an access token. This could be used to provide elevated rights and compromise 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;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57932r849303_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Create a token object to be defined but containing no entries (blank).</fixtext>
+            <fix id="F-57932r849303_fix" />
+            <check system="C-57981r849302_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups are granted the "Create a token object" user right, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs are granted the "SeCreateTokenPrivilege" user right, this is a finding.
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).
+
+Passwords for application accounts with this user right must be protected as highly privileged accounts.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254497">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254497r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000070</version>
+            <title>Windows Server 2022 create global objects user right must only be assigned to Administrators, Service, Local Service, and Network Service.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Create global objects" user right can create objects that are available to all sessions, which could affect processes in other users' sessions.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57933r849306_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Create global objects to include only the following accounts or groups:
+
+- Administrators
+- Service
+- Local Service
+- Network Service</fixtext>
+            <fix id="F-57933r849306_fix" />
+            <check system="C-57982r849305_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Create global objects" user right, this is a finding:
+
+- Administrators
+- Service
+- Local Service
+- Network Service
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeCreateGlobalPrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)
+S-1-5-6 (Service)
+S-1-5-19 (Local Service)
+S-1-5-20 (Network Service)
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254498">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254498r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000080</version>
+            <title>Windows Server 2022 create permanent shared objects user right must not be assigned to any groups or accounts.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Create permanent shared objects" user right could expose sensitive data by creating shared objects.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57934r849309_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Create permanent shared objects to be defined but containing no entries (blank).</fixtext>
+            <fix id="F-57934r849309_fix" />
+            <check system="C-57983r849308_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups are granted the "Create permanent shared objects" user right, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs are granted the "SeCreatePermanentPrivilege" user right, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254499">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254499r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000090</version>
+            <title>Windows Server 2022 create symbolic links user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Create symbolic links" user right can create pointers to other objects, which could expose the system to 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57935r849312_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Create symbolic links to include only the following accounts or groups:
+
+- Administrators
+
+Systems that have the Hyper-V role will also have "Virtual Machines" given this user right. If this needs to be added manually, enter it as "NT Virtual Machine\Virtual Machines".</fixtext>
+            <fix id="F-57935r849312_fix" />
+            <check system="C-57984r849311_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Create symbolic links" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeCreateSymbolicLinkPrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)
+
+Systems that have the Hyper-V role will also have "Virtual Machines" given this user right (this may be displayed as "NT Virtual Machine\Virtual Machines", SID S-1-5-83-0). This is not a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254500">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254500r958726_rule" weight="10.0" severity="high">
+            <version>WN22-UR-000100</version>
+            <title>Windows Server 2022 debug programs user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Debug programs" user right can attach a debugger to any process or to the kernel, providing complete access to sensitive and critical operating system components. This right is given to Administrators in the default configuration.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57936r849315_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Debug programs to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57936r849315_fix" />
+            <check system="C-57985r849314_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Debug programs" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeDebugPrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).
+
+Passwords for application accounts with this user right must be protected as highly privileged accounts.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254501">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254501r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000110</version>
+            <title>Windows Server 2022 force shutdown from a remote system user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Force shutdown from a remote system" user right can remotely shut down a system, which could result in a denial of 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57937r849318_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Force shutdown from a remote system to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57937r849318_fix" />
+            <check system="C-57986r849317_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Force shutdown from a remote system" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeRemoteShutdownPrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254502">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254502r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000120</version>
+            <title>Windows Server 2022 generate security audits user right must only be assigned to Local Service and Network Service.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Generate security audits" user right specifies users and processes that can generate Security Log audit records, which must only be the system service accounts defined.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57938r849321_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Generate security audits to include only the following accounts or groups:
+
+- Local Service
+- Network Service</fixtext>
+            <fix id="F-57938r849321_fix" />
+            <check system="C-57987r849320_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Generate security audits" user right, this is a finding:
+
+- Local Service
+- Network Service
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeAuditPrivilege" user right, this is a finding:
+
+S-1-5-19 (Local Service)
+S-1-5-20 (Network Service)
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254503">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254503r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000130</version>
+            <title>Windows Server 2022 impersonate a client after authentication user right must only be assigned to Administrators, Service, Local Service, and Network Service.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Impersonate a client after authentication" user right allows a program to impersonate another user or account to run on their behalf. An attacker could use this to elevate 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57939r849324_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Impersonate a client after authentication to include only the following accounts or groups:
+
+- Administrators
+- Service
+- Local Service
+- Network Service</fixtext>
+            <fix id="F-57939r849324_fix" />
+            <check system="C-57988r849323_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Impersonate a client after authentication" user right, this is a finding:
+
+- Administrators
+- Service
+- Local Service
+- Network Service
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeImpersonatePrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)
+S-1-5-6 (Service)
+S-1-5-19 (Local Service)
+S-1-5-20 (Network Service)
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254504">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254504r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000140</version>
+            <title>Windows Server 2022 increase scheduling priority: user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Increase scheduling priority" user right can change a scheduling priority, causing performance issues or a denial of 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57940r849327_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Increase scheduling priority to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57940r849327_fix" />
+            <check system="C-57989r849326_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Increase scheduling priority" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeIncreaseBasePriorityPrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254505">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254505r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000150</version>
+            <title>Windows Server 2022 load and unload device drivers user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Load and unload device drivers" user right allows a user to load device drivers dynamically on a system. This could be used by an attacker to install malicious code.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57941r849330_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Load and unload device drivers to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57941r849330_fix" />
+            <check system="C-57990r849329_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Load and unload device drivers" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeLoadDriverPrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254506">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254506r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000160</version>
+            <title>Windows Server 2022 lock pages in memory user right must not be assigned to any groups or accounts.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+The "Lock pages in memory" user right allows physical memory to be assigned to processes, which could cause performance issues or a denial of service.
+
+Satisfies: SRG-OS-000324-GPOS-00125, SRG-OS-000433-GPOS-00193&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <ident system="http://cyber.mil/cci">CCI-002824</ident>
+            <fixtext fixref="F-57942r849333_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Lock pages in memory to be defined but containing no entries (blank).</fixtext>
+            <fix id="F-57942r849333_fix" />
+            <check system="C-57991r849332_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups are granted the "Lock pages in memory" user right, this is a finding.
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs are granted the "SeLockMemoryPrivilege" user right, this is a finding.
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254507">
+        <title>SRG-OS-000057-GPOS-00027</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254507r958434_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000170</version>
+            <title>Windows Server 2022 manage auditing and security log user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Manage auditing and security log" user right can manage the security log and change auditing configurations. This could be used to clear evidence of tampering.
+
+Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029, SRG-OS-000063-GPOS-00032, SRG-OS-000337-GPOS-00129&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000162</ident>
+            <ident system="http://cyber.mil/cci">CCI-000163</ident>
+            <ident system="http://cyber.mil/cci">CCI-000164</ident>
+            <ident system="http://cyber.mil/cci">CCI-000171</ident>
+            <ident system="http://cyber.mil/cci">CCI-001914</ident>
+            <fixtext fixref="F-57943r849336_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Manage auditing and security log to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57943r849336_fix" />
+            <check system="C-57992r849335_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Manage auditing and security log" user right, this is a finding.
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeSecurityPrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)
+
+If the organization has an Auditors group, the assignment of this group to the user right would not be a finding.
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254508">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254508r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000180</version>
+            <title>Windows Server 2022 modify firmware environment values user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Modify firmware environment values" user right can change hardware configuration environment variables. This could result in hardware failures or a denial of 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57944r849339_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Modify firmware environment values to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57944r849339_fix" />
+            <check system="C-57993r849338_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Modify firmware environment values" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeSystemEnvironmentPrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254509">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254509r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000190</version>
+            <title>Windows Server 2022 perform volume maintenance tasks user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Perform volume maintenance tasks" user right can manage volume and disk configurations. This could be used to delete volumes, resulting in data loss or a denial of 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57945r849342_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Perform volume maintenance tasks to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57945r849342_fix" />
+            <check system="C-57994r849341_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Perform volume maintenance tasks" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeManageVolumePrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254510">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254510r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000200</version>
+            <title>Windows Server 2022 profile single process user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Profile single process" user right can monitor nonsystem processes performance. An attacker could use this to identify processes to 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57946r849345_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Profile single process to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57946r849345_fix" />
+            <check system="C-57995r849344_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Profile single process" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeProfileSingleProcessPrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254511">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254511r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000210</version>
+            <title>Windows Server 2022 restore files and directories user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Restore files and directories" user right can circumvent file and directory permissions and could allow access to sensitive data. It could also be used to overwrite more current data.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57947r849348_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Restore files and directories to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57947r849348_fix" />
+            <check system="C-57996r849347_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Restore files and directories" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeRestorePrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254512">
+        <title>SRG-OS-000324-GPOS-00125</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254512r958726_rule" weight="10.0" severity="medium">
+            <version>WN22-UR-000220</version>
+            <title>Windows Server 2022 take ownership of files or other objects user right must only be assigned to the Administrators group.</title>
+            <description>&lt;VulnDiscussion&gt;Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.
+
+Accounts with the "Take ownership of files or other objects" user right can take ownership of objects and make changes.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-002235</ident>
+            <fixtext fixref="F-57948r849351_fix">Configure the policy value for Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment &gt;&gt; Take ownership of files or other objects to include only the following accounts or groups:
+
+- Administrators</fixtext>
+            <fix id="F-57948r849351_fix" />
+            <check system="C-57997r849350_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify the effective setting in Local Group Policy Editor.
+
+Run "gpedit.msc".
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Windows Settings &gt;&gt; Security Settings &gt;&gt; Local Policies &gt;&gt; User Rights Assignment.
+
+If any accounts or groups other than the following are granted the "Take ownership of files or other objects" user right, this is a finding:
+
+- Administrators
+
+For server core installations, run the following command:
+
+Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt
+
+Review the text file.
+
+If any SIDs other than the following are granted the "SeTakeOwnershipPrivilege" user right, this is a finding:
+
+S-1-5-32-544 (Administrators)
+
+If an application requires this user right, this would not be a finding.
+
+Vendor documentation must support the requirement for having the user right.
+
+The requirement must be documented with the Information System Security Officer (ISSO).
+
+The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060).</check-content>
+            </check>
+        </Rule>
+    </Group>
+</Benchmark>
\ No newline at end of file
diff --git a/test/sample_data/xccdf/stigs/Windows_Server_2022_V2R1_mini-sample-xccdf.xml b/test/sample_data/xccdf/stigs/Windows_Server_2022_V2R1_mini-sample-xccdf.xml
new file mode 100644
index 000000000..b5e562462
--- /dev/null
+++ b/test/sample_data/xccdf/stigs/Windows_Server_2022_V2R1_mini-sample-xccdf.xml
@@ -0,0 +1,186 @@
+<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type='text/xsl' href='STIG_unclass.xsl'?>
+<Benchmark xmlns:dc="http://purl.org/dc/elements/1.1/"
+    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+    xmlns:cpe="http://cpe.mitre.org/language/2.0"
+    xmlns:xhtml="http://www.w3.org/1999/xhtml"
+    xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/schema/xccdf-1.1.4.xsd http://cpe.mitre.org/dictionary/2.0 http://cpe.mitre.org/files/cpe-dictionary_2.1.xsd" id="MS_Windows_Server_2022_STIG" xml:lang="en"
+    xmlns="http://checklists.nist.gov/xccdf/1.1">
+    <status date="2024-06-14">accepted</status>
+    <title>Microsoft Windows Server 2022 Security Technical Implementation Guide</title>
+    <description>This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.</description>
+    <notice id="terms-of-use" xml:lang="en"></notice>
+    <front-matter xml:lang="en"></front-matter>
+    <rear-matter xml:lang="en"></rear-matter>
+    <reference href="https://cyber.mil">
+        <dc:publisher>DISA</dc:publisher>
+        <dc:source>STIG.DOD.MIL</dc:source>
+    </reference>
+    <plain-text id="release-info">Release: 1 Benchmark Date: 24 Jul 2024</plain-text>
+    <plain-text id="generator">3.5</plain-text>
+    <plain-text id="conventionsVersion">1.10.0</plain-text>
+    <version>2</version>
+    <Group id="V-254238">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254238r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000010</version>
+            <title>Windows Server 2022 users with Administrative privileges must have separate accounts for administrative duties and normal operational tasks.</title>
+            <description>&lt;VulnDiscussion&gt;Using a privileged account to perform routine functions makes the computer vulnerable to malicious software inadvertently introduced during a session that has been granted full 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57674r848529_fix">Ensure each user with administrative privileges has a separate account for user duties and one for privileged duties.</fixtext>
+            <fix id="F-57674r848529_fix" />
+            <check system="C-57723r848528_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Verify each user with administrative privileges has been assigned a unique administrative account separate from their standard user account. 
+
+If users with administrative privileges do not have separate accounts for administrative functions and standard user functions, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254239">
+        <title>SRG-OS-000076-GPOS-00044</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254239r1000150_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000020</version>
+            <title>Windows Server 2022 passwords for the built-in Administrator account must be changed at least every 60 days.</title>
+            <description>&lt;VulnDiscussion&gt;The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. The built-in Administrator account is not generally used and its password may not be changed as frequently as necessary. Changing the password for the built-in Administrator account on a regular basis will limit its exposure.
+
+Windows LAPS must be used to change the built-in Administrator account 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 Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004066</ident>
+            <fixtext fixref="F-57675r951094_fix">Change the enabled local Administrator account password at least every 60 days. Windows LAPS must be used to change the built-in Administrator account password. Domain-joined systems can configure this to occur more frequently. LAPS will change the password every 30 days by default. 
+
+More information is available at:
+https://techcommunity.microsoft.com/t5/windows-it-pro-blog/by-popular-demand-windows-laps-available-now/ba-p/3788747
+https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-overview#windows-laps-supported-platforms-and-azure-ad-laps-preview-status</fixtext>
+            <fix id="F-57675r951094_fix" />
+            <check system="C-57724r951093_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If there are no enabled local Administrator accounts, this is Not Applicable.
+
+Review the password last set date for the enabled local Administrator account.
+
+On the stand alone or domain-joined workstation:
+
+Open "PowerShell".
+
+Enter "Get-LocalUser -Name * | Select-Object *".
+
+If the "PasswordLastSet" date is greater than "60" days old for the local Administrator account for administering the computer/domain, this is a finding.
+
+Verify LAPS is configured and operational. 
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; LAPS &gt;&gt; Password Settings &gt;&gt; Set to enabled. Password Complexity, large letters + small letters + numbers + special, Password Length 14, Password Age 60. If not configured as shown, this is a finding. 
+
+Navigate to Local Computer Policy &gt;&gt; Computer Configuration &gt;&gt; Administrative Templates &gt;&gt; System &gt;&gt; LAPS &gt;&gt; Password Settings &gt;&gt; Name of administrator Account to manage &gt;&gt; Set to enabled &gt;&gt; Administrator account name is populated. If it is not, this is a finding. 
+
+Verify LAPS Operational logs &gt;&gt; Event Viewer &gt;&gt; Applications and Services Logs &gt;&gt; Microsoft &gt;&gt; Windows &gt;&gt; LAPS &gt;&gt; Operational. Verify LAPS policy process is completing. If it is not, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254240">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254240r991589_rule" weight="10.0" severity="high">
+            <version>WN22-00-000030</version>
+            <title>Windows Server 2022 administrative accounts must not be used with applications that access the internet, such as web browsers, or with potential internet sources, such as email.</title>
+            <description>&lt;VulnDiscussion&gt;Using applications that access the internet or have potential internet sources using administrative privileges exposes a system to compromise. If a flaw in an application is exploited while running as a privileged user, the entire system could be compromised. Web browsers and email are common attack vectors for introducing malicious code and must not be run with an administrative account.
+
+Since administrative accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy require administrative accounts to not access the internet or use applications such as email.
+
+The policy must define specific exceptions for local service administration. These exceptions may include HTTP(S)-based tools that are used for the administration of the local system, services, or attached devices.
+
+Whitelisting can be used to enforce the policy to ensure compliance.
+
+Satisfies: SRG-OS-000480-GPOS-00227, SRG-OS-000205-GPOS-00083&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <ident system="http://cyber.mil/cci">CCI-001312</ident>
+            <fixtext fixref="F-57676r848535_fix">Establish a policy, at minimum, to prohibit administrative accounts from using applications that access the internet, such as web browsers, or with potential internet sources, such as email. Ensure the policy is enforced.
+
+The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement.</fixtext>
+            <fix id="F-57676r848535_fix" />
+            <check system="C-57725r848534_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Determine whether organization policy, at a minimum, prohibits administrative accounts from using applications that access the internet, such as web browsers, or with potential internet sources, such as email, except as necessary for local service administration.
+
+If it does not, this is a finding.
+
+The organization may use technical means such as whitelisting to prevent the use of browsers and mail applications to enforce this requirement.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254241">
+        <title>SRG-OS-000480-GPOS-00227</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254241r991589_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000040</version>
+            <title>Windows Server 2022 members of the Backup Operators group must have separate accounts for backup duties and normal operational tasks.</title>
+            <description>&lt;VulnDiscussion&gt;Backup Operators are able to read and write to any file in the system, regardless of the rights assigned to it. Backup and restore rights permit users to circumvent the file access restrictions present on NTFS disk drives for backup and restore purposes. Members of the Backup Operators group must have separate logon accounts for performing backup duties.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-000366</ident>
+            <fixtext fixref="F-57677r848538_fix">Ensure each member of the Backup Operators group has separate accounts for backup functions and standard user functions.</fixtext>
+            <fix id="F-57677r848538_fix" />
+            <check system="C-57726r848537_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>If no accounts are members of the Backup Operators group, this is NA.
+
+Verify users with accounts in the Backup Operators group have a separate user account for backup functions and for performing normal user tasks.
+
+If users with accounts in the Backup Operators group do not have separate accounts for backup functions and standard user functions, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+    <Group id="V-254242">
+        <title>SRG-OS-000078-GPOS-00046</title>
+        <description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description>
+        <Rule id="SV-254242r1000151_rule" weight="10.0" severity="medium">
+            <version>WN22-00-000050</version>
+            <title>Windows Server 2022 manually managed application account passwords must be at least 14 characters in length.</title>
+            <description>&lt;VulnDiscussion&gt;Application/service account passwords must be of sufficient length to prevent being easily cracked. Application/service accounts that are manually managed must have passwords at least 14 characters in length.&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description>
+            <reference>
+                <dc:title>DPMS Target Microsoft Windows Server 2022</dc:title>
+                <dc:publisher>DISA</dc:publisher>
+                <dc:type>DPMS Target</dc:type>
+                <dc:subject>Microsoft Windows Server 2022</dc:subject>
+                <dc:identifier>5485</dc:identifier>
+            </reference>
+            <ident system="http://cyber.mil/cci">CCI-004066</ident>
+            <fixtext fixref="F-57678r951097_fix">Establish a policy that requires application/service account passwords that are manually managed to be at least 14 characters in length. Ensure the policy is enforced.</fixtext>
+            <fix id="F-57678r951097_fix" />
+            <check system="C-57727r951096_chk">
+                <check-content-ref href="Microsoft_Windows_Server_2022_STIG.xml" name="M" />
+                <check-content>Determine if manually managed application/service accounts exist. If none exist, this is NA.
+
+Verify the organization has a policy to ensure passwords for manually managed application/service accounts are at least 14 characters in length.
+
+If such a policy does not exist or has not been implemented, this is a finding.</check-content>
+            </check>
+        </Rule>
+    </Group>
+</Benchmark>
\ No newline at end of file