-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added --control-id flag #229
Conversation
I'd use a v3 RedHat xccdf |
Updated the RHEL7 V1R4 example profile to V3R3 |
5191e74
to
f87e4bf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the option a string instead of boolean?
…hey want the created profile to use legacy vuln IDs (ex. 'V-XXXXX') or rule IDs as the control IDs for the generated profile Signed-off-by: Will Dower <[email protected]>
Signed-off-by: Will Dower <[email protected]>
Signed-off-by: Will Dower <[email protected]>
Signed-off-by: Will Dower <[email protected]>
Signed-off-by: Will Dower <[email protected]>
f87e4bf
to
e87e92e
Compare
I think we left it a string so that we could eventually use any tag for the control_id as opposed to just a flag for using the legacy vulnID (which for now would need to default to true anyway). But the logic using the variable does expect it to be either ruleID or vulnID. |
note that there seem to be at least two ids hat are considered 'legecy' so it looks like it need to be an array |
Signed-off-by: Robert Clark <[email protected]>
94fece0
to
fa7c87a
Compare
We are already mapping over the legacy array so this shouldn't be an issue. |
Signed-off-by: Robert Clark <[email protected]>
fa7c87a
to
8f849eb
Compare
Added --control-id flag to xccdf2inspec to allow user to specify if they want the created profile to use legacy vuln IDs (ex. 'V-XXXXX') or rule IDs as the control IDs for the generated profile
resolves #218
Signed-off-by: Will Dower [email protected]