PowerStig 4.19.0 & above - File not found - Rule.Skipped\SkippedRule.psm1 because it does not exist. about powerstig HOT 7 CLOSED

Hello @RKSelvi

Thanks for creating the issue. Please provide your DSC configuration so we better troubleshoot the issue.

The following configuration with skip rules works on Server 2022 with PowerShell 5.1

    
 configuration Windows
{
    Import-DscResource -ModuleName PowerSTIG -ModuleVersion 4.21.0
    Import-DscResource -ModuleName SecurityPolicyDsc -ModuleVersion 2.10.0.0

    Node localhost
    {

         WindowsServer BaseLine
        {
            OsVersion   = '2022'
            OsRole      = 'MS'
            DomainName  = 'sample.test'
            ForestName  = 'sample.test'
            SkipRule = @('V-254286', 'V-254285', 'V-254287')
        }

         AccountPolicy BaseLine2
        {
            Name                                = "2022fix"
            Account_lockout_threshold           = 3
            Account_lockout_duration            = 15
            Reset_account_lockout_counter_after = 15
        }
     }
}

windows

Thank you,

Eric

from powerstig.

Hi @erjenkin
Thank you for your response. Below is the configuration I am using.

$NtpClientType = NT5DS
$NtpServers = time.windows.com,0x8

`Configuration win2022STIG
{
param(
[parameter(Mandatory)]
[String]
$NtpClientType,

    [parameter(Mandatory)]
    [String]
    $NtpServers
)

Import-DscResource -ModuleName 'PowerSTIG' -ModuleVersion 4.21.0
Import-DscResource -ModuleName 'PSDscResources' -ModuleVersion 2.12.0.0

Node localhost
{
    WindowsServer STIGs
    {
        OsVersion    = '2022'
        OSRole       = 'MS'
        Exception    = @{
            'V-254435' = 'guests'
            'V-254429' = '1'
            'V-254438' = 'guests'
            'V-254439' = 'guests'
        }
        SkipRule     = @(
            'V-254424',
            'V-254421',
            'V-254254'
        )
    }

    WindowsDefender STIG_WindowsDefender
    {
        StigVersion = '2.3'
    }
}

}
`
compile is failing,

from powerstig.

What version of PowerShell are you using? We only support PowerShell 5.1 currently.

from powerstig.

I am compiling in the GitHub actions workflow with provider host agent which I believe it is Windows 2022. The PS version would be whatever the agent has it. This works for DSC for 2019 but only issue with 2022

dscnodeconfiguration:
name:    Compile DSC Node Config
runs-on: windows-latest

steps:
- uses: actions/[email protected]

- name:  Compile DSC Config
  shell: powershell
  run:   |
    Write-Host 'Installing PowerSTIG'
    $PowerStigVersion = $env:POWERSTIG_VERSION
    $null = Install-Module -Name 'PowerSTIG' -RequiredVersion $PowerStigVersion -Scope CurrentUser -Force -AllowClobber

    Write-Host "Executing Configuration at ${{ github.workspace}}\DSC\${{ env.DSC_CONFIGURATION_NAME }}.ps1"
    . ${{ github.workspace}}\DSC\${{ env.DSC_CONFIGURATION_NAME }}.ps1
    ${{ env.DSC_CONFIGURATION_NAME }} -NtpClientType "$env:DSC_CONFIGURATION_NTP_CLIENT_TYPE" -NtpServers "$env:DSC_CONFIGURATION_NTP_SERVERS"

from powerstig.

It is PS 5.1 in the runner agent also.

Downgrading to 4.18 works for Windows 2022

from powerstig.

Please attempt to run this on a 2022 VM rather than the Github Runner. I am not sure how those are configured, but I am not able to reproduce on a 2022 VM, so leaning towards this being a configuration issue with that container vs PowerSTIG.

Thank you,
Eric

from powerstig.

Hi @erjenkin
The new release of PowerSTIG 4.22, just four days fixed the windows2022 DSC compile issue!

https://www.powershellgallery.com/packages/PowerSTIG/4.22.0

Perhaps some fix went in. I am good to go. Closing this issue. Thank you for all your responses.

from powerstig.