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:20_comments:brp:q11:05_risks [2022/04/24 15:35] nick |
cbdc:public:cbdc_omg:04_doc:20_comments:brp:q11:05_risks [2022/06/17 19:05] (current) terrance |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 5. Risk of Data being hacked due weak Security Infrasture ====== | + | ====== 5. Risk of Data being hacked due to weak Security Infrastructure ====== |
| - | [[cbdc:private:cbdc_omg:04_doc:20_comments:brp:q11:start | Return to Question 11]] | + | |< 100% >| |
| + | | [[cbdc:public:cbdc_omg:04_doc:20_comments:brp:q11:start| Return to Question 11]] | <WRAP> | ||
| + | <html><b> | ||
| + | <a href="mailto:[email protected]?Subject=OMG's CBDC WG Response: | ||
| + | 11.5. Risk of Data being hacked due weak Security Infrasture | ||
| + | ">Provide Feedback</a></b> | ||
| + | </html> | ||
| + | </WRAP> | | ||
| - | : //When Senator Mark Warner (D-VA) questioned witness Dr. Neha Narula, Director of the Digital Currency Initiative at MIT, on security risks associated with cryptocurrencies, she responded that, with respect to ransomware attacks, the issue is that valuable data has not been properly secured, and suggested that a CBDC could have built-in safeguards. She also believed that open source software is critical for security.//(( | + | : //When Senator Mark Warner (D-VA) questioned witness Dr. Neha Narula, Director of the Digital Currency Initiative at MIT, on security risks associated with cryptocurrencies, she responded that, with respect to ransomware attacks, the issue is that valuable data has not been properly secured, and suggested that a CBDC could have built-in safeguards. She also believed that open-source software is critical for security.//(( |
| Buckley Firm, | Buckley Firm, | ||
| __Senate holds hearing on central bank digital currency__, | __Senate holds hearing on central bank digital currency__, | ||
| Line 10: | Line 17: | ||
| )) | )) | ||
| - | Data can exist in many states depending on how it is being used. Each of the different Data States poses its own risks of compromising data. The primary concern with data is that it compromises End User Privacy. See section [[cbdc:private:cbdc_omg:04_doc:15_common:45_privacy:start]]. | + | Data can exist in many states depending on how it is being used. Each of the different Data States poses its own risks of compromising data. The primary concern with data is that it compromises End User Privacy. See section [[cbdc:public:cbdc_omg:04_doc:15_common:45_privacy:start]]. |
| The risks and concerns about Data in each of the different states are also important. Often, the primary focus for understanding data is to concentrate on [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:d:dataatrest | Data-at-Rest]]. Although this data is relatively static, it can change over time. In the past, there was little concern for [[https://www.omgwiki.org/dido/doku.php?id=[dido:public:ra:xapend:xapend.a_glossary:d:data_in_motion | Data-in-Motion ]], which can have serious effects on [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:r:ram | Reliability, Maintainability, and Availability (RAM)]], as well as, [[https://www.omgwiki.org/dido/doku.php?id=[dido:public:ra:1.4_req:2_nonfunc:25_security | Securability]] and can leave a system vulnerable to breaches. With the advent of HTTPS, these vulnerabilities are mitigated. The latest issue has become the need to secure [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:d:data_in_use | Data-In-Use]]. A recent WhatsApp data breach (( | The risks and concerns about Data in each of the different states are also important. Often, the primary focus for understanding data is to concentrate on [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:d:dataatrest | Data-at-Rest]]. Although this data is relatively static, it can change over time. In the past, there was little concern for [[https://www.omgwiki.org/dido/doku.php?id=[dido:public:ra:xapend:xapend.a_glossary:d:data_in_motion | Data-in-Motion ]], which can have serious effects on [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:r:ram | Reliability, Maintainability, and Availability (RAM)]], as well as, [[https://www.omgwiki.org/dido/doku.php?id=[dido:public:ra:1.4_req:2_nonfunc:25_security | Securability]] and can leave a system vulnerable to breaches. With the advent of HTTPS, these vulnerabilities are mitigated. The latest issue has become the need to secure [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:d:data_in_use | Data-In-Use]]. A recent WhatsApp data breach (( | ||
| Line 25: | Line 32: | ||
| <figure DataStateFigure> | <figure DataStateFigure> | ||
| - | {{ :cbdc:private:cbdc_omg:04_doc:20_comments:brp:q11:data_states.png?600 |}} | + | {{ cbdc:04_doc:20_comments:brp:q11:data_states.png?600 |}} |
| <caption>The Various States of Data.</caption> | <caption>The Various States of Data.</caption> | ||
| </figure> | </figure> | ||