Integrate the the SCAP Extensions. Make it easier to use, faster, and include dashboards\reports.
- Make a GUI for running the SCAP extensions. Preferably integrate the SCAP extensions into SCCM so SCAPtoDCM.exe can be run from right clicking Compliance Settings
- Reduce the amount of PowerShell code created in each Configuration Item (CI). A CI that checks for the existence of a registry key is very long. Additionally, some of the CI’s will either timeout or require an increase in the timeout time which could affect client performance.
- CI’s created should not use the oval ID as its name as it cannot be correlated to practical information. In the case of DISA STIGS, the CI name should be the Vulnerability ID.
- Each CI should contain the Vulnerability ID, STIG ID, Severity, and Title within it so that any report generated will provide meaningful data.
- STIG Vulnerability ID’s that contain multiple definitions should have each definition place in it meaning a SCCM CI could have more than one script.
- CI’s should have categories assigned to it
- Scripts shouldn’t query Win32_UserAccount
- There should be a dashboard and sub reports for SCAP baselines. The default reports make it difficult to use the data created by the SCAPtoDCM tool. Ideally, a reporting pane specifically for SCAP extensions, similar to the SCEP console reports.