DISTRIBUTED DATABASE

2,794 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,794
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
75
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • These multidatabasearchitectures have been studied extensively in the literature.
  • 1-trusted front-end database system is connected to non-trusted back-end database systems Each back-end database system operates at a single level and manages data at that level.For example, an Unclassified DBMS manages the unclassified data while a Secret DBMS manages Secret data. All communication between the backend database systems is through the front-end database system.2-In this approach, the unclassified data is replicated at the Secret and Top-Secret databases, and the Secret data is replicated at the Top-Secret database.
  • -at the same time trusted mediator has received a great deal of attention
  • These are consumer facing services which allow the patient to enter and manage their own information, as well as create sub accounts to allow healthcare providers direct access.
  • Step 1: Identification of sites, subjects, objects, and permitted actions (identification process). Step 2: Assignment of security labels (labeling process). Step 3: Fragmentation and allocation of data (distribution process). Step 4: Processing of security constraints. Step 5: Definition of permitted actions.
  • Identification of the subjects 1. Define all the user roles that exist within an application. 2. Group the existing user roles under the corresponding user category depending on the task of the user in the application.Identification of the objects. The security objects are the target of the security protection, and are in another sense the data contained in the application. Data sets represent data with a common use. These data sets are grouped into a number of data categories. Identification of the sites. the function of each site in the context of the whole application, the technical, the type of connection, whether the site is mobile or not and the degree of mobility, the security threats to each site, any special requirementsIdentification of the permitted actions. DAC and MAC security policies 2-Assignment of security labels to the subjects 1. Assign data sets starting with the user roles under a user category. 2. Move data sets shared by all user roles to their common user category. 3. Move data sets shared by all user categories to their common super categories. This procedure is repeated till reaching the root.
  • The proposed design methodology takes into account and handles all three components of security (availability, integrity, confidentiality). Fragmentation. 1. If the part to be upgraded is the whole table, then all the table and all its rows are upgraded. 2. If the part to be upgraded is just some rows of the table, then just these rows are assigned a higher security label. 3. In the case that the part to be upgraded is only some fields of a table, then this causes the initial table to be fragmented into two tables. One part is assigned a low and another a strictly higher level. Allocation and replication The decision of whether to replicate or not is usually based on two factors: the number of reads versus the number of updates
  • Personal opiniondiscussed a methodology to combine only two types of access control and limitation of this if we have more than two types I think that process of combination will not successful .
  • conflicting policies implemented in an ad hoc mannerSecurity managers of mission-critical information enclaves must guarantee the coherence of their policies within global
  • JDBC provides a standard API for accessing heterogeneous databases, while CORBA enables cross-platform application-level integration.These technologies can be used in concert to provide a common interface for security policy mediators.Each enterprise manages its own policy mediator, which rests on CORBA and JDBC layers. Each mediator contains a current model of its database and prevailing security policy . This is held as a mapping to the primitive authorization modelThe metapolicy concept –a policy about policies– was introduced in . Metapolicies were applied to policy negotiation
  • verify its security based on the state machine theory
  • Access Attribute : the type of access mode including select, append, modifySecurity Level : represent categories set privileges on different access mode to an objectRequest element: The set of all the access request elements charged by subjectAccess Request : A certain request charged by a subject to some objectAccess Decision :The set of system decisions on access request denoted as D, D={Yes, No, Error}.Time :The index of event labeled by time
  • Access Set : is the set of all the current access statuses. representing that subject s has access authority a on objectObject hierarchy : is the paternity of objects described by a rooted tree. The security of an object dominates that of its son.Role hierarchy : is the paternity of objects described by a rooted tree. The security of an object dominates that of its son.APT : is the set of the APTs of all the current objects in the system denoted as APT.Functions : are level functions and role functions that decide the security level of subject/object or the corresponding relation between the roles and the subjects.
  • DISTRIBUTED DATABASE

    1. 1. DISTRIBUTED DATABASE<br /> SECURITY<br />“State-of-the-art”<br />Prepared by :-<br />Mohammed Siddig Ahmed.<br />Omer SalihDawood.<br />Mohammed zein.<br />
    2. 2. introduction<br />The developments in computer networking technology and database systems technology resulted in the development of distributed databases in the late 1970s.<br />There are various architectural for a distributed database systems :-<br />the control is centralized while the data is distributed.<br />the data as well as control are distributed.<br />Multidatabase architectures .<br />non-multidatabase approach(no local database management systems (DBMSs))<br />
    3. 3. Multilevel Security <br />Much of the work in secure distributed database systems has focused on multilevel security.<br />the early work in the field began with the US. Air Force Summer Study .<br />approaches based on distributed data and centralized control architectures were proposed. <br />Prototypes based on these approaches were also developed during the late 1980s and early 1990s<br />
    4. 4. Multilevel Security Con.<br />Two approaches were proposed at the Summer Study:-<br /> the Partitioned approach .<br />trusted front-end database system is connected to non-trusted back-end.<br />second approach was examined where data is replicated.<br />In this approach, the unclassified data is replicated at the Secret and Top-Secret databases, and the Secret data is replicated at the Top-Secret database<br />
    5. 5. Inference Problem<br />This problem has been discussed a great deal over the past three decades. <br />An extensive investigation of the inference problem for distributed database systems began around 1992.<br />There is still work on this problem especially with emerging technologies such as data warehousing, data mining and the web. <br />
    6. 6. Hippocratic databases <br /> During the late of 1990s and early and mid of 2000s .<br />These databases are designed such that data collection and disclosure are only performed with the consent of the user who’s data is in question. <br />
    7. 7. trusted mediator <br />At the same time the trusted mediator databaseshas received a great deal of attention<br />the TIHI (Trusted Interoperation of Healthcare Information) project uses a trusted mediator to determine which queries should or should not be allowed .<br />several commercial systems.<br /> Google Health.<br />Microsoft HealthVault,<br />
    8. 8. Blind comparer <br /> During the mid and late of 2000s .<br />share privacy-sensitive data across distinct organizations.<br />allowing organizations to keep their legacy databases and maintain ownership of the data that they currently store<br />
    9. 9. Blind comparer <br />
    10. 10. Improve Blind comparer <br />On the late of 2000s.<br />to make the blind comparer more secure it was better to use fake queries and declassification techniques<br />
    11. 11. Federated database security <br />“state of the art”<br />
    12. 12. Introduction.<br />A federated database system .<br />Characteristics of Federated Database Systems :<br /><ul><li>Distribution.
    13. 13. Heterogeneity .
    14. 14. Autonomy .</li></li></ul><li>Multidatabase systems can be classified into two types based on the autonomy <br />
    15. 15. Five-level Schema Architecture for Federated Databases:<br /><ul><li>Local schema .
    16. 16. Component schema.
    17. 17. Export schema .
    18. 18. Federated schema .
    19. 19. External schema .</li></ul>Federated Database Security:<br />
    20. 20. Federated Database Security State of The Art :<br />Federated Database Security in 80th:<br />Federated Database Security in 90th focused on:<br /><ul><li>access control .
    21. 21. identity management .
    22. 22. Authorization.</li></li></ul><li>
    23. 23. Federated Database Security in millennium :<br /><ul><li>access control .
    24. 24. identity management .
    25. 25. Authorization.
    26. 26. Concurrency control .</li></li></ul><li>Integrated distributed<br /> database security<br />“state of the art”<br />
    27. 27. Integrated Distributed Database<br />A common problem within most large corporations is the diversity of database systems.<br />multi-vendor database servers.<br />components of security (availability, integrity, confidentiality). <br />
    28. 28. Research Directions (1998) <br />Security is an important issue in health care environments where large amounts of highly sensitive personal data are processed. <br />appeared in the late nineties methodology based on the combination of DAC and MAC security models and uses hierarchies of user roles and data sets <br />
    29. 29. User Role Hierarchies<br />
    30. 30. Fragmentation and allocation <br />
    31. 31. Fragmentation and allocation <br />
    32. 32. Beginning of the millennium <br />
    33. 33. Research Directions (2002) <br /> New architecture that uses mediators and a primitive ticket-based authorization model to manage disparate policies in information enclaves.<br />
    34. 34. Heterogeneous information system<br />
    35. 35. Mediation Infrastructure<br /> A middleware architecture for security policy mediation in information enclaves. It begins by assessing existing technology for software interoperability.<br />
    36. 36. Mediator & primitive authorization <br />Mediators can be used in conjunction with other integration technologies to achieve a standard architecture for security policy coordination .<br />The primitive authorization model architecture provides a common foundation for policy facilitates and coordination <br />
    37. 37. Ticket-based Authorization Model Architecture<br />
    38. 38. At the end of 2006 <br />
    39. 39. Research Directions (2006) <br />Some researchers develop “Mediator” to map different policies. The deficiency is its lower efficiency. They proposed the concept of “authority propagation” to realize the integration AC policies.<br />
    40. 40. Authority Propagating Tree (APT) Model<br /> Use “tree” to express the ministration of authorities for Graph Theory offer convenient means describing attribution flows.<br />The Advantages of APT<br />It can represent RBAC, MAC and DAC policies.<br />It can track the whole authority granting history.<br /> Because of the above advantages the APT can generate a new access control model .<br />
    41. 41. Integrated Database Access ControlModel (DBIAC)<br />Model Elements<br /><ul><li>Access Attribute
    42. 42. Security Level
    43. 43. Request element
    44. 44. Access Request
    45. 45. Access Decision
    46. 46. Time</li></li></ul><li>Integrated Database Access ControlModel (DBIAC)<br />Model Components<br /><ul><li>Access Set
    47. 47. Object hierarchy
    48. 48. Role hierarchy
    49. 49. APT
    50. 50. Functions</li></li></ul><li>References<br />http://www.utdallas.edu/~bxt043000/Publications/Journal-Papers/DAS/J3_Multilevel_security_issues_in_distributed_database_management_systems.pdf<br />www.gbv.de/dms/tib-ub-hannover/016971752.pdf<br />M. Siegenthaler and K. Birman, “Sharing private information across distributed databases,” in submitted for publication, 2009.<br />http://www.utdallas.edu/~bxt043000/Publications/Journal-Papers/DAS/J25_Security_Constraint_Processing_in_a_Multilevel_Secure_Distributed_Database_Management_System.pdf<br />R. Agrawal, J. Kiernan, R. Srikant, and Y. Xu, “Hippocratic databases,” 2002, pp. 143–154.<br />K. LeFevre, R. Agrawal, V. Ercegovac, R. Ramakrishnan, Y. Xu, and D. DeWitt, “Limiting disclosure in hippocratic databases,” in VLDB ’04: Proceedings of the Thirtieth international conference on Very large databases. VLDB Endowment, 2004, pp. 108–119.<br />G. Wiederhold, M. Bilello, V. Sarathy, and X. Qian, “A security mediator for health care information,” in Proceedings of the 1996 AMIA Conference, 1996, pp. 120–124.<br />
    51. 51. References<br />Google Health, “http://www.google.com/health.”<br />Microsoft HealthVault, http://www.healthvault.com/.<br />M. Siegenthaler and K. Birman, “Sharing private information across distributed databases,” in submitted for publication, 2009.<br />-Susanne Busse, Ralf-DetlefKutsche, Ulf Leser, Herbert Weber, Federated Information Systems:Concepts, Terminology and Architectures, TechnischeUniversit.t Berlin,1999.<br />JAMES A. LARSON, Federated Database Systems for Managing Distributed,<br />Heterogeneous, and Autonomous Databases’, 1990.<br />W. Eßmayr, G. Pernul, A M. Tjoa, A Security Concept for Federated Database Systems, 1st Int. Congress on Ethical, Legal, and Social Aspects of Digital Information, Monte-Carlo, Monaco, March 1997.<br />Sabrina De CapitanidiVimercati ,PierangelaSamarati, Access Control in Federated Systems.<br />
    52. 52. References<br /> Eugene F. Fodor, Deriving Global Authorizations for Federated Databases.1999.<br />Ajoy Kumar, Federated Identity Management,2004.<br />Arun Kumar Yadav, An Approach for Ensuring Concurrency Control of Global Transactions in Heterogeneous Distributed Database,2010.<br />http://en.wikipedia.org/wiki/Federated_database_system.<br />Marie Khair, IoannisMavridis & George Pangalos, Design of secure distributed medical database systems, Database and Expert Systems Applications, 9th International Conference, DEXA'98 Vienna, Austria, August 24–28, 1998.<br />John Hale, Pablo Galiasso, Mauricio Papa, SujeetShenoi,Security Policy Coordination for Heterogeneous Information Systems, IEEE 6 Aug 2002.<br />LIU Xin, HAN Zhen & SHEN Chang-Xiang,An Integrated Access Control Model of Distributed Database Systems, First International Conference on Innovative Computing, Information and Control - Volume III (ICICIC'06), 2006.<br />
    53. 53. References<br />Bell, D.E., and La Padula, L.J. “Secure Computer Systems: A Refinement of the Mathematical Fundations” [J],ESD-TR-73-278, Vol.III, AD 780 528, Electronic Systems Division, Air Force System Command, Hanscom AFB, Bedford, Massachusetts, November. 1974.<br />R.S. Sandhu, E.J.Coyne, H.L.Feinstein. Role Based Access Control Models. IEEE Computer, February 1996. Vol 29( 2): 38-47.<br />E.Bertino, S.Jajodia, P.Samarati. Supporting Multiple Access Control Policies in Databases System. In: IEEE Symposium on Security and Privacy. Oakland, California. 1996.<br />Liuyi, Database and Information System Security[M, Science Press, China,2000.<br />Xin LIU, Zhen HAN, etc., Research On the Extended Confidential Level of BLP Model, Proceedings of KES 2005, Knowledge-Based Intelligent Information and Engineering Systems PartIV, Pps257-262.<br />JiangZongli, JiangShouxu, Formal Language and Automata Theory, Tsinghua University Press,2003. <br />

    ×