PowerShell Protect should be able to enumerate its default rules

[DataTraveler1]

Is your feature request related to a problem? Please describe.

No. This feature request is an informational enhancement. This was discussed on the forums here.

Describe the solution you'd like

The full details of the default built-in rules that are shipped with PowerShellProtect should be enumerable and exportable from within the module (e.g. Get-PSPConfiguration).

Describe alternatives you've considered

I tried looking with the module files but I was not able to find any clues.

Additional context

I am sure there is a demand for this information. Any software that changes the system configuration is going to have demand for a precise list of what is actually being changed. For example, test criteria for a Windows server to pass OAT.

[adamdriscoll]

This issue has been mentioned on Ironman Software Forums. There might be relevant details there:

https://forums.ironmansoftware.com/t/question-about-the-default-built-in-rules/6607/3