From Windows 2008 Member Server Security Technical Implementation Guide
Part of WINGE-000200
Associated with: CCI-000366
Several user rights on domain systems require that local administrator accounts be assigned to them. This is separate from the built-in Administrators group, which also contains domain administrative accounts/groups. Defining a consistent group name allows compliance to be more easily determined.
This requirement is NA for non domain-joined systems. Review local groups on the system. Documentation and scripts supporting the creation of this group to restrict local administrative accounts were changed at one point. The original name, "DeniedNetworkAccess", was changed to "DenyNetworkAccess". Automated benchmarks will look for either of these groups. If the group "DenyNetworkAccess" or "DeniedNetworkAccess" does not exist, this is a finding. Compare the membership of the defined group with the local Administrators group. Verify the group includes all local administrator accounts as members. This includes the built-in Administrator account. It does not include domain administrative accounts or groups. If the group "DenyNetworkAccess" or "DeniedNetworkAccess" does not include all local administrator accounts, this is a finding.
This requirement is NA for non domain-joined systems. Create a local group with the name "DenyNetworkAccess" or "DeniedNetworkAccess" on the system. Include all local administrator accounts as members of the group, including the built-in Administrator account. Do not include domain administrative accounts or groups.
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