Skip to content

The following guidelines provide a starting point for governance model design. The specific details of what you need to put in place depend on your own environment.

System and environment

The following table gives an overview of the factors relating to your system and environment to take into account when you design your governance model.

ElementDetails
DataData management needs to ensure smart usage of data, for example:
  • Data caching
  • Data for fetching policies
Domain structureThe domain hierarchy needs to be designed to fit the model, for example:
  • Whether to implement parallel domains or a single domain hierarchy
  • The depth and width of the domain structure
  • The number of subdomains associated with each domain
  • User-friendliness of domain names

For more information about domains and how the hierarchy affects policies, see Domains.
UsersUser administration needs to take the model into account, for example:
  • Number of user groups
  • Number of users per group
  • User-friendliness of group names
  • Usage of technical users (bots)

Policy framework

The following table gives an overview of the factors relating to your policy framework to take into account when you design your governance model.

ElementFactors to consider
Granularity and spreadThe framework needs to include an approach to policy coverage, for example:
  • All-encompassing or very specific
  • Granularity:
    • MECE approach (mutually exclusive, collectively exhaustive)
    • Russian doll approach: A stack of increasingly specific policies, for example:
      • BTC transfer (rank 100)
      • BTC transfer above 2 BTC (rank 50)
      • BTC transfer above 2 BTC to a non whitelisted address (rank 20)
  • Edge cases
FailsafeA failsafe mechanism needs to be considered, in the form of a breakglass policy. For more information, see Breakglass policy.