dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_in_motion
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_in_motion [2022/03/17 17:37] char [Discussion] |
dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_in_motion [2022/05/27 19:57] (current) nick |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 2.3.4.2.2 Data-In-Motion ====== | + | ====== 2.3.4.2.2 Data-in-Motion ====== |
| [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:start| Return to State of Data Taxonomy]] | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:start| Return to State of Data Taxonomy]] | ||
| Line 16: | Line 16: | ||
| Once the data arrives at its final destination, it is classified as [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_at_rest| Data-at-Rest]]. | Once the data arrives at its final destination, it is classified as [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_at_rest| Data-at-Rest]]. | ||
| - | Because Data-in-Motion is vulnerable to [[dido:public:ra:xapend:xapend.a_glossary:m:mitm]] attacks, it is often [[dido:public:ra:xapend:xapend.a_glossary:e:encryption | Encrypted]] to prevent interception. For example, the [[dido:public:ra:xapend:xapend.a_glossary:i:iscsi| Internet Small Computer System Interface (iSCSI)]] transport layer incorporates [[dido:public:ra:xapend:xapend.a_glossary:i:ipsec]], which can [[dido:public:ra:xapend:xapend.a_glossary:e:encryption | encrypt]] data as it is transferred between two devices to prevent a hacker with a sniffer from seeing the contents of that data. IPSec has been used extensively as a transit encryption protocol for [[dido:public:ra:xapend:xapend.a_glossary:v:vpn]] tunnels because it makes use of [[dido:public:ra:xapend:xapend.a_glossary:c:cryptographic_algorithm | Cryptography Algorithms]] such as Triple DES (3DES) and [[dido:public:ra:xapend:xapend.b_stds:tech:nist:sp_800-34e | Advanced Encryption Standard (AES)]]. Encryption [[dido:public:ra:xapend:xapend.a_glossary:p:platform]] software can also be integrated with existing [[dido:public:ra:xapend:xapend.a_glossary:e:erp]] systems to keep Data-in-Motion secure. | + | Because Data-in-Motion is vulnerable to [[dido:public:ra:xapend:xapend.a_glossary:m:mitm]] attacks, it is often [[dido:public:ra:xapend:xapend.a_glossary:e:encryption | Encrypted]] to prevent interception. For example, the [[dido:public:ra:xapend:xapend.a_glossary:i:iscsi| Internet Small Computer System Interface (iSCSI)]] transport layer incorporates [[dido:public:ra:xapend:xapend.a_glossary:i:ipsec]], which can [[dido:public:ra:xapend:xapend.a_glossary:e:encryption | encrypt]] data as it is transferred between two devices to prevent a [[dido:public:ra:xapend:xapend.a_glossary:h:hacker]] with a sniffer from seeing the contents of that data. IPSec has been used extensively as a transit encryption protocol for [[dido:public:ra:xapend:xapend.a_glossary:v:vpn]] tunnels because it makes use of [[dido:public:ra:xapend:xapend.a_glossary:c:cryptographic_algorithm | Cryptography Algorithms]] such as Triple DES (3DES) and [[dido:public:ra:xapend:xapend.b_stds:tech:nist:sp_800-34e | Advanced Encryption Standard (AES)]]. Encryption [[dido:public:ra:xapend:xapend.a_glossary:p:platform]] software can also be integrated with existing [[dido:public:ra:xapend:xapend.a_glossary:e:erp]] systems to keep Data-in-Motion secure. |
| ===== DIDO Specifics ===== | ===== DIDO Specifics ===== | ||
| Line 101: | Line 101: | ||
| </WRAP>| | </WRAP>| | ||
| ^ Network | <WRAP> | ^ Network | <WRAP> | ||
| - | The **Network Level** is analogous to the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:s:sessionlayer]] providing data routing paths for network communication. Data is transferred in the form of packets via logical network paths in an ordered format controlled by the network layer. Logical connection setup, data forwarding, routing and delivery error reporting are the Network Layer’s primary responsibilities. | + | The **Network Level** is analogous to the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:s:sessionlayer]] providing data routing paths for network communication. Data is transferred in the form of packets via logical network paths in an ordered format controlled by the network layer. Logical connection setup, data forwarding, routing, and delivery error reporting are the Network Layer’s primary responsibilities. |
| This layer includes: | This layer includes: | ||
| Line 141: | Line 141: | ||
| </figure> | </figure> | ||
| - | Most of the **DIDO Platforms**, in combination with the **Frameworks** and **Application Layer**, provide a [[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:reuseability | Reusable]], general mechanism for [[dido:public:ra:xapend:xapend.a_glossary:d:dapp | Dapps]] to interact with oither DIDO [[dido:public:ra:xapend:xapend.a_glossary:n:node | Nodes]] in a [[dido:public:ra:xapend:xapend.a_glossary:n:node_network]]. However, this combination of **Platforms**, **Frameworks**, and **Applications** create **DIDO [[dido:public:ra:xapend:xapend.a_glossary:s:silo | Silos]]** creating isolation and offering little to no [[dido:public:ra:xapend:xapend.a_glossary:i:interoperability]] between the silos inhibiting [[dido:public:ra:xapend:xapend.a_glossary:i:interoperability]]. | + | Most of the **DIDO Platforms**, in combination with the **Frameworks** and **Application Layer**, provide a [[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:reuseability | Reusable]], general mechanism for [[dido:public:ra:xapend:xapend.a_glossary:d:dapp | Dapps]] to interact with oither DIDO [[dido:public:ra:xapend:xapend.a_glossary:n:node | Nodes]] in a [[dido:public:ra:xapend:xapend.a_glossary:n:node_network]]. However, this combination of **Platforms**, **Frameworks**, and **Applications** create **DIDO [[dido:public:ra:xapend:xapend.a_glossary:s:silo | Silos]]** thereby inhibiting [[dido:public:ra:xapend:xapend.a_glossary:i:interoperability]] between the silos. |
| - | [[dido:public:ra:xapend:xapend.a_glossary:b:bridge | Bridges]] can be built between the Silos. However, the existing DIDO Platforms have no incentive to design or implement **Bridges**, in fact, they have a deinsentive as the purveyor of competitive DIDO Platforms. Many of the DIDO Platform [[dido:public:ra:xapend:xapend.a_glossary:a:api | Application Programming Interfaces (APIs)]] are poorly documented and hide behind a curtain of [[dido:public:ra:xapend:xapend.a_glossary:o:oss]] as standards. | + | [[dido:public:ra:xapend:xapend.a_glossary:b:bridge | Bridges]] can be built between the Silos. However, existing DIDO Platforms have no incentive to design or implement **Bridges**. In fact, as the purveyor of competitive DIDO Platforms, they have a distinct disincentive. Many of the DIDO Platform [[dido:public:ra:xapend:xapend.a_glossary:a:api | Application Programming Interfaces (APIs)]] are also poorly documented and hide behind a curtain of [[dido:public:ra:xapend:xapend.a_glossary:o:oss]] as standards. |
| - | The Interoperability issues between the various platforms silos csan be traced to the lowest level of the DIDO Platform, or depending on the perspective, the upper level of the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:p:presentlayer]]. For example, the selection of a **Framework** narrows the Interoperability options to those DIDO Platforms that have selected the same **Framework**. The same can be said of the messaging systems defined in **''Transport --> Message Transport Level''**. Messages are at the core of DIDO Platforms. | + | The Interoperability issues between the various platforms silos can be traced to the lowest level of the DIDO Platform, or depending on the perspective, the upper level of the [[dido:public:ra:xapend:xapend.a_glossary:o:osi]] [[dido:public:ra:xapend:xapend.a_glossary:p:presentlayer]]. For example, the selection of a **Framework** narrows the Interoperability options to those DIDO Platforms that have selected the same **Framework**. The same can be said of the messaging systems defined in **''Transport --> Message Transport Level''**. Messages are at the core of DIDO Platforms. |
| + | |||
| + | <color blue><todo @char #char:2022-03-17>New section - review </todo></color> | ||
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
dido/public/ra/1.2_views/3_taxonomic/4_data_tax/02_state_taxonomy/data_in_motion.1647553044.txt.gz · Last modified: 2022/03/17 17:37 by char
