Potential damage
- Low
- Medium
- High
- Very high
Decisions:
- Accept: acknowledge the risk, but do not take any action before it hits
- Mitigate: take measures to reduce the probability of occurrence or the potential damage
- Avoid: do something else without this risk, e.g. nothing
- Transfer: let someone else take care of it, e.g. insurance
- (Deny the risk: not allowed to choose, but many managers do this nevertheless...)
Probability of occurrence | Potential damage | Decision | Reasons | |||
---|---|---|---|---|---|---|
Financial | 1 | GAFAM |
|
|
| Financially it is not possible to compete with GAFAM Mitigate→ find approach against GAFAM in strategic category |
2 | Competing technology |
|
|
| ||
3 |
Market Growth Challenges
Marketing |
|
|
| Mitigate→
| ||
4 | Funding |
|
|
| participating in projects and present ourself and requirements and capabilities | |
5 | Environmental cost |
|
|
| not selecting environmental consuming technology like some types of ledgers | |
Legal | 6 | Governments Rules |
|
|
|
|
7 |
Environmental cost
Governments Rules
International Compatibility (ex. GDPR) |
|
Dependency
Intermediaries
Acceptance
Engagement (Governance Rules)
Usability
Interoperability (Standards and Protocols)
Integration
Communication (Marketing)
Physical vulnerabilities (Device lost)
Protecting sensitive data
|
|
| same as above plus finding common denominator solutions | |||
8 | Misusing of DID |
|
|
| Refer to existing solution like revoking ID | |
9 | User Responsibility |
|
|
|
| |
Strategic | 10 | Dependency |
|
|
| |
11 | Intermediaries |
|
|
| Improvement in EUDI wallet | |
12 | Exposure to Governance Rules and standards |
|
|
| ||
13 | Usability |
|
|
| Existing system are still in place, and we improve the products and solutions continuously. | |
14 | Acceptance |
|
|
| Existing system are still in place, and we improve the products and solutions continuously. | |
15 | Interoperability (Standards and Protocols) |
|
|
| mitigate the risk with customization | |
16 | Integration |
|
|
| mitigate the risk with development | |
17 | ontopiness |
|
|
| come up with new services | |
Security | 18 | Protecting data |
|
|
| any security solution
|
19 | Losing data |
|
|
| improve recovery processes | |
20 | Dark Net |
|
|
| ||
21 | Trust Infrastructure |
|
|
|
- Consensus
many times in a year |
|
| User Responsibility |
|
once in 1 years | Funding |
| ||
once in 2 years | Dark Net |
| ontopiness | |
once in 5 years | Trust Infrastructure | |||
once in 10 years | Environmental cost | |||
Occurrence |
Probability / Potential damage | Low | Medium | High | Very High |
- No-consensus-pile
.....