| V-243454 | | A Windows PAW used to manage domain controllers and directory services must not be used to manage any other type of high-value IT resource. | Domain controllers (DC) are usually the most sensitive, high-value IT resources in a domain. Dedicating a PAW to be used solely for managing domain co... |
| V-243458 | | The Windows PAW must use a trusted channel for all connections between a PAW and IT resources managed from the PAW. | Note: The Common Criteria Security Functional Requirement (SFR) FTP_ITC.1.1(1) defines "trusted channel" as "a channel that uses IPsec, SSH, TLS, or T... |
| V-243443 | | Site IT resources designated as high value by the Authorizing Official (AO) must be remotely managed only via a Windows privileged access workstation (PAW). | The AO must designate which IT resources are high value. The list must include the following IT resources:
- Directory service (including Active Dire... |
| V-243444 | | Administrative accounts of all high-value IT resources must be assigned to a specific administrative tier in Active Directory to separate highly privileged administrative accounts from less privileged administrative accounts. | Note: The Microsoft Tier 0-2 AD administrative tier model (https://docs.microsoft.com/en-us/windows-server/identity/securing-privileged-access/securin... |
| V-243445 | | A Windows PAW must only be used to manage high-value IT resources assigned to the same tier. | Note: Allowed exception - For sites that are constrained in the number of available workstations, an acceptable approach is to install lower-tier admi... |
| V-243446 | | All high-value IT resources must be assigned to a specific administrative tier to separate highly sensitive resources from less sensitive resources. | Note: The Microsoft Tier 0-2 AD administrative tier model (https://docs.microsoft.com/en-us/windows-server/identity/securing-privileged-access/securin... |
| V-243447 | | The Windows PAW must be configured with a vendor-supported version of Windows 11 and applicable security patches that are DOD approved. | Older versions of operating systems usually contain vulnerabilities that have been fixed in later released versions. In addition, most operating syste... |
| V-243448 | | A Windows update service must be available to provide software updates for the PAW platform. | Older versions of operating systems usually contain vulnerabilities that have been fixed in later versions. In addition, most operating system patches... |
| V-243449 | | The Windows PAW must be configured so that all non-administrative-related applications and functions are blocked or removed from the PAW platform, including but not limited to email, Internet browsing, and line-of-business applications. | Note: The intent of this requirement is that a PAW must not be used for any function not related to the management of high-value IT resources.
Note: ... |
| V-243450 | | Device Guard Code Integrity Policy must be used on the Windows PAW to restrict applications that can run on the system (Device Guard Code Integrity Policy). | A main security architectural construct of a PAW is to restrict non-administrative applications and functions from the PAW workstation. Many standard ... |
| V-243451 | | Device Guard Code Integrity Policy must be used on the Windows PAW to restrict applications that can run on the system (Device Guard User Mode Code Integrity). | A main security architectural construct of a PAW is to restrict non-administrative applications and functions from the PAW workstation. Many standard ... |
| V-243452 | | Windows PAWs must be restricted to only allow groups used to manage high-value IT resources and members of the local Administrators group to log on locally. | A main security architectural construct of a PAW is to limit users of the PAW to only administrators of high-value IT resources. This will mitigate so... |
| V-243453 | | The domain must be configured to restrict privileged administrator accounts from logging on to lower-tier hosts. | If the domain is not configured to restrict privileged administrator accounts from logging on to lower-tier hosts, it would be impossible to isolate a... |
| V-243455 | | PAWs used to manage Active Directory must only allow groups specifically designated to manage Active Directory, such as Enterprise and Domain Admins and members of the local Administrators group, to log on locally. | PAW platforms are used for highly privileged activities. The accounts that have administrative privileges on domain-level PAW platforms must not be us... |
| V-243456 | | In a Windows PAW, administrator accounts used for maintaining the PAW must be separate from administrative accounts used to manage high-value IT resources. | Note: PAW accounts used to manage high-value IT resources have privileged rights on managed systems but no administrative or maintenance rights on the... |
| V-243457 | | The Windows PAW must be configured to enforce two-factor authentication and use Active Directory for authentication management. | Due to the highly privileged functions of a PAW, a high level of trust must be implemented for access to the PAW, including nonrepudiation of the user... |
| V-243459 | | If several Windows PAWs are set up in virtual machines (VMs) on a host server, the host server must only contain PAW VMs. If the PAW is hosted, the hosting system must be separated either physically or logically from other servers. The server is restricted to only PAW hosting functions. | A main security architectural construct of a PAW is to remove nonadministrative functions from the PAW. Many standard user functions, including email ... |
| V-243460 | | The Windows PAW must be configured so that all inbound ports and services to a PAW are blocked except as needed for monitoring, scanning, and management tools or when the inbound communication is a response to an outbound connection request. | A main security architectural construct of a PAW is that the workstation is isolated from most Internet threats, including phishing, impersonation, an... |
| V-243461 | | The Windows PAW must be configured so that all outbound connections to the Internet from a PAW are blocked. | Note: Internal domain connections from a PAW to communicate with IT resources being managed via the PAW with domain controllers or with a digital cred... |
| V-243462 | | The local Administrators group on the Windows PAW must only include groups with accounts specifically designated to administer the PAW. | A main security architectural construct of a PAW is to restrict access to the PAW from only specific privileged accounts designated for managing the h... |
| V-243463 | | Local privileged groups (excluding Administrators) on the Windows PAW must be restricted to include no members. | A main security architectural construct of a PAW is to restrict access to the PAW from only specific privileged accounts designated for managing the h... |
| V-243464 | | Restricted remote administration must be enabled for high-value systems. | Restricted remote administration features, RestrictedAdmin mode, and Remote Credential Guard for Remote Desktop Protocol (RDP), are an additional safe... |
| V-243465 | | If several PAWs are set up in virtual machines (VMs) on a host server, domain administrative accounts used to manage high-value IT resources must not have access to the VM host operating system (OS) (only domain administrative accounts designated to manage PAWs should be able to access the VM host OS). | The VM host OS should be protected from high-value IT resource administrators accidently or deliberately modifying the security settings of the host O... |
| V-243442 | | Administrators of high-value IT resources must complete required training. | Required training helps to mitigate the risk of administrators not following required procedures. High-value IT resources are the most important and c... |
