dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_at_rest
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_at_rest [2022/03/15 17:52] char |
dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_at_rest [2022/05/27 19:56] (current) nick |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 2.3.4.2.1 Data-At-Rest ====== | + | ====== 2.3.4.2.1 Data-at-Rest ====== |
| [[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 5: | Line 5: | ||
| [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_at_rest| Return to Top]] | [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_at_rest| Return to Top]] | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary:d:dataatrest]] refers to all data in computer storage. It excludes data while it is moving across or within a network and it excludes data that is temporarily residing in computer memory. Data-at-Rest refers to data that is actively being accessed within the computer storage, data that is archived (i.e., backups), or reference data that change rarely or never. | + | [[dido:public:ra:xapend:xapend.a_glossary:d:dataatrest]] refers to all data in computer storage. It excludes data while it is moving across or within a network and it excludes data that is temporarily residing in computer memory. **Data-at-Rest** refers to data that is actively being accessed within the computer storage, data that is archived (i.e., backups), or reference data that change rarely or never. |
| Here are some specific, traditional examples of Data-at-Rest: | Here are some specific, traditional examples of Data-at-Rest: | ||
| Line 29: | Line 29: | ||
| Within [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum]], data at rest is labeled [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum_storage | Storage]] within [[dido:public:ra:xapend:xapend.a_glossary:s:solidity]] and represents two 32 byte values. One represents the [[dido:public:ra:xapend:xapend.a_glossary:k:key]] for the Storage, while the other represents the data value associated with the **key**. As a general rule, the **key** value is an address within the Node Network. | Within [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum]], data at rest is labeled [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum_storage | Storage]] within [[dido:public:ra:xapend:xapend.a_glossary:s:solidity]] and represents two 32 byte values. One represents the [[dido:public:ra:xapend:xapend.a_glossary:k:key]] for the Storage, while the other represents the data value associated with the **key**. As a general rule, the **key** value is an address within the Node Network. | ||
| - | Within a DIDO, **Data-At-Rest** is generally physically available to anyone having access to the **Node**. Depending on the [[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:start| Network Access Control]], the risk can vary. In a [[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:private | Private Network]] there is obviously less risk than there is a [[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:public | Public Network]], however, this depends on the [[dido:public:ra:1.4_req:2_nonfunc:25_security | Securability ]] of every [[dido:public:ra:xapend:xapend.a_glossary:n:node]] in the [[dido:public:ra:xapend:xapend.a_glossary:n:node_network]]. | + | Within a DIDO, **Data-At-Rest** is generally physically available to anyone having access to the **Node**. Depending on the [[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:start| Network Access Control]], the risk can vary. In a [[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:private | Private Network]] there is obviously less risk than there is in a [[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:public | Public Network]]; however, this depends on the [[dido:public:ra:1.4_req:2_nonfunc:25_security | Securability ]] of every [[dido:public:ra:xapend:xapend.a_glossary:n:node]] in the [[dido:public:ra:xapend:xapend.a_glossary:n:node_network]]. |
| It is best to assume there is | It is best to assume there is | ||
| - | * No **[[dido:public:ra:xapend:xapend.a_glossary:p:physicalsecurity | Physical Security]]** - Unless the DIDO is completely locked down with a few well physically fortified **Nodes**, there is no **Physical Security**. If they are locked down, how distributed is the system? | + | * No **[[dido:public:ra:xapend:xapend.a_glossary:p:physicalsecurity | Physical Security]]**: Unless the DIDO is completely locked down with a few well physically fortified **Nodes**, there is no **Physical Security**. If they are locked down, how distributed is the system? |
| - | * No **[[dido:public:ra:xapend:xapend.a_glossary:p:platformsecurity | Platform Security]]** - DIDOs are all about the data and if anyone gains access to the machines there is no **Platform** security other than the encryption of the data. No matter what is done on the **platform**, the data can be accessed by other platforms that may be compromised. | + | * No **[[dido:public:ra:xapend:xapend.a_glossary:p:platformsecurity | Platform Security]]**: DIDOs are all about the data and if anyone gains access to the machines there is no **Platform** security other than the encryption of the data. No matter what is done on the **platform**, the data can be accessed by other platforms that may be compromised. |
| - | * No **[[dido:public:ra:xapend:xapend.a_glossary:a:applicationsecurity | Application Security]]** - DIDOs are all about the data and if anyone gains access to the machines there is no **Application** security other than the encryption of the data. No matter what is within the **application**, the data can be accessed by other platforms that may be compromised. | + | * No **[[dido:public:ra:xapend:xapend.a_glossary:a:applicationsecurity | Application Security]]**: DIDOs are all about the data and if anyone gains access to the machines there is no **Application** security other than the encryption of the data. No matter what is within the **application**, the data can be accessed by other platforms that may be compromised. |
| - | * No **[[dido:public:ra:xapend:xapend.a_glossary:c:securityculture | Culture Security]]** - Unless a DIDO is **[[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:permissioned | Permissioned]]** and **[[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:private| Private]]** network, there is no way to rely on cultural security. | + | * No **[[dido:public:ra:xapend:xapend.a_glossary:c:securityculture | Culture Security]]**: Unless a DIDO is **[[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:permissioned | Permissioned]]** and **[[dido:public:ra:1.2_views:3_taxonomic:2_network_access_ctrll:private| Private]]** network, there is no way to rely on cultural security. |
| - | [[dido:public:ra:xapend:xapend.a_glossary:c:cryptocurrency | Cryptocurrencies]], when viewed as a surrogate for DIDOs in general, have had a fair share of suspicion from governments including: India, China, the US, and Europe(( | + | [[dido:public:ra:xapend:xapend.a_glossary:c:cryptocurrency | Cryptocurrencies]], when viewed as a surrogate for DIDOs in general, have been regarded with a fair level of suspicion by governments including: India, China, the US, and Europe(( |
| Madana Prathap, | Madana Prathap, | ||
| Business Insider India, | Business Insider India, | ||
| Line 46: | Line 46: | ||
| )). | )). | ||
| - | : //Until a few years ago, Bitcoin was touted as the underground currency that even the world’s leading intelligence agencies won’t be able to track — but that may not really be the case. Examples from as far back as 2015, when the creator of the Bitcoin market called the ‘Silk Road’ was sentenced to life in prison for facilitating the sale of $1 billion in illegal drugs, show otherwise. Investigators can still follow the money. Even the most private of cryptocurrencies like Monero, DASH, and Verge are traceable to a certain degree. This is because of the very nature of blockchain. Every single transaction is recorded and kept on a ledger — and that ledger is accessible to everyone.// | + | : //Until a few years ago, Bitcoin was touted as the underground currency that even the world’s leading intelligence agencies would be unable to track — but that may not really be the case. Examples from as far back as 2015, when the creator of the Bitcoin market called the ‘Silk Road’ was sentenced to life in prison for facilitating the sale of $1 billion in illegal drugs, demonstrate otherwise. Investigators can still follow the money. Even the most private of cryptocurrencies like Monero, DASH, and Verge are traceable to a certain degree. This is because of the very nature of blockchain. Every single transaction is recorded and kept on a ledger — and that ledger is accessible to everyone.// |
| - | As evidence of the non-anonymous nature of Cryptocurrencies, the United States just filed a Civil Action suite to return $150M in embezzled funds from Sony by tracking money to Bitcoin(( | + | As evidence of the non-anonymous nature of Cryptocurrencies, the United States just filed a Civil Action suit to return $150M in embezzled funds from Sony by tracking money to Bitcoin(( |
| United States Department of Justice, | United States Department of Justice, | ||
| U.S. Attorney's Office, | U.S. Attorney's Office, | ||
| Line 58: | Line 58: | ||
| )). | )). | ||
| - | : //The United States took action in federal court today to protect and ultimately return more than $154 million in funds that were allegedly stolen from a subsidiary of Tokyo-based Sony Group Corporation and then seized by law enforcement during the FBI’s investigation of the theft. The United States filed a civil forfeiture complaint in the Southern District of California to protect Sony’s interest in the property, which an employee allegedly embezzled in May 2021 and converted to more than 3,879 Bitcoins valued today at more than $180 million. Those funds were seized by law enforcement on December 1, 2021, based on the FBI’s investigation. According to the government’s complaint, Rei Ishii, an employee of Sony Life Insurance Company Ltd. (“Sony Life”) in Tokyo, allegedly diverted the $154 million when the company attempted to transfer funds between its financial accounts. Ishii allegedly did this by falsifying transaction instructions, which caused the funds to be transferred to an account that Ishii controlled at a bank in La Jolla, California. Ishii then quickly converted the funds to Bitcoin cryptocurrency, the complaint said.// | + | : //The United States took action in federal court today to protect and ultimately return more than \$154 million in funds that were allegedly stolen from a subsidiary of Tokyo-based Sony Group Corporation and then seized by law enforcement during the FBI’s investigation of the theft. The United States filed a civil forfeiture complaint in the Southern District of California to protect Sony’s interest in the property, which an employee allegedly embezzled in May 2021 and converted to more than 3,879 Bitcoins valued today at more than \$180 million. Those funds were seized by law enforcement on December 1, 2021, based on the FBI’s investigation. According to the government’s complaint, Rei Ishii, an employee of Sony Life Insurance Company Ltd. (“Sony Life”) in Tokyo, allegedly diverted the \$154 million when the company attempted to transfer funds between its financial accounts. Ishii allegedly did this by falsifying transaction instructions, which caused the funds to be transferred to an account that Ishii controlled at a bank in La Jolla, California. Ishii then quickly converted the funds to Bitcoin cryptocurrency, the complaint said.// |
| + | |||
| + | <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_at_rest.1647381135.txt.gz · Last modified: 2022/03/15 17:52 by char
