You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
There are no documentation and evaluations for the current infrastructure setup on what security assumptions have been made and how we could improve them in the future.
What is your hypothesis?
Documenting this will allow us to act faster on upcoming security issues and constantly improve on this.
What value does this bring to our customer and/or our mission? What is the goal?
Increased security for our services and interfaces.
How do we measure it?
Possible periodic test described in the solution are ok
Overview
Security must be considered as a whole. As we have a final production (not a prototype) is our responsability to take care of this area.
For instance, if our smartcontracts are audited but a user who needs to transfer funds urgently (bear market maybe?) can't do it because the interface/service is down, we are not meeting the expectations.
rmeissner
changed the title
There is evaluation on security measures for our current infrastructure
There is no evaluation on security measures for our current infrastructure
May 5, 2022
Part 1: Define the problem
What problem are you trying to solve?
There are no documentation and evaluations for the current infrastructure setup on what security assumptions have been made and how we could improve them in the future.
What is your hypothesis?
Documenting this will allow us to act faster on upcoming security issues and constantly improve on this.
What value does this bring to our customer and/or our mission? What is the goal?
Increased security for our services and interfaces.
How do we measure it?
Links:
Part 2: Shaping the problem
Problem Owner
@luarx
Non Goal(s)
Solution
Overview
Security must be considered as a whole. As we have a final production (not a prototype) is our responsability to take care of this area.
For instance, if our smartcontracts are audited but a user who needs to transfer funds urgently (bear market maybe?) can't do it because the interface/service is down, we are not meeting the expectations.
For that reason, all of our teams must consider security when they are working instead of implementing security measures at the end of the process (https://en.wikipedia.org/wiki/Software_development_security).
Analysis:
Solutions can be:
Rough Scoping & Timeline
Risk(s), Key Trade Offs & Decisions
Alternative solutions & ideas
Open Questions
The text was updated successfully, but these errors were encountered: