CN202663444U - Cloud safety data migration model - Google Patents
Cloud safety data migration model Download PDFInfo
- Publication number
- CN202663444U CN202663444U CN 201220314858 CN201220314858U CN202663444U CN 202663444 U CN202663444 U CN 202663444U CN 201220314858 CN201220314858 CN 201220314858 CN 201220314858 U CN201220314858 U CN 201220314858U CN 202663444 U CN202663444 U CN 202663444U
- Authority
- CN
- China
- Prior art keywords
- cloud
- data
- migration
- cloud system
- tenant
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Landscapes
- Storage Device Security (AREA)
Abstract
The utility model discloses a cloud safety data migration model, which comprises cloud tenants, a third-party audit, a source cloud system and a target cloud system; the third-party audit comprises data integrity inspection function which is used for detecting the data integrity situation of the cloud tenants in the cloud system; the source cloud system comprises a metadata node and data nodes; the target cloud system comprises a metadata node and data nodes; each metadata node comprises an access control module, a migration decision module and metadata of the corresponding overall cloud system; each access control module is used for verifying whether the cloud tenants have corresponding operation authority; each migration decision module is used for generating and submitting the data migration request of the cloud tenants; each metadata node is used for managing the data of all the cloud tenants; and each data node is used for storing the actual data and backup thereof of all the cloud tenants. The model provided by the utility model overcomes the disadvantages of the existing data migration model, reduces the safety risks in data migration process, and enhances the control ability of the cloud tenants to the data migration.
Description
Technical field
The utility model relates to computer safety field, relates in particular to a kind of cloud security Data Migration model.
Background technology
The cloud Data Migration refers to data are dumped to another cloud system from a cloud system, comprises privately owned cloud to publicly-owned cloud, publicly-owned cloud to privately owned cloud, publicly-owned cloud to three kinds of scenes of publicly-owned cloud.
Privately owned cloud is modal a kind of scene to publicly-owned cloud.Such as network shopping mall such as eBay, Taobao and social networks such as Facebook, Myspace etc. in the early stage not mass data need management, therefore only need to adopt to make up privately owned cloud even traditional storage solution.Along with the expansion of business, its data volume also is exponential growth, and they begin to consider a feasible solution---and rent the memory space of publicly-owned cloud, be about to Data Migration in publicly-owned cloud.Overcome so on the one hand the defective of the privately owned cloud finite capacity of enterprise, saved on the other hand construction, the operation and maintenance expense of super data center, and by the storage security of cloud service merchant's professional safe troop service data.
Publicly-owned cloud is also very common to privately owned cloud.Suppose that certain enterprise has bought the cloud stores service of Amazon S3, along with the development of the said firm's business, find that some data becomes very secret, so they consider data are moved to from publicly-owned cloud in the privately owned cloud of enterprises.
Publicly-owned cloud is the trend of cloud computing development to publicly-owned cloud.Show the required main challenge that faces when safety is still the user and adopts cloud service from the investigation of Internet data center (IDC).Therefore, along with popularizing of cloud computing, when the user finds that the cloud stores service of oneself buying exposes security risk, they can with oneself Data Migration in the higher cloud service quotient data of safe class in the heart.Obvious characteristic of cloud stores service is the storage administration optimization to large data sets.If the user wants to upgrade to VIP user from domestic consumer, the cloud service merchant will adopt a series of measures to this user's data so, as migrate its data to and have faster access speed and more in the cloud storage system of high safety grade.Suppose that again certain enterprise has bought the cloud stores service of Amazon S3, this enterprise headquarters is in Shanghai, so Amazon Company can be deployed in the data portion of this enterprise the data center near Shanghai.Along with the development of business, this enterprise has set up office in Beijing, and in order to take into account data access speed and the service quality of Beijing office, Amazon Company needs the data center near the Pekinese is moved in the related data backup of this enterprise.
Therefore Data Migration is a critical services of cloud storage.Therefore how to guarantee the fail safe of Data Migration, all significant concerning cloud tenant and cloud service merchant.More easily data access and stores service are enjoyed in the loss that causes when on the one hand the user needn't concern of data meets with security risk; Promoted on the other hand cloud service merchant's prestige.If there is potential safety hazard in Data Migration, will cause serious consequence to cloud tenant and cloud service merchant.For example the accounts information of network shopping mall and social networks relates to individual privacy, if these information are illegally stolen or distorted, for these enterprises, will face catastrophic consequence.
Existing Data Migration model has: traditional Data Migration model, HDFS or S3 Data Migration model, improved HDFS or S3 Data Migration model.
The enforcement of traditional Data Migration model comprises two processes: 1) the cloud tenant downloads to this locality with data from the data center of cloud service merchant A; 2) the cloud tenant upload the data to the data center of cloud service merchant B from this locality.Fig. 1 is traditional Data Migration model.
The defective that traditional Data Migration model exists has: 1) data are downloaded to this locality from cloud service merchant A, need to prepare in this locality data storage device temporarily, this is unpractical to those enterprises that have mass storage data; 2) data have increased network security risk in the process of fetching with unloading, comprise that general network attack, reply attack, middle attacks etc.; 3) data have increased communicating by letter and time overhead of cloud tenant in the process of fetching with unloading; 4) concerning the cloud tenant, can not guarantee that the cloud tenant data fetches rear cloud service merchant A and whether leave backup or illegally analyze its residual data.Fig. 1 is traditional Data Migration model.
The concrete steps of HDFS or S3 Data Migration model are: 1) user A sends the Data Migration request to its stores service merchant (cloud system 1), and request comprises source data, destination, object; 2) metadata node of cloud system 1 checks whether user A possesses the Data Migration authority of its appointment; 3) metadata node of cloud system 1 sends write request to the metadata node of the cloud system 2 that comprises object, path, order ground; 4) metadata node of cloud system 2 checks whether user A possesses the authority of writing data in the write request in the specified path; 5) if inspection is passed through, when generating a write token(Data Migration, the metadata node of cloud system 2 and its back end use); 6) metadata node of cloud system 2 returns to the write token that generates the metadata node of cloud system 1; 7) metadata node of cloud system 1 is distributed to the back end that has user A data with the write token that receives; 8) back end of cloud system 1 sends data (data access request) and token to the metadata node of write token appointment; 9) can the metadata node of cloud system 2 checking token write with the specified data piece; 10) if checking is passed through, the metadata node of cloud system 2 can send target data address of node information to the source data node; 11) the source data node is write data to the destination data node.Fig. 2 is the schematic diagram of this model.
From said process, can find out to have 3 class security risks: the 1) communication security between cloud system 1 and cloud system 2 both sides' metadata node.Security protocol or token may be blocked or distort at this one-phase, and the hacker may utilize the legal side deception the opposing party of these token personations; 2) communication security of source data node and purpose metadata node.If the token that sends is blocked, the hacker has obtained the address information that should only have the source data node to learn; 3) cloud system 1 and cloud system 2 both sides' back end communication security.
Because metadata node and back end all might be palmed off by victim, therefore there are two kinds of methods to improve the fail safe of migration: the protection of entity authentication and migration data.
At first, the both sides' metadata node that relates to Data Migration all needs to carry out certain safety certification.Solve thinking: use ssl protocol to set up escape way, be used for the security parameter of transmission back such as data encryption key, MAC, random key etc., also be used for the source data node to order ground metadata node transmission ticket etc.
Secondly, the metadata node of order ground system has the right the source data node is authenticated.Authentication is not passed through, just can not be to data writing in the purpose system.
At last, send and accept both sides all will to the migration data carry out certain safety measure (particularly guaranteeing its confidentiality).Solution: data need to be encrypted with a temporary key, and ciphertext is calculated its MAC with predefined algorithm.
Be embodied in following three aspects: 1) the SSL stage.Be escape ways of two system mades, and transmit security parameters: the Data Migration ticket of interim conversation key (using when MAC calculates), random key (using during symmetric cryptography), least privilege; 2) the Data Migration ticket of least privilege.Main consideration assailant may intercept and capture namely top said token of ticket(), migration works the mischief to data.The safety of software levels can not stop the generation of this situation, but can reduce the impact that it brings.Even the assailant has intercepted and captured ticket by physical means, it is also very limited that he can do.For example, it is disposable can designing ticket, in case the ticket of back end is passed through by the authentication of the metadata node of order ground system, this ticket has just become invalid after the specified date.In case have two identical ticket request authentication in the system, show to have the assailant.At this moment, the person that need in time feed back to the migration management.Here can be used as ticket(in case an ID authentication is passed through with source ID, purpose ID, be destroyed immediately); 3) data encryption is processed.Data mode originally is " data block+hash value ", can only be for detection of the integrality of data.Present data mode " data block+hash value+MAC code (hash value and random code calculate gained) " can guarantee integrality, the confidentiality and anti-tamper of migration data.
The transition process of improved HDFS or S3 Data Migration model is as follows: 1) user A identity by authentication after, the MDM(of source HDFS migration decision-making module merges in metadata node) MDM in the metadata node of purpose HDFS sends the SSL connection request.The security parameter of after this both sides' metadata node meeting negotiate further; 2) receive the migration request of source metadata node after, the purpose metadata node generates a session key (Kdn is used for communicating by letter of source metadata node and purpose metadata node), a random number (Dhash is used for dual hash calculating).Then the purpose metadata node sends to the source metadata node with Kdh and Dhash; 3) then the source metadata node sends ticket request (IP address list that comprises DataNode) to the purpose metadata node after distributing the migration task to back end; 4) MDM of purpose metadata node generates a series of ticket, and with Kdst(only by known to the purpose metadata node) encrypt each ticket, then return tickets(tickets { IP, the Kdst{ticket(s of encrypted form to the source metadata node, ip, filepath) } }); 5) after the source metadata node receives the tickets of encryption, to each back end distribution ticket, Kdn, Dhash; 6) distribution complete after, SSL connects termination.Each tasks carrying device uses Kdn and timestamp to encrypt the ticket that each has been encrypted, and the ticket of this double-encryption is sent to the purpose metadata node; 7) the purpose metadata node is deciphered tickets, and upgrades the timestamp in each ticket, then returns the IP address information with each source data node corresponding data node; 8) after each source data node receives the IP address of destination data node, use session key (Kdn) and encrypt the data block that each will move, obtain first hash value (hash1), hash2 then calculates with Dhash.Then the source data node sends the data block (data block+hash1+hash2) of double-encryption form to the destination data node.Fig. 3 is the schematic diagram of this model.
Improved HDFS or S3 Data Migration model can guarantee integrality and the confidentiality in the data migration process, but Shortcomings still, be embodied in: 1) the cloud tenant data is after the migration of source cloud system, whether have data backup or data remanence, whether the cloud service merchant exists the possibility of illegal analysis user data; 2) source, purpose cloud system are lacked supervision mechanism, in case the safe dispute of Data Migration occurs, the situation that causes easily the cloud service merchant to shirk responsibility mutually, the cloud tenant can't determine it is the mistake of which side.For example, after the cloud tenant data was moved to cloud system B safely from cloud system A, cloud system A can delete metadata and all data backups of this cloud tenant migration data.For a certain reason, user data is illegally deleted or is distorted after arriving cloud system B, and cloud service this moment merchant B is in order to keep the business reputation of oneself, says to move after data are illegally deleted or revised in cloud system A and comes just can insist.In this case, it is the responsibility of which side on earth that the cloud tenant can't know for sure, is the mistake of cloud service merchant B even if the cloud tenant knows, also can't safeguard the rights and interests of oneself, because the cloud tenant cannot take out reliable evidence.3) do not support dynamic data to upgrade operation, the data during for example modification or deletion move, the user could operate migration data after can only or moving before migration and finishing, and using to the user makes troubles.
The utility model content
The purpose of this utility model provides a kind of cloud security Data Migration model, to reduce the security risk in the data migration process.
The utility model is that the technical scheme that its technical problem of solution adopts is,
A kind of cloud security Data Migration model comprises:
Cloud tenant, third party's audit, source cloud system, purpose cloud system;
Third party's audit, it comprises the data integrity check function, is used for check cloud system medium cloud tenant's data integrity situation;
The source cloud system, it comprises metadata node, back end;
The purpose cloud system, it comprises metadata node, back end;
Metadata node, it comprises the metadata of access control module, migration decision-making module, whole cloud system;
Access control module is used for checking cloud tenant and whether possesses corresponding operating right;
The migration decision-making module is used for generating and submission cloud tenant data migration request;
Metadata node is used for all cloud tenants' of management data;
Back end is used for depositing all cloud tenants' real data and backup thereof.
The cloud tenant is the entity of having bought source cloud service merchant and purpose cloud service merchant's stores service, possesses to read and write data in the cloud system of source and to the authority of purpose cloud system migration data.
The source cloud system is the entity that cloud storage and cloud security service are provided for the cloud tenant, when the cloud tenant proposes the Data Migration requirement, the source cloud system can dump to the cloud tenant data in the purpose cloud system of its appointment safely, in addition, can accept the safety supervision of third party's audit.
The purpose cloud system is the entity that cloud storage and cloud security service are provided for the cloud tenant, and when the cloud tenant proposed the Data Migration requirement, the purpose cloud system can receive the data from the source cloud system of cloud tenant appointment, in addition, can accept the safety supervision of third party's audit.
The third party audits and can check that the cloud tenant is arranged in the entity of the integrality of cloud system data, when the cloud tenant proposes the Data Migration requirement, can moving into and moving and finish the opisthogenesis cloud system metadata of migration data and the fully deletion of data backup thereof are carried out security audit the moving out of source cloud system data, purpose cloud system data, in addition, fully transparent to the cloud tenant data in audit process, namely can't analyze the real information of Audit data.
Third party's audit can be processed the Data Migration audit task that a plurality of cloud tenants submit to simultaneously, namely criticizes audit.
Similar real-life notarization and supervisory organ are trusted in third party's audit by cloud tenant and cloud service merchant both sides.The third party audits and satisfies three requirements: 1) can carry out integrity check to cloud system medium cloud tenant's data in the situation of needs local backup not; 2) in integrity verification process, fully transparent to the cloud tenant data, namely can't analyze the real information of Audit data; 3) supported data dynamically updates, and the cloud tenant can upgrade at any time to the related data in the cloud system, such as increase, modification and deletion etc.; 4) the Data Migration audit that can process simultaneously a plurality of cloud tenants is asked.
The cloud tenant can audit to the third party first and submit the request of migration security audit to before migration data, and request content comprises source cloud system, purpose cloud system and the data that will audit.The third party's data that can will audit to the cloud tenant of auditing are done a comprehensively data integrity inspection, and audit report is attached to sends to the cloud tenant in the auditing notice.After receiving the auditing notice that the third party audits, the cloud tenant has had clearly understanding to the integrality of the data of oneself, if exceeded cloud tenant's the scope of accepting, the cloud tenant can negotiate the agreement of reaching an agreement with source cloud service merchant.Subsequently cloud tenant Xiang Yuan cloud service merchant submits the Data Migration request to, and the source cloud system is after the identity and authority of confirming the cloud tenant, and beginning is sent request to purpose cloud system and third party's audit.Why sending migration request by the source cloud system to third party's audit, mainly is in order to stop the source cloud system in the purpose cloud system of moving to cloud tenant appointment, the cloud tenant data to be migrated into certain " in confidence ", as illegally analyze in the future.Third party's migration request that security audit request that contrast cloud tenant submits to and source cloud system are submitted to of auditing if the purpose cloud system of appointment is consistent in two requests, then show safety, otherwise there is security risk in explanation, should report this situation to the cloud tenant at once.After a series of authentications by the purpose cloud system, the source cloud system is formally to purpose cloud system migration data, and meanwhile third party's audit also begins the integrality of whole transition process data is checked.Here, the function of third party's audit comprises: 1) moving out of source cloud system data audited; 2) moving into of purpose cloud system data audited; 3) metadata of source cloud system migration data and the safety deleting of data backup are audited; 4) data integrity of moving in the purpose cloud system is audited.At last, after Data Migration finished, source cloud system and purpose cloud system can submit to Data Migration to finish report to the cloud tenant, and third party's audit also can be submitted the migration Audit Report to the cloud tenant.The cloud tenant will move Audit Report as source, and the report that contrast source, purpose cloud system are submitted to if content is consistent, shows Data Migration safety, otherwise the cloud tenant can be as the rights and interests according to maintenance oneself.At last, the cloud tenant can continue to entrust the third party to audit the migration data in the purpose cloud system is carried out the integrality supervision.
The advantage of this cloud security Data Migration model is:
1) overcome traditional Data Migration model defectiveness, the cloud tenant uploads to the purpose cloud system after needn't in person downloading migration data again;
2) all security risks in HDFS or the S3 Data Migration model transition process have been eliminated;
3) overcome improved HDFS or S3 Data Migration model source, purpose cloud system are lacked the defective of supervision, in case the safe dispute of Data Migration occurs, third party's audit can very fast definite causes of incident, and the strong evidence of safeguarding self rights and interests is provided for the cloud tenant;
4) overcome existing three kinds of models and can't solve the defective of the data security dispute between user and cloud system;
5) having overcome existing three kinds of models can't the specified data migration finish the opisthogenesis cloud system and whether deletes the metadata of migration data and the deficiency of all data backups thereof fully;
6) solved that source cloud system in existing three kinds of models is may be in transition process secret transfers to somewhere problem with the cloud tenant data, namely portion is the purpose cloud system of moving to cloud tenant appointment, and another part be certain place that the source cloud system plans sth. ahead;
7) overcome existing three kinds of models and can't dynamically update the defective of migration data data migration process medium cloud tenant, namely transition process medium cloud tenant does not possess access rights to migration data;
8) overcome existing three kinds of Data Migration models and behind the purpose cloud system, lacked the deficiency that follow-up integrality is supervised at safe migration of data;
9) overcome existing three kinds of model medium cloud tenants to the complete transparent defective of data transition process, third party's audit has strengthened the control of cloud tenant to the data migration for the complete report that the cloud tenant provides Data Migration;
10) third party's audit can be processed a plurality of Data Migration requests simultaneously, namely criticize audit, not only saved cloud tenant's time, man power and material's expense, and saved social resources, the idea of development that meets cloud computing, significant for further enlarging the cloud large-scale production.
Description of drawings
Fig. 1 is traditional Data Migration model structure schematic diagram;
Fig. 2 is the Data Migration model structure schematic diagram of HDFS or S3;
Fig. 3 is the Data Migration model structure schematic diagram of improved HDFS or S3;
Fig. 4 is the structural representation of the cloud security Data Migration model that the utility model proposes.
Embodiment
For technological means, creation characteristic that the utility model is realized, reach purpose with effect is easy to understand, below in conjunction with illustrating and specific embodiment, further set forth the utility model.
With reference to figure 3, Fig. 4, the cloud security Data Migration model that the utility model proposes comprises cloud tenant, third party's audit, source cloud system, purpose cloud system; Third party's audit comprises the data integrity check function, is used for check cloud system medium cloud tenant's data integrity situation; The source cloud system comprises metadata node, back end; The purpose cloud system comprises metadata node, back end; Metadata node comprises the metadata of access control module, migration decision-making module, whole cloud system; Access control module is used for checking cloud tenant and whether possesses corresponding operating right; The migration decision-making module is used for generating and submission cloud tenant data migration request; Metadata node is used for all cloud tenants' of management data; Back end is used for depositing all cloud tenants' real data and backup thereof.
According to this cloud security Data Migration model, the detailed process of Data Migration is as follows under the cloud environment:
1. the cloud tenant audits to the third party and submits migration security audit request (comprising source cloud system, purpose cloud system) to;
2. third party's examination of auditor is arranged in the integrality of source cloud system migration data, generates the front data integrity report of migration, returns to the cloud tenant;
3. after the cloud tenant checks report, if all normally then send Data Migration request (comprising the data that will move, purpose cloud system, third party's audit etc.) to the source cloud system;
4. the source cloud system sends migration request to purpose cloud system and third party's audit;
5. the purpose cloud system in the migration request is obtained in third party's audit, and the purpose cloud system of the appointment in the migration security audit request that itself and cloud tenant are submitted to is compared, if both are inconsistent, show that then there is the secret behavior of shifting the cloud tenant data in the source cloud system, the third party audited and need in time report this situation to the cloud tenant this moment; Otherwise the third party audits and formally source cloud system and purpose cloud system is carried out the safety transfer audit;
6. behind the License Info of receiving the purpose cloud system, the source cloud system begins to purpose cloud system migration data (data migration process is by improved HDFS or S3 Data Migration model);
7. Data Migration is complete, and the purpose cloud system sends the complete information of data receiver (comprising time started, concluding time, data volume, source cloud system etc.) to cloud tenant and source cloud system;
8. the source cloud system is after the complete information of the data receiver of receiving the purpose cloud system, beginning safety deleting cloud tenant's migration data, and send the complete information of Data Migration (comprising time started, concluding time, data volume, purpose cloud system, migration data deletion information etc.) to the cloud tenant;
9. third party's audit sends migration Audit Report (comprising source cloud system, purpose cloud system, time started, concluding time, data volume, source cloud system migration data deletion information etc.) to the cloud tenant;
10. if the cloud tenant consistent, then shows Data Migration safety with the information of source cloud system and the submission of purpose cloud system and the auditing result contrast of third party's audit, otherwise, illustrate to have the behavior of cheating the cloud tenant.
11. the cloud tenant can continue to entrust the third party to audit the migration data in the purpose cloud system is carried out the integrality supervision.
More than show and described basic principle of the present utility model, principal character and advantage of the present utility model.The technical staff of the industry should understand; the utility model is not restricted to the described embodiments; that describes in above-described embodiment and the specification just illustrates principle of the present utility model; the utility model also has various changes and modifications under the prerequisite that does not break away from the utility model spirit and scope, and these changes and improvements all fall in claimed the utility model scope.The claimed scope of the utility model is defined by appending claims and equivalent thereof.
Claims (6)
1. a cloud security Data Migration model is characterized in that, comprising:
Cloud tenant, third party's audit, source cloud system, purpose cloud system;
Third party's audit, it comprises the data integrity check function, is used for check cloud system medium cloud tenant's data integrity situation;
The source cloud system, it comprises metadata node, back end;
The purpose cloud system, it comprises metadata node, back end;
Metadata node, it comprises the metadata of access control module, migration decision-making module, whole cloud system;
Access control module is used for checking cloud tenant and whether possesses corresponding operating right;
The migration decision-making module is used for generating and submission cloud tenant data migration request;
Metadata node is used for all cloud tenants' of management data;
Back end is used for depositing all cloud tenants' real data and backup thereof.
2. a kind of cloud security Data Migration model as claimed in claim 1, it is characterized in that, the cloud tenant is the entity of having bought source cloud service merchant and purpose cloud service merchant's stores service, possesses to read and write data in the cloud system of source and to the authority of purpose cloud system migration data.
3. a kind of cloud security Data Migration model as claimed in claim 1, it is characterized in that, the source cloud system is the entity that cloud storage and cloud security service are provided for the cloud tenant, when the cloud tenant proposes the Data Migration requirement, the source cloud system can dump to the cloud tenant data in the purpose cloud system of its appointment safely, in addition, can accept the safety supervision of third party's audit.
4. a kind of cloud security Data Migration model as claimed in claim 1, it is characterized in that, the purpose cloud system is the entity that cloud storage and cloud security service are provided for the cloud tenant, when the cloud tenant proposes the Data Migration requirement, the purpose cloud system can receive the data from the source cloud system of cloud tenant appointment, in addition, can accept the safety supervision of third party's audit.
5. a kind of cloud security Data Migration model as claimed in claim 1, it is characterized in that, the third party audits and can check that the cloud tenant is arranged in the entity of the integrality of cloud system data, when the cloud tenant proposes the Data Migration requirement, can moving into and moving and finish the opisthogenesis cloud system metadata of migration data and the fully deletion of data backup thereof are carried out security audit the moving out of source cloud system data, purpose cloud system data, in addition, fully transparent to the cloud tenant data in audit process, namely can't analyze the real information of Audit data.
6. a kind of cloud security Data Migration model as claimed in claim 1 is characterized in that, third party's audit can be processed the Data Migration audit task that a plurality of cloud tenants submit to simultaneously, namely criticizes audit.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201220314858 CN202663444U (en) | 2012-06-29 | 2012-06-29 | Cloud safety data migration model |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201220314858 CN202663444U (en) | 2012-06-29 | 2012-06-29 | Cloud safety data migration model |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN202663444U true CN202663444U (en) | 2013-01-09 |
Family
ID=47458317
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201220314858 Expired - Fee Related CN202663444U (en) | 2012-06-29 | 2012-06-29 | Cloud safety data migration model |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN202663444U (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103699851A (en) * | 2013-11-22 | 2014-04-02 | 杭州师范大学 | Remote data completeness verification method facing cloud storage |
| CN104052775A (en) * | 2013-03-14 | 2014-09-17 | 腾讯科技（深圳）有限公司 | Authority management method of cloud platform service, device and system |
| WO2015000105A1 (en) * | 2013-07-01 | 2015-01-08 | Empire Technology Development Llc | Data migration in a storage network |
| CN104426952A (en) * | 2013-08-28 | 2015-03-18 | 华为技术有限公司 | Data migration method, device and system |
| CN105721515A (en) * | 2014-12-02 | 2016-06-29 | 鸿富锦精密工业（深圳）有限公司 | Cloud agent device, cloud storage and file transfer method |
| CN106101216A (en) * | 2016-06-08 | 2016-11-09 | 北京工业大学 | Based on the safe migration of data method separating logic |
| CN107277162A (en) * | 2017-07-20 | 2017-10-20 | 成都超域物联科技有限公司 | A kind of intelligent household management system and method based on network cloud |
| CN107995147A (en) * | 2016-10-27 | 2018-05-04 | 中国电信股份有限公司 | Metadata encryption and decryption method and system based on distributed file system |
| CN108197496A (en) * | 2018-01-18 | 2018-06-22 | 成都博睿德科技有限公司 | Data safety Enhancement Method under cloud computing environment |
| CN114398005A (en) * | 2021-12-22 | 2022-04-26 | 上海金仕达软件科技有限公司 | Data secure migration method and device and storage medium |
-
2012
- 2012-06-29 CN CN 201220314858 patent/CN202663444U/en not_active Expired - Fee Related
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104052775A (en) * | 2013-03-14 | 2014-09-17 | 腾讯科技（深圳）有限公司 | Authority management method of cloud platform service, device and system |
| WO2014139298A1 (en) * | 2013-03-14 | 2014-09-18 | Tencent Technology (Shenzhen) Company Limited | Permission management method, device and system for cloud platform service |
| CN104052775B (en) * | 2013-03-14 | 2016-11-23 | 腾讯科技（深圳）有限公司 | Right management method, device and the system of a kind of cloud platform service |
| US20150373026A1 (en) * | 2013-03-14 | 2015-12-24 | Tencent Technology (Shenzhen) Company Limited | Permission management method, device and system for cloud platform service |
| US9444891B2 (en) | 2013-07-01 | 2016-09-13 | Emoire Technology Development LLC | Data migration in a storage network |
| WO2015000105A1 (en) * | 2013-07-01 | 2015-01-08 | Empire Technology Development Llc | Data migration in a storage network |
| CN104426952A (en) * | 2013-08-28 | 2015-03-18 | 华为技术有限公司 | Data migration method, device and system |
| CN103699851B (en) * | 2013-11-22 | 2016-05-25 | 杭州师范大学 | A kind of teledata integrity verification method of facing cloud storage |
| CN103699851A (en) * | 2013-11-22 | 2014-04-02 | 杭州师范大学 | Remote data completeness verification method facing cloud storage |
| CN105721515A (en) * | 2014-12-02 | 2016-06-29 | 鸿富锦精密工业（深圳）有限公司 | Cloud agent device, cloud storage and file transfer method |
| CN105721515B (en) * | 2014-12-02 | 2019-06-07 | 鸿富锦精密工业（深圳）有限公司 | The method of cloud agent equipment, cloud disk and archives transfer |
| CN106101216A (en) * | 2016-06-08 | 2016-11-09 | 北京工业大学 | Based on the safe migration of data method separating logic |
| CN107995147A (en) * | 2016-10-27 | 2018-05-04 | 中国电信股份有限公司 | Metadata encryption and decryption method and system based on distributed file system |
| CN107277162A (en) * | 2017-07-20 | 2017-10-20 | 成都超域物联科技有限公司 | A kind of intelligent household management system and method based on network cloud |
| CN107277162B (en) * | 2017-07-20 | 2021-03-30 | 成都超域物联科技有限公司 | Intelligent home management system and method based on network cloud |
| CN108197496A (en) * | 2018-01-18 | 2018-06-22 | 成都博睿德科技有限公司 | Data safety Enhancement Method under cloud computing environment |
| CN114398005A (en) * | 2021-12-22 | 2022-04-26 | 上海金仕达软件科技有限公司 | Data secure migration method and device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN202663444U (en) | Cloud safety data migration model | |
| US11689366B2 (en) | Cryptoasset custodial system with vault-specific rules governing different actions allowed for different vaults | |
| US11757627B2 (en) | Cryptoasset custodial system with proof-of-stake blockchain support | |
| CN109508552B (en) | Privacy protection method of distributed cloud storage system | |
| CN109829326B (en) | Cross-domain authentication and fair audit de-duplication cloud storage system based on block chain | |
| Yavari et al. | An improved blockchain-based authentication protocol for IoT network management | |
| CN102170440B (en) | Method suitable for safely migrating data between storage clouds | |
| CN110032545A (en) | File memory method, system and electronic equipment based on block chain | |
| CN109409122A (en) | File memory method and its electronic equipment, storage medium | |
| CN114631286B (en) | Encrypted asset hosting system with custom logic | |
| CN109472164A (en) | The verification method and its network and electronic equipment of contract dataset | |
| US20160294794A1 (en) | Security System For Data Communications Including Key Management And Privacy | |
| CN107579958A (en) | Data managing method, apparatus and system | |
| Yao et al. | PBCert: Privacy-preserving blockchain-based certificate status validation toward mass storage management | |
| US11405198B2 (en) | System and method for storing and managing keys for signing transactions using key of cluster managed in trusted execution environment | |
| CN109491965A (en) | The storage method and its network and electronic equipment of purchase sale of electricity contract | |
| CN109951490A (en) | Webpage integrity assurance, system and electronic equipment based on block chain | |
| KR102627868B1 (en) | Method and system for authenticating data generated in blockchain | |
| WO2019125521A1 (en) | Re-encrypting data on a hash chain | |
| Wu et al. | Blockchain-based data audit mechanism for integrity over big data environments | |
| Zakir et al. | Improving data security in message communication between ACT and aircraft using private Blockchain | |
| Purchina et al. | Securing an Information System via the SSL Protocol. | |
| CN117097526A (en) | Block chain-based data security sharing method and device | |
| CN109816525A (en) | A kind of data processing method and its device, medium, terminal | |
| CN111769956B (en) | Service processing method, device, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130109 Termination date: 20130629 |