From Windows PAW Security Technical Implementation Guide
Part of SRG-OS-000480-GPOS-00227
Associated with: CCI-000366
A main security architectural construct of a PAW is to restrict access to the PAW from only specific privileged accounts designated for managing the high-value IT resources the PAW has been designated to manage. If unauthorized standard user accounts or unauthorized high-value administrative accounts are able to access a specific PAW, high-value IT resources and critical DoD information could be compromised.
Verify the PAW is configured to restrict access to privileged accounts specifically designated to administer the PAW: - On the Windows PAW, verify the membership of the local Administrators group. - Verify the only members in the local Administrators group are the group specifically designated for managing the PAW and local administrator(s). If the local Administrators group includes any members not members of the specifically designated group for managing the PAW and local administrator(s), this is a finding.
Restrict membership of the local Administrators group to only include members of the group specifically designated to manage the PAW and local administrator(s). See the Microsoft PAW paper (https://docs.microsoft.com/en-us/windows-server/identity/securing-privileged-access/privileged-access-workstations) for more information (go to PAW Installation instructions).
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer