Skip to content
This repository has been archived by the owner on Jun 17, 2020. It is now read-only.

O> Attack Governance Model #135

Closed
patrick727 opened this issue Nov 2, 2017 · 7 comments
Closed

O> Attack Governance Model #135

patrick727 opened this issue Nov 2, 2017 · 7 comments
Assignees
Labels
needs-SMART-objective Specific; Measurable; Assignable; Realistic; Time-related Security Voting guide: @Jake-Gillberg @jimscarver @allancto zz-Governance NEEDS SPONSOR guides @jimscarver, @barneycinnamon, @rayzor zz-Operations NEEDS SPONSOR guides: @TrenchFloat, @jimscarver @Tonyprisca13

Comments

@patrick727
Copy link
Contributor

patrick727 commented Nov 2, 2017

Phil's POV "a critical part of the security of the whole platform. one has to avoid that the coop ends up being a SPOF due to political centralization & centralization of development decisions as well as centralization of staking coins. after all the coop has a jurisdiction and that might be an SPOF as well. I know it sounds weird at this point but maybe more restrictions of the coop's power might be better for the overall platform security. also it is much harder to restrict the power of the coop later on."

  1. Define Governance Process'
  2. Postulate attack vectors
  3. Test through small scale experiments within a Circle
  4. Review the results
@Ojimadu Ojimadu self-assigned this Nov 3, 2017
@kitblake kitblake self-assigned this Nov 10, 2017
@Ojimadu
Copy link
Contributor

Ojimadu commented Nov 19, 2017

https://docs.google.com/document/d/1EW0H833BsBZV9hWQC7cl3_KucMbckQfPpVQtEK3JOuQ/edit?usp=sharing

This a first draft i wrote, we would be need some volunteers to test these postulations.

Edit: I just realised this issue was for the governance committee which am not part of. Since the links is here already I would leave it for as a note. Except there is a need to remove it.

@Ojimadu Ojimadu removed their assignment Nov 20, 2017
@Phistr90 Phistr90 self-assigned this Dec 4, 2017
@patrick727 patrick727 changed the title Attack Governance Model M> Attack Governance Model Dec 9, 2017
@patrick727 patrick727 changed the title M> Attack Governance Model O> Attack Governance Model Dec 9, 2017
@patrick727 patrick727 added zz-Governance NEEDS SPONSOR guides @jimscarver, @barneycinnamon, @rayzor zz-Operations NEEDS SPONSOR guides: @TrenchFloat, @jimscarver @Tonyprisca13 labels Jan 2, 2018
@9rb 9rb self-assigned this Jan 20, 2018
@Keaycee
Copy link
Contributor

Keaycee commented Jan 25, 2018

This is also a document on Governance process for your review. Make suggestions and correction if needed. #133

@dckc
Copy link
Contributor

dckc commented Feb 8, 2018

@pmoorman see? We've been talking about this openly for some time. This might be an even better place for your analysis than #261.

@dckc dckc added the Security label Feb 8, 2018
@pmoorman
Copy link

pmoorman commented Feb 9, 2018

@dckc yes, I even wrote it for this issue initially, to be honest.

Oke so for everyone else: a week ago @traviagio and I made an analysis of the "attack vectors" that we currently see exposed (or can easily imagine) in the Coop governance structure.

The document can be found here:

Analysis of attack vectors: https://docs.google.com/document/d/1qHQIuzj83VeZjusy6AvK7PAoKrg0CKP2SQTtNYv_3GI/edit?usp=sharing

Main findings:

  • Whether intentional or not, we can already look back through our history and see "attacks". (notice that attacks don't necessarily constitute bad intentions, but rather hint at exposed attack vectors)

  • Many attacks are much simpler than previously thought

  • In the document, we outline 6 of the most common attack vectors

  • We also provide suggested improvements

  • I collaborated with @dckc to integrate our findings into a new 'spreadsheet-killer' tool that he's building that will replace the current spreadsheet. In the document I reflected our main conclusions and ideas.

@TrenchFloat
Copy link
Contributor

I'm assuming this has been solved by the web app in #260 and the trust metric in #375.

@Phistr90 Phistr90 reopened this Jun 7, 2018
@dckc
Copy link
Contributor

dckc commented Jun 7, 2018

@Phistr90 be sure to explain why when you reopen an issue.

@dckc dckc closed this as completed Jun 7, 2018
@Phistr90
Copy link

Phistr90 commented Jun 8, 2018

@dckc This has just been resolved and addressed as well as analysed in regards to attack vectors of the bounty system.
The original intention was imo to cover as many coop related attack vectors. That also would include for example attacks like hostile takeovers of the coop due to current bylaws or for example regulatory risks due to the fact that the coop is a legal entity within the US jurisdiction.

I might be wrong here, in this case please point me to the extensive attack vector analysis.

@dckc dckc reopened this Jun 9, 2018
@jimscarver jimscarver added the needs-SMART-objective Specific; Measurable; Assignable; Realistic; Time-related label Jun 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs-SMART-objective Specific; Measurable; Assignable; Realistic; Time-related Security Voting guide: @Jake-Gillberg @jimscarver @allancto zz-Governance NEEDS SPONSOR guides @jimscarver, @barneycinnamon, @rayzor zz-Operations NEEDS SPONSOR guides: @TrenchFloat, @jimscarver @Tonyprisca13
Projects
None yet
Development

No branches or pull requests