Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically Determine RoleSets for each server #6

Closed
mapresto opened this issue Feb 6, 2019 · 1 comment
Closed

Automatically Determine RoleSets for each server #6

mapresto opened this issue Feb 6, 2019 · 1 comment
Assignees
Labels
enhancement New feature or request PowerShell
Milestone

Comments

@mapresto
Copy link
Owner

mapresto commented Feb 6, 2019

Is your feature request related to a problem? Please describe.
Right now, we are using a compliance mapping in SQL to map servers to the roles that are being scanned against. Using PowerShell logic in either Invoke-PowerStigScan or Invoke-PowerStigBatch, we should determine if the relevant roles/applications are installed and use that to scan against.

Describe the solution you'd like
Test against WMI/Registry/WindowsFeature to determine what is installed out of the supported kit and dynamically assign those roles to be scanned on the server. This should be able to be compared at the end to ensure that a new mof and/or ckl is created for each role determined.

@mapresto mapresto added enhancement New feature or request PowerShell labels Feb 6, 2019
@mapresto mapresto added this to the 2.0.0.0 milestone Feb 6, 2019
@mapresto mapresto self-assigned this Feb 6, 2019
@mapresto
Copy link
Owner Author

Complete in 2.0.0.0. DotNet is current set as a hard false until PowerStig starts generating results for the test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request PowerShell
Projects
None yet
Development

No branches or pull requests

1 participant