Difference between revisions of "Security Team"
Jump to navigation
Jump to search
| Line 35: | Line 35: | ||
* firefighting | * firefighting | ||
* no feature implementation work, because that is either dev or ops. | * no feature implementation work, because that is either dev or ops. | ||
| + | |||
| + | === Mode of operation === | ||
| + | |||
| + | Results and work of the security team might not be shared with the general public immediately. Simply because it makes no sense to publish a security vulnerability before it has been patched up. This is why the various channels of communication are invite-only. | ||
=== General Roadmap === | === General Roadmap === | ||
Revision as of 16:35, 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.securitysubteam
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.
Mode of operation
Results and work of the security team might not be shared with the general public immediately. Simply because it makes no sense to publish a security vulnerability before it has been patched up. This is why the various channels of communication are invite-only.
