Default controls to unsatisfied by not including satisfies:
frontmatter in templates
#85
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.
This is an alternate approach to #79 that would fix #77 in a backwards compatible manner.
Instead of changing to a new frontmatter format that requires a
live
property to satisfy controls this PR merely updates the template files to have thesatisfies
property commented out by default.This has the effect that newly Comply generated compliance programs start by showing the 61 controls from TSC-2017.yaml as unsatisfied. The
TODO.yml
is also updated to reference a step in the customize policies phase for uncommenting thesatisfies
frontmatter.I also removed the
satisfies
frontmatter altogether from templates where the TSC mapped isCC9.9
. That's not a real criteria and seems to have been added as a placeholder. No sense in confusing people new to the TSC with fictitious listings.