Differences

This shows you the differences between two versions of the page.

--- dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:start [2021/11/06 16:00]
char
+++ dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:start [2022/04/23 21:45] (current)
nick
@@ Line 2: / Line 2: @@
 [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:start| Return to Data Taxonomy]]
-Data can exist in many states depending on how it is being used. The risks and concerns about Data at each of the different states are also important. Often, the primary focus for understanding data is to concentrate on [[dido:public:ra:xapend:xapend.a_glossary:d:dataatrest]]. Although this data is relatively static, it can change through time. In the past, there was little concern for [[dido:public:ra:xapend:xapend.a_glossary:d:data_in_motion]], which can have serious effects on [[dido:public:ra:xapend:xapend.a_glossary:r:ram]], as well as, [[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 [[dido:public:ra:xapend:xapend.a_glossary:d:data_in_use]]. A recent WhatsApp data breach ((
+===== Overview =====
+[[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:start | Return to Top]]
+Data can exist in many states depending on how it is being used. 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 [[dido:public:ra:xapend:xapend.a_glossary:d:dataatrest]]. Although this data is relatively static, it can change over time. In the past, there was little concern for [[dido:public:ra:xapend:xapend.a_glossary:d:data_in_motion]], which can have serious effects on [[dido:public:ra:xapend:xapend.a_glossary:r:ram]], as well as, [[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 [[dido:public:ra:xapend:xapend.a_glossary:d:data_in_use]]. A recent WhatsApp data breach ((
 Czarina Grace,
 __WhatsApp Data Breach 2021 Could Expose 2 Billion Users: Update Now on Android, iOS to Fix Security Risk__,
@@ Line 11: / Line 14: @@
 )) found that switching data between image filters could cause memory corruption followed by a crash that left data exposed.
-<figure DataState>
+Figure {{ref>DataStateFigure}} graphically represents the different Data States within a system. Most systems are now able to handle the Data-in-Motion and the Data-at-Rest issues but have traditionally relied on physical security to protect Data-in-Use.
+<figure DataStateFigure>
 {{  :dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:screen_shot_2021-10-06_at_3.06.39_pm.png?600  |}}
 <caption>The various States of Data</caption>
+</figure>
+===== Data States =====
+[[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:start | Return to Top]]
+The only way to control access to the data at the various Data States is to control all aspects of the system:
+  * Data Storage
+  * Data Transmission
+  * Data Processing
+Therefore, a very important Function Decision to make is what is the nature of the [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:start | Distributed System Network Access Control]].
+Network access control [[dido:public:ra:xapend:xapend.a_glossary:t:taxonomy|taxonomy]] classifies the types of access individuals (i.e., [[dido:public:ra:xapend:xapend.a_glossary:n:node|nodes]]) have from outside and from within the [[dido:public:ra:xapend:xapend.a_glossary:n:node_network|node network]]. The two main classes of [[dido:public:ra:xapend:xapend.a_glossary:a:accesscontrol|access control]] are
+[[dido:public:ra:xapend:xapend.a_glossary:p:permissionless| permissionless]] and
+[[dido:public:ra:xapend:xapend.a_glossary:p:permissioned| permissioned]].(("Public Vs Private Blockchain In A Nutshell",
+Demiro Massessi, 12 December 2018,
+[[https://medium.com/coinmonks/public-vs-private-blockchain-in-a-nutshell-c9fe284fa39f]]
+))
+Within each of these two classifications it is possible to have
+[[dido:public:ra:xapend:xapend.a_glossary:p:public_network| public]] and
+[[dido:public:ra:xapend:xapend.a_glossary:p:private_network| private]] access. Public and private access define who is able to write data onto a network or [[dido:public:ra:xapend:xapend.a_glossary:l:ledger|ledger]]. In contrast, open (i.e., permissionless) and closed (i.e., permissioned) determine who is able to read the data. Networks are classified as(("Public Vs Private Blockchain In A Nutshell",
+Demiro Massessi, 12 December 2018,
+[[https://medium.com/coinmonks/public-vs-private-blockchain-in-a-nutshell-c9fe284fa39f]]
+)):
+  * public and open
+  * public and closed
+  * private and open
+  * private and closed
+<figure>
+{{ dido:public:ra:1.2_views:1_stake:3_taxonomic:access_control_taxonomy.png?400 |}}
+<caption>The Node Network Access Taxonomy
+</caption>
 </figure>
@@ Line 20: / Line 60: @@
 <nspages -tree dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy -exclude -subns -pagesInNs -h1 -textNs="">
-<color blue><todo @char>New section - review plus all subsections</todo></color>
+<color blue><todo @char #char:2022-03-17>New section - review plus all subsections</todo></color>
 /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

DIDO Wiki

User Tools

Site Tools

Differences

Page Tools