WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@uplavikarnitish
Copy link

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 and Non-compliance found in the LINDDUN privacy threat modeling framework. More details can be found in the privacy-rules doc

These 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])

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` and `Non-compliance` found in the [LINDDUN](https://linddun.org/) privacy threat modeling framework. More details can be found in the [privacy-rules doc](./docs/privacy-rules.md)

These 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])
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant