cloud computing preservity


Published on

cloud computing preservity........

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

cloud computing preservity

  1. 1. Preserving Integrity through Cloud Computing…………. ................
  2. 2.  Cloud computing is the long dreamed vision of     computing, where users can remotely store their data into the cloud to enjoy high quality applications. By data outsourcing, users can be relieved from the burden of local data storage and maintenance. Data integrity protection in CC a very challenging task, especially for users. To introduce an effective TPA. by using the technique “bilinear aggregate signature we can perform Multiple auditing task simultaneously.
  3. 3.  Data in a cloud environment can be formidable and     expensive for the cloud users. It is crucial to realize public audit ability for CSS, so that data owners may resort to a TPA. Audit service is significantly important for digital forensics and credibility in clouds. To implement Public audit ability, Retrievability and provable data possession have been proposed by some researchers. It is based on Probabilistic proof technique for Storage.
  4. 4. Disadvantages: Lack of rigorous performance analysis for constructed audit system.  It is crucial to develop a more efficient and secure mechanism for DAS.  Single TPA take more time to auditing the files.
  5. 5.  In this paper, we introduce a Dynamic Audit Service for     integrity verification of untrusted and outsourced storages. Our audit system, based on novel audit system architecture, can support dynamic data operations. Techniques such as fragment structure , random sampling, index-hash table. Approach based on probabilistic query & periodic verification. lower computation cost & shorter extra storage for integrity verification.
  6. 6. Advantages:  Improve performance & reduce extra storage.  Audit activities are efficiently scheduled in an audit period.  Each TPA to audit for a batch of files and to save the times for auditing the files.
  7. 7. System Requirements: Hardware Requirements: Processor Hard Disk RAM : : : Pentium 4. 80 GB. 1 GB Software Requirements: Operating System Coding Language Front end , Applets IDE : : : windows XP Java Swings , AWT : My Eclipse 8.6
  8. 8. Modules:  Key Generation  Design Framework  Basic Schemes  Privacy preserving auditing  Support for batch auditing  Support for data dynamics  Version control system  Generalization
  9. 9. Key generation:  File is divided into number of blocks.  File is encrypted &Use Key generation. Add file + key this is in cipher text reach to destination. This is called pseduo random results. Design Framework: In this there are 4 steps  Key generation:- Based on file size generate the randomized key.  Signature:- In this we add the signature that is unique signature.  Generation proof:- after data is transmited,same data is deliver in destination with same signature.  Verification proof:- If proof is matched then it is authentication data and integrity satisfis.
  10. 10. Basic Schemes:  Physical layer + MAC layer. Two layers are present so no possibility of attakers.  Single audit schemes verifed by TPA.  Multiple auditing schemes— so optimal solution. Privacy preserving auditing:  All number of blocks deliver in destination.  Once again verify those block in destination using HLA.  Two cases deliver or not deliver.& encryption and decryption.
  11. 11. Support for batch auditing:  concurrent authentication schemes we are perform in implementation of project after implementation of authentication schemes distinct files are deliver in destination. Support for data dynamics:  In less amount of time whatever corrupted files are removed and update the original in fraction of seconds by TPA. This support data dynamics.
  12. 12. Version control system:  In cloud server some blocks are modified those blocks are updated to new version of browser.  Whenever changes the hash function and browser version it is some what complex for accessing data. Generalization:  it uses HLA. In Multiple audit tasks one audit task is fail total information is incorrect.  All audit tasks are correct then only data is security. It is know as zero round knowledge proof.
  13. 13. Design: UML Diagrams:  Class diagram  Use case diagram  Sequence diagram  Collaboration diagram  Activity diagram
  14. 14. Class Diagram: It shows a set of classes ,interfaces and collaborations and their relationship.
  15. 15. Use case Diagram: it shows a set of use cases and other Actors and their relationship.
  16. 16. Sequence Diagram: It shows a set of objects and the message sent and received by those objects
  17. 17. Collaboration Diagram: It is an interaction diagram that emphasizes the structural organization of objects that send and receive messages.
  18. 18. Activity Diagram: It shows asset of special kind of doing that shows the flow from one activity to other activity within the system
  19. 19. DFD Diagram:
  20. 20. References:  C. Wang, Q. Wang, k. Ren, and W. Lou, “Privacy- Preserving Public auditing for Storage Security in CC.” in Proc. Of IEEE INFOCOM’10, March 2010.  Cloud Security Alliance, “Top threats to Cloud Computing,” 2010.  Storage Services in Cloud Computing,” IEEE Transactions on Service Computing,2011,to appear.
  21. 21. Thank You