Sidebar
cbdc:public:cbdc_omg:04_doc:20_comments:brp:q11:start
This is an old revision of the document!
Table of Contents
Question: 11. TBD Are there additional ways to manage potential risks associated with CBDC that were not raised in this paper?
Question
Are there additional ways to manage potential risks associated with CBDC that were not raised in this paper?
Answer
By all descriptions, the U.S. CBDC is primarily a large System-of-Systems (SoS) or even an SoS of SoSs. Some of these would ideally already exist and some will need to be created. The new systems are predominately a Software (SW) effort. Yes, there will be some specialized Hardware(HW) required, but the primary focus appears to be Software (including Commercial-Off-The-Shelf (COTS), Government Off-The-Shelf (GOTS), or Modified Off-The-Shelf (MOTS). This software will ultimately need to be Managed and Modified.
1. Risk of a Software Crisis
2. Risk of Lack of Stakeholder Buy-In
3. Risk due to Poor Community of Interest (CoI) Governance
4. Risk due to lack of Broad, Wide Ranging Security Planning
5. Risk of Data being hacked due weak Security Infrasture
6. Risk of Meta-Data being hacked due weak Security Infrasture
7. Risk of Business Processes Being Hacked
cbdc/public/cbdc_omg/04_doc/20_comments/brp/q11/start.1650828975.txt.gz · Last modified: 2022/04/24 15:36 by nick
Translations of this page:
