Extend the generated oscal with all the .csv fields #36
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
Signed-off-by: Donald Hunter <[email protected]>
Include all of the .csv fields in the generated oscal by using a list of properties under each control. Signed-off-by: Donald Hunter <[email protected]>
JonZeolla
approved these changes
May 10, 2024
JonZeolla
merged commit 7006bdb
into
cloud-native-security-controls:main
1 check passed
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.
Map .csv fields to props in the generated oscal.
Some of the content needs to be sanitised (remove leading/trailing whitespace, etc.) to pass the trestle field constraints. I chose to do this programmatically rather than modifying the source in the .csv file.