-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Threat Modeling for notation (TS+TP+Envelope) #391
Comments
Discussed on community call today. Would be good to have some brief things written out for process of trying to find vulnerabilities and then if issue(s) found, file issue(s) to help mitigate. Idea would be work shared amongst dev area ownership for those who are most familiar with codebase. Needs estimate. |
Putting this for RC-1, but this would be last thing which could potentially be cut and pushed to RC-2. IMO - I believe would be good right after RC-1 and if we find things, ok to release shortly after fix/patches from RC-1. |
Confirmed to move this issue out of rc-1 scope. Now moved to "Discuss". We will review all the issues later for rc-2 release scope. |
Threat modeling involves identifying ways that an adversary might try to attack notation and then designing mitigations to prevent, detect or reduce the impact of those attacks.
Aspect:
TS+TP+Envelope - 1 SDE week
Other Aspect is tracked under the issue : #409
The text was updated successfully, but these errors were encountered: