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
When a new version of a STIG comes out, Inspec profile developers currently have to copy and paste the check code into the new stub generated by inspec_tools. It would be great if, when generating the stubs for a new version of a STIG to take a parameter that is the old profile and move the check code to the new profile.
Use the DISA provided mapping from old to new controls for STIGS that are upgraded by a major version number i.e RHEL V2.6 to V3.0
The text was updated successfully, but these errors were encountered:
When a new version of a STIG comes out, Inspec profile developers currently have to copy and paste the check code into the new stub generated by inspec_tools. It would be great if, when generating the stubs for a new version of a STIG to take a parameter that is the old profile and move the check code to the new profile.
Use the DISA provided mapping from old to new controls for STIGS that are upgraded by a major version number i.e RHEL V2.6 to V3.0
The text was updated successfully, but these errors were encountered: