You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#23 Since the server 2016 stig benchmark id doesn't contain MS or DC should the output file name be generated from the stig file name? Where in the stack would Split-StigXccdf have to be run to get a proper output file name?
The text was updated successfully, but these errors were encountered:
camusicjunkie
changed the title
Issue #23 didn't address Server 2016 stig benchmark id missing technology role
PR #23 didn't address Server 2016 stig benchmark id missing technology role
Jul 18, 2018
Thanks for catching that. I updated the function in PR #26
I wanted to keep the STIG archive clean, meaning that those files are dropped in unaltered. Split-StigXccdf is intended to be used outside of the normal conversion process for now. Just split the 2016 STIG and then parse each half independently. We were just getting started on the Windows Server 2016 before we moved all of this to GitHub, so we are still working through it. Thanks again for digging into this with us. I really helps to have more eyes on it.
#23 Since the server 2016 stig benchmark id doesn't contain MS or DC should the output file name be generated from the stig file name? Where in the stack would
Split-StigXccdf
have to be run to get a proper output file name?The text was updated successfully, but these errors were encountered: