microsoft / microsoft/PowerStig
Convert the old .ckl format for STIG Checklists to the more modern .cklb format after generating with New-StigCheckList cmdlet
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 619
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
Since New-StigCheckList can only generate STIG Checlists as .ckl format (unless my research is wrong) and because I was needing .cklb formatted STIG Checklists and didn't want to have to go around my automation and put them in STIG Viewer or some other app to do the conversion for me I concocted some PowerShell that converts the xml-based .ckl to the json-based .cklb formatted STIG Checklists. Its setup as a function currently and it just runs along side my scripts to make PowerSTIG do its thing and spit out the checklists I need afterwards.
If anyone would like that PowerShell let me know, Perhaps it can get integrated into a future PowerSTIG release since .ckl files have been more or less deprecated for several years now.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the New-StigCheckList cmdlet and confirm whether it currently produces only .ckl output. Compare the existing XML-based .ckl and JSON-based .cklb checklist requirements, then determine how conversion should fit into PowerSTIG. Done should include an agreed integration point and validation that the generated .cklb checklist works without STIG Viewer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100