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
{{ message }}
This repository has been archived by the owner on Mar 26, 2024. It is now read-only.
I would like to use inspec_delta to go from the RHEL 7 profile to a RHEL 8 profile.
At present, RHEL 8's STIG controls have different Vul IDs than RHEL 7 (RHEL 7 STIG controls start with V-7, V-8, or V-9, while the RHEL 8 controls start with V-2). As a result inspec_delta will simply stub out control metadata for what it parses as "new" controls, even though I suspect that many of the controls' describe blocks for RHEL 8 will wind up being very similar to RHEL 7.
It would be very helpful if inspec_delta had a way to map new Vuln IDs to their old counterparts to allow the control code to transfer to the new profile (while still using the new STIG's tags, description, etc.).
The text was updated successfully, but these errors were encountered:
I would like to use inspec_delta to go from the RHEL 7 profile to a RHEL 8 profile.
At present, RHEL 8's STIG controls have different Vul IDs than RHEL 7 (RHEL 7 STIG controls start with V-7, V-8, or V-9, while the RHEL 8 controls start with V-2). As a result inspec_delta will simply stub out control metadata for what it parses as "new" controls, even though I suspect that many of the controls'
describe
blocks for RHEL 8 will wind up being very similar to RHEL 7.It would be very helpful if inspec_delta had a way to map new Vuln IDs to their old counterparts to allow the control code to transfer to the new profile (while still using the new STIG's tags, description, etc.).
The text was updated successfully, but these errors were encountered: