Modified risk and model schemas #732
Open
+690
−138
Conversation
This file contains hidden or 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
| "risk": "Risk management perspective", | ||
| "stakeholder": "General stakeholder perspective", | ||
| "use-case": "A high level persepctive that captures the data-flows of the use case, rather than deep granularity of systems", | ||
| "abuse-case": "A high level persepctive that captures the data-flows of a certain abuse case, rather than deep granularity of systems", |
Member
There was a problem hiding this comment.
Remove use-case as this is covered in the usecase schema. Add abuse case to the threat schema
| "service": "Service or microservice", | ||
| "dataStore": "Database, file system, or data repository", | ||
| "data": "Data asset or dataset", | ||
| "data": "Dataset", |
Member
|
Thanks Petra. Let me know when these minor changes are in and I'll merge it in. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Issue:
As discussed in ticket #731 , this PR is a review of the schema
Model schema reviewed to ensure no data loss
Risk schema changes done based on risk and compliance tooling taxonomies to ensure compatibility (including data classification etc)
This PR is to use for discussion on the TM-BOM discussion 0 not for merging yet