cbdc:public:cbdc_omg:04_doc:90_recommend:80_recomend:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cbdc:public:cbdc_omg:04_doc:90_recommend:80_recomend:start [2022/05/13 17:32] terrance |
cbdc:public:cbdc_omg:04_doc:90_recommend:80_recomend:start [2022/06/17 19:42] (current) terrance |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== 6.09 Baked-in Security ====== | ===== 6.09 Baked-in Security ====== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:90_recommend:start| Return to Recommendations]] | + | |< 100% >| |
| + | | [[cbdc:public:cbdc_omg:04_doc:90_recommend:start| Return to Recommendations ]] | <WRAP> | ||
| + | <html><b> | ||
| + | <a href="mailto:[email protected]?Subject=OMG's CBDC WG Response: | ||
| + | 6.09 Baked-in Security | ||
| + | ">Provide Feedback</a></b> | ||
| + | </html> | ||
| + | </WRAP> | | ||
| - | The OMG members recommend the Federal Reserve define a task to ensure that Security is baked into the U.S. CBDC rather than trying to //post facto// add it later (i.e bolted-on). | + | The OMG's CBDC WG members recommend the Federal Reserve define a task to ensure that Security is baked into the U.S. CBDC rather than trying to //post facto// add it later (i.e bolted-on). |
| Also see the answers to: | Also see the answers to: | ||
| - | : 1. [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q13:sb_01:start]] | + | : 1. [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q13:sb_01:start]] |
| - | * [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q13:sb_01:prt_b:start]] | + | * [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q13:sb_01:prt_b:start]] |
| - | : 2. [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q07:start]] | + | : 2. [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q07:start]] |
| - | * [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q07:start#lack_of_reporting_and_oversight | Lack of Reporting and Oversight]] | + | * [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q07:start#lack_of_reporting_and_oversight| Lack of Reporting and Oversight]] |
| - | : 3. [[cbdc:private:cbdc_omg:04_doc:20_comments:dsn:q18:start]] | + | : 3. [[cbdc:public:cbdc_omg:04_doc:20_comments:dsn:q18:start]] |
| - | : 4. [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q02:start]] | + | : 4. [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q02:start]] |
| Cryptocurrency skirts near the edges of illegal, illicit, or shady interactions and transactions. The Chainalysis Team recently published their 2021 findings(( | Cryptocurrency skirts near the edges of illegal, illicit, or shady interactions and transactions. The Chainalysis Team recently published their 2021 findings(( | ||
| Line 29: | Line 36: | ||
| - | It appears that the [[https://www.omgwiki.org/CBDC/doku.php?id=cbdc:private:cbdc_omg:04_doc:15_common:08_currency_models:10_cash:start | Digital Cash Model]] is less vulnerable than the [[https://www.omgwiki.org/CBDC/doku.php?id=cbdc:private:cbdc_omg:04_doc:15_common:08_currency_models:15_accounts:start | Digital Account Model]]. The use of Stablecoins could help with maintaining the value of CBDC, but would not add any security. | + | It appears that the [[cbdc:public:cbdc_omg:04_doc:15_common:08_currency_models:10_cash:start | Digital Cash Model]] is less vulnerable than the [[cbdc:public:cbdc_omg:04_doc:15_common:08_currency_models:15_accounts:start | Digital Account Model]]. The use of Stablecoins could help with maintaining the value of CBDC, but would not add any security. |
| - | Regardless of which model ([[cbdc:private:cbdc_omg:04_doc:15_common:08_currency_models:15_accounts:start| Digital Accounts]], [[cbdc:private:cbdc_omg:04_doc:15_common:30_stablecoins:start| Stablecoins]], [[cbdc:private:cbdc_omg:04_doc:15_common:08_currency_models:10_cash:start| Digital Cash]]) is used for the CBDC, the [[https://www.omg.org/ | Object Management Group ]] recommends that the Federal Reserve consider Seurity of the system from the earliest phases of the U.S. CBDC. This means having the Non-Functional requirement of Security be well defined and formal. | + | Regardless of which model ([[cbdc:public:cbdc_omg:04_doc:15_common:08_currency_models:15_accounts:start| Digital Accounts]], [[cbdc:public:cbdc_omg:04_doc:15_common:30_stablecoins:start| Stablecoins]], [[cbdc:public:cbdc_omg:04_doc:15_common:08_currency_models:10_cash:start| Digital Cash]]) is used for the CBDC, the [[https://www.omg.org/ | Object Management Group's ]] CBDC WG recommends that the Federal Reserve consider Seurity of the system from the earliest phases of the U.S. CBDC. This means having the Non-Functional requirement of Security be well defined and formal. |
| One way to accomplish this is through the use of a Model-Based Systems Engineering (MBSE) and Unified Architecture Framework (UAF) to model all aspects of the CBDC before it is built. Since the requirements for the security of the system are a moving, ever-changing target, this does not mean that every security issue must be fully understood or specified before work can begin. It means that at every step, the Security question needs to be raised. The CBDC is a complex issue that, once released, could have a life expectancy of many, many years. Only through extensive Systems Analysis, Engineering, and Design will the CBDC have the stability it needs to instill confidence in the public. | One way to accomplish this is through the use of a Model-Based Systems Engineering (MBSE) and Unified Architecture Framework (UAF) to model all aspects of the CBDC before it is built. Since the requirements for the security of the system are a moving, ever-changing target, this does not mean that every security issue must be fully understood or specified before work can begin. It means that at every step, the Security question needs to be raised. The CBDC is a complex issue that, once released, could have a life expectancy of many, many years. Only through extensive Systems Analysis, Engineering, and Design will the CBDC have the stability it needs to instill confidence in the public. | ||
| Line 42: | Line 49: | ||
| <figure DataStateFigure> | <figure DataStateFigure> | ||
| - | {{ :cbdc:private:cbdc_omg:04_doc:20_comments:brp:q13:sb_02:datastateflow.png?700 |}} | + | {{ cbdc:04_doc:20_comments:brp:q13:sb_02:datastateflow.png?700 |}} |
| <caption>The various States of Data</caption> | <caption>The various States of Data</caption> | ||
| </figure> | </figure> | ||
| Line 61: | Line 68: | ||
| </WRAP>| | </WRAP>| | ||
| </table> | </table> | ||
| + | \\ | ||
| <table> | <table> | ||
| <caption>White Paper Desirements related to disruption and security</caption> | <caption>White Paper Desirements related to disruption and security</caption> | ||
cbdc/public/cbdc_omg/04_doc/90_recommend/80_recomend/start.1652477563.txt.gz · Last modified: 2022/05/13 17:32 by terrance
