Difference between revisions of "Security Team"
Jump to navigation
Jump to search
(Created page with "The Security Team is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures, be a point of contact for security related topics. __TO...") |
|||
Line 20: | Line 20: | ||
* [[Keybase]] <code>bisq.security</code> subteam | * [[Keybase]] <code>bisq.security</code> subteam | ||
+ | |||
+ | == Goals == | ||
+ | |||
+ | === What does "security" in "Security Team" mean === | ||
+ | |||
+ | * Optimize information footprint | ||
+ | * Hardening of the Bisq app, services, protocols, down to code | ||
+ | |||
+ | === Duties === | ||
+ | |||
+ | * find attack vectors | ||
+ | * design counter strategies | ||
+ | * act as a think-tank, consortium and knowledge base for security-related stuff | ||
+ | * firefighting | ||
+ | * no feature implementation work, because that is either dev or ops. | ||
+ | |||
+ | === General Roadmap === | ||
+ | |||
[[Category:Teams]] | [[Category:Teams]] |
Revision as of 16:31, 10 June 2020
The Security Team is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures, be a point of contact for security related topics.
Contents
Roles
Infrastructure
GitHub
Team
Repositories
Chat
- Keybase
bisq.security
subteam
Goals
What does "security" in "Security Team" mean
- Optimize information footprint
- Hardening of the Bisq app, services, protocols, down to code
Duties
- find attack vectors
- design counter strategies
- act as a think-tank, consortium and knowledge base for security-related stuff
- firefighting
- no feature implementation work, because that is either dev or ops.