microsoft / microsoft/PowerStig

Windows Server 2025 member server rule V-278001.c includes domain-controller-only Server Operators principal

Open
#1,562 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
619
Forks
124
PR merge metrics
No merged PRs in 30d

Description

PowerSTIG 4.30.0 incorrectly includes the Server Operators principal in V-278001.c for the Windows Server 2025 Member Server STIG 1.1.

The rule manages permissions on:

HKLM:\SYSTEM

Its processed ACL contains:

<Entry>
    <Principal>Server Operators</Principal>
    <Inheritance />
    <Rights>ReadKey</Rights>
</Entry>

However, the rule's own STIG text states:

Server Operators - Read - This key and subkeys (Domain controllers only)

The Server Operators group does not exist on a member server. AccessControlDsc therefore fails while attempting to resolve it.

Exception calling "Translate" with "1" argument(s):
"Some or all identity references could not be translated."

A constructor was not found. Cannot find an appropriate constructor
for type System.Security.Principal.NTAccount.

The PowerShell DSC resource
[RegistryAccessEntry][V-278001.c]::[WindowsServer]Baseline
threw one or more non-terminating errors while running Test-TargetResource.

Workaround:

Exception = @{
    'V-278001.c' = @{
        AccessControlEntry = @{
            Entry = @(
                @{
                    Type = ''
                    Principal = 'Authenticated Users'
                    ForcePrincipal = 'False'
                    Inheritance = 'This Key and Subkeys'
                    Rights = 'ReadKey'
                }
                @{
                    Type = ''
                    Principal = 'Administrators'
                    ForcePrincipal = 'False'
                    Inheritance = 'This Key and Subkeys'
                    Rights = 'FullControl'
                }
                @{
                    Type = ''
                    Principal = 'SYSTEM'
                    ForcePrincipal = 'False'
                    Inheritance = 'This Key and Subkeys'
                    Rights = 'FullControl'
                }
                @{
                    Type = ''
                    Principal = 'CREATOR OWNER'
                    ForcePrincipal = 'False'
                    Inheritance = 'This Key and Subkeys'
                    Rights = 'FullControl'
                }
                @{
                    Type = ''
                    Principal = 'ALL APPLICATION PACKAGES'
                    ForcePrincipal = 'False'
                    Inheritance = 'This Key and Subkeys'
                    Rights = 'ReadKey'
                }
                @{
                    Type = ''
                    Principal = 'S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681'
                    ForcePrincipal = 'False'
                    Inheritance = 'This Key and Subkeys'
                    Rights = 'ReadKey'
                }
            )
        }
    }
}

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the PowerStig definition or baseline entry for V-278001.c and compare its Windows Server 2025 Member Server permissions with the STIG text quoted in the issue. Verify the member-server configuration no longer attempts to resolve Server Operators, while the reported AccessControlDsc failure is no longer reproduced.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
operating-systems, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.