Assert-WDACConfigIntegrity available parameters¶
Syntax¶
Assert-WDACConfigIntegrity
[-SaveLocally]
[-Path <FileInfo>]
[-SkipVersionCheck]
[<CommonParameters>]
Description¶
This cmdlet scans all of the relevant files in the WDACConfig module's folder and computes their SHA2-512 hashes.
Then it downloads the cloud CSV file from the GitHub repository and compares the hashes of the local files with the ones in the cloud.
By doing so, you can ascertain that the files in your local WDACConfig folder are identical to the ones in the cloud and devoid of any interference.
If there is any indication of tampering, the outcomes will be displayed on the console.
Parameters¶
-SaveLocally¶
This parameter is used to generate hashes of the final module's files prior to publishing them to the GitHub. This parameter shouldn't be used.
Type: | SwitchParameter |
---|---|
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-Path¶
Can define a different path for the Hashes.csv
file. This parameter shouldn't be used.
Type: | FileInfo |
---|---|
Position: | Named |
Default value: | Module's Root Directory |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Note¶
The WDACConfig module comprises of .ps1
and .psm1
files that bear the cryptographic signature of my local certificate authority's (CA) certificate. The module incorporates mechanisms to automatically ascertain the integrity of the module files and prevent any unauthorized modifications. The module manifest, .psd1
file, on the other hand, lacks a signature due to the installation error that arises from the PowerShell gallery when it is signed with a self-signed certificate.
The public key of the certificate used to sign the module files can be obtained from here.