SCCA Mapping #162
Merged
SCCA Mapping #162
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
brooke-hamilton
requested review from
kyle-hoyer,
glennmusa,
Breanna-Stryker and
Phydeauxman
glennmusa
approved these changes
Apr 20, 2021
There was a problem hiding this comment.
Looks good to me. I left some suggestions for consistent product naming between components.
I imagine another field "Justification" or "Why Mission LZ doesn't address this" may be helpful for the N/A fields in some future, but don't think that's necessary today.
Co-authored-by: Glenn Musa <4622125+glennmusa@users.noreply.github.com>
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.
Description
Documentation on how Mission LZ maps to SCCA controls:
https://github.com/Azure/missionlz/blob/6c1112eefa2cc0b3aa299d477abec6ed0f9f5b8a/README.md#product-roadmap
Issue reference
The issue this PR will close: #38
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:
Code compiles or validates correctlyBASH scripts have been validated usingshellcheckAll tests pass (manual and automated).vscode/extensions.json.)