Skip to main content
CUI

Vulnerability V-224994

Back

V-224994

CAT II

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.

Ships Affected
1
Total Findings
8
Open
1
Closed
0

Check Text

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.

Fix Text

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.

STIG Reference

STIG
Microsoft Windows Server 2016 Security Technical Implementation Guide
Version
2
Release
10
Rule ID
SV-224994r958484_rule

All Occurrences

This vulnerability appears on 1 ship(s)

Ship Hull # Source File Status Assigned To Scan Date Actions
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-AP-002/Checklist/MONT-AP-002_WinServer2016_V2R10_20251023-144214.ckl
Unassigned 2026-01-14T12:57:42.721079 View in Context
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-BE-002/Checklist/MONT-BE-002_WinServer2016_V2R10_20251023-143943.ckl
Unassigned 2026-01-14T12:57:41.363810 View in Context
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-DB-002/Checklist/MONT-DB-002_WinServer2016_V2R10_20251023-144132.ckl
Unassigned 2026-01-14T12:57:39.082634 View in Context
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-DC-003/Checklist/MONT-DC-003_WinServer2016_V2R10_20251023-172220.ckl
Unassigned 2026-01-14T12:57:37.248886 View in Context
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-DP-001/Checklist/MONT-DP-001_WinServer2016_V2R10_20251023-144106.ckl
Unassigned 2026-01-14T12:57:35.637816 View in Context
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-MB-002/Checklist/MONT-MB-002_WinServer2016_V2R10_20251023-152736.ckl
Unassigned 2026-01-14T12:57:33.842838 View in Context
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-VSF-003/Checklist/MONT-VSF-003_WinServer2016_V2R10_20251023-143935.ckl
Unassigned 2026-01-14T12:57:31.534241 View in Context
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-VSF-004/Checklist/MONT-VSF-004_WinServer2016_V2R10_20251023-143909.ckl
Unassigned 2026-01-14T12:57:30.046447 View in Context
CUI