Privacy Rules Contribution From Comcast-SPIDER #138
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 contribution contains 12 privacy rules that detect privacy risks for a given architecture model (in a YAML file). These privacy rules detect risks which could be classified under threat categories like
Linking
,Identifying
,Data Disclosure
,Unawareness
andNon-compliance
found in the LINDDUN privacy threat modeling framework. More details can be found in the privacy-rules docThese privacy rules are contributed by the SPIDER team from Comcast Cybersecurity.
Thank you!
Contacts:
Nitish Uplavikar ([email protected])
Nuray Baltaci Akhuseyinoglu ([email protected])
Bahman Rashidi ([email protected])