added inputs to allow indication of operational requirements documented with ISSO #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ed with ISSO Signed-off-by: kemley76 <kemley@mitre.org>
wdower
approved these changes
Jun 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix to #39. Modeled these changes off of previous cases where ISSO waivers were mentioned such as SV-257970 and SV-257968. Added inputs where inputs weren't provided already. I avoided doing SV-257951 and SV-258040, because they did not fit the pattern with all the other changes and are a bit more complex. These seem to require a list of approved exemptions rather than just a
is_setting_or_module_an_operational_requirementtype of implementation.