-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add ability to include custom tags in InSpec #493
Comments
My original thought for this was that we had both a 'tags' and 'inputs' table for each Vulcan project so that the project would know what tags and inputs had been used in the controls already and we could avoid duplication or 'like inputs/tags' from being introduced. Much like in github were the system knows 'labels' that exist and suggest you reuse rather then recreate. Aligning that controls use of that tag or input may be something we add the the 'constructor' as an optional object we can pass in at runtime / create time. |
Currently we cannot add additional metadata to the InSpec code that is generated.
Proposing either adding an option to include component "Addtional Questions" as additional tags or add a new option to specify new key,value custom tag data to add to controls in a component.
Currently we have these tags that are auto generated:
tag severity: 'low'
tag gtitle: 'SRG-APP-000141-AS-000095'
tag gid: nil
tag rid: nil
tag stig_id: 'VABC-50-000142'
tag cci: ['CCI-000381']
tag nist: ['CM-7 a']
Custom tags would be the same so if we had an additional question of "Color" with a value of "Blue" we could check a box to indicate it should be added as a tag.
tag color: 'Blue'
The text was updated successfully, but these errors were encountered: