CSVs generated by STIG viewer present some obstacles because CCI numbers are exported with additional information by STIG viewer. This caused errors when trying to apply the NIST tags to controls because the CCI cell reference within the CSV had extra information and was not compatible with our CCI to NIST XML mapping.
Basically this meant that the NIST control was always empty and the CCI tag had a bunch of extra information in it.
This also updates the generate_map file to use a separate class per sub-command (following a pattern I'm trying to standardize within the gem) and fixes spacing issues with the generated map YML.
CSVs generated by STIG viewer present some obstacles because CCI numbers are exported with additional information by STIG viewer. This caused errors when trying to apply the NIST tags to controls because the CCI cell reference within the CSV had extra information and was not compatible with our CCI to NIST XML mapping.
Basically this meant that the NIST control was always empty and the CCI tag had a bunch of extra information in it.
This also updates the generate_map file to use a separate class per sub-command (following a pattern I'm trying to standardize within the gem) and fixes spacing issues with the generated map YML.
Closes #200 Closes #201