Skip to content

Latest commit

 

History

History
22 lines (20 loc) · 1.26 KB

Principle of Separation of Privilege.md

File metadata and controls

22 lines (20 loc) · 1.26 KB

“Where feasible, a protection mechanism that requires two keys to unlock it is more robust and flexible than one that allows access to the presenter of only a single key” — Ensure that critical privileges are separated across multiple actors so that there are no single points of failure/abuse.

A good example of this is to require a multisig address (not EOA) for privileged actors (e.g. owner, admin, governor, deployer) who control key contract functionality such as pause/unpause/shutdown, emergency fund drain, upgradeability, allow/deny list and critical parameters.

The multisig address should be composed of entities that are different and mutually distrusting/verifying. (See Saltzer and Schroeder's Secure Design Principles)


Slide Screenshot

0193.jpg


Slide Text

  • Separation of Privilege
  • Saltzer & Schroeder 1975
  • Privileges -> Separated
  • Multiple Actors
  • E.g.: Multi-Sigs vs EOA
  • Separation -> No Single Point of Failure

References


Tags