-
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 tagging to categorize controls #453
Comments
Would the additional component question feature work for this? You can add additional fields to components with that. |
Thank you I did not see that. I added some metadata to try it out. Is there a way to search for all the controls with similar metadata or view them in categories related to that? |
I'm not sure if that data is included in the search bar in the filter area and no way to filter by that as well. |
Okay. I think the component metadata would be preserved when releasing the STIG content, correct? I am interested in development tags that do not persist afterwards where we can filter or categorize controls for ease of development. For example, things like "needs research" "related to password policy", etc. |
I don't believe it's included in any exports. |
When developing STIG ready content, we have several controls that relate to each other. We are currently keeping a separate word document of notes to record which controls relate to each other (for example, all these controls relate to password policy, all these other controls relate to audit rules, etc.)
It would be great to tag/categorize this in the Vulcan app instead.
The text was updated successfully, but these errors were encountered: