1 / 29

Data and Applications Security Developments and Directions

Data and Applications Security Developments and Directions. Dr. Bhavani Thuraisingham The University of Texas at Dallas Lecture #24 Semantic Web and Security April 7, 2005. Outline. Semantic Web Overview

kalli
Download Presentation

Data and Applications Security Developments and Directions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data and Applications Security Developments and Directions Dr. Bhavani Thuraisingham The University of Texas at Dallas Lecture #24 Semantic Web and Security April 7, 2005

  2. Outline • Semantic Web Overview • Web Data Management and Web Services, XML (eXtensible Markup Language) , RDF (Resource Description Framework),, Closed World Machine, Rules ML, Ontologies and Inference, Trust and Proof • Secure Semantic Web • Security for Web data management and web services, XML, RDF, Closed World Machine, Rules ML, Security and Ontologies, - - - • Vision • Reference: www.w3c.org

  3. Semantic Web: Overview • According to Tim Berners Lee, The Semantic Web supports • Machine readable and understandable web pages • Enterprise application integration • Nodes and links that essentially form a very large database Premise: Semantic Web = Web Database Management + Web Services + Information Integration + Rules Processing + - - - - -

  4. SECURITY P R I V A C Y Logic, Proof and Trust Rules/Query Other Services RDF, Ontologies XML, XML Schemas URI, UNICODE Layered Architecture for Dependable Semantic Web • Adapted from Tim Berners Lee’s description of the Semantic Web • Some Challenges: Interoperability between Layers; Security and Privacy cut across all layers; Integration of Services; Composability

  5. Privacy Confidentiality Trust Dependability Relationships between Dependability, Confidentiality, Privacy, Trust Dependability: Security, Privacy, Trust, Real-time Processing, Fault Tolerance; also sometimes referred to as “Trustworthiness” Confidentiality: Preventing the release of unauthorized information considered sensitive Privacy: Preventing the release of unauthorized information about individuals considered sensitive Trust: Confidence one has that an individual will give him/her correct information or an individual will protect sensitive information

  6. Web Database Management: Developments and Directions • Database access through the web • JDBC and related technologies • Query, indexing and transaction management • E.g., New transaction models for E-commerce applications • Index strategies for unstructured data • Query languages and data models • XML has become the standard document interchange language • Managing XML databases on the web • XML-QL, Extensions to XML, Query and Indexing strategies • Integrating heterogeneous data sources on the web • Information integration and ontologies are key aspects • Mining the data on the web • Web content, usage, structure and content mining

  7. Web Services • Web Services are about services on the web for carrying out many functions including directory management, source location, subscribe and publish, etc. • Web services description language (WSDL) exists for web services specification • Web services architectures have been developed • Challenge now is to compose web services; how do you integrate multiple web services and provide composed web service in a seamless fashion • Ultimate goal is to have web services for information integration

  8. Publish Query UDDI Answer Request the service Service providers Web service architecture Service requestor

  9. What is XML all about? • XML is needed due to the limitations of HTML and complexities of SGML • It is an extensible markup language specified by the W3C (World Wide Web Consortium) • Designed to make the interchange of structured documents over the Internet easier • Key to XML is Document Type Definitions (DTDs) • Defines the role of each element of text in a formal model • Allows users to bring multiple files together to form compound documents

  10. RDF • Resource Description Framework is the essence of the semantic web • Adds semantics with the use of ontologies, XML syntax • Separates syntax from semantics • RDF Concepts • Basic Model • Resources, Properties and Statements • Container Model • Bag, Sequence and Alternative

  11. Ontology • Common definitions for any entity, person or thing • Several ontologies have been defined and available for use • Defining common ontology for an entity is a challenge • Mappings have to be developed for multiple ontologies • Specific languages have been developed for ontologies including RDF and OIL (Ontology Interface Language) • DAML (Darpa Agent Markup Language) is an ontology and inference language based on RDF • DAMP + OIL; combines both languages

  12. Rules ML, Inference and CWM • Rules ML is a Rules Markup Language for specifying rules • Inferencing is about making deductions • Deductions based on rules specified in Rules ML or DAML+OIL • Based on denotational logic • CWM: Closed World Machine • Inference engine for the semantic web written as a Python program

  13. Trust and Proof • Context • Based on the context specify to what extent one trusts the statements • Digital signatures • Verifies that one wrote a particular document • Proof • Using proof languages we prove whether or not a statement is true • Proofs based on logical systems

  14. Secure Web databases • Secure data models • Secure XML, RDF, - - - - • Relational, object-oriented, text, images, video, etc. • Secure data management functions • Secure query, transactions, storage, metadata • Key components for secure digital libraries and information retrieval/browsing

  15. Query UDDI Service requestor BusinessService Secure Web Service Architecture Confidentiality, Authenticity, Integrity BusinessEntity <dsig:Signature> tModel BusinessService PublisherAssertion BindingTemplate Service provider

  16. Aspects of XML Security • Controlling access to XML documents • Granularity of access: parts of documents, entire documents • Specifying policies and credentials in XML • Third party publication of XML documents • Encryption (www.w3c.org)

  17. Specifying User Credentials in XML <Professor credID=“9” subID = “16: CIssuer = “2”> <name> Alice Brown </name> <university> University of X <university/> <department> CS </department> <research-group> Security </research-group> </Professor> <Secretary credID=“12” subID = “4: CIssuer = “2”> <name> John James </name> <university> University of X <university/> <department> CS </department> <level> Senior </level> </Secretary>

  18. Specifying Security Policies in XML <? Xml VERSION = “1.0” ENCODING = “utf-8”?> <Policy–base> <policy-spec cred-expr = “//Professor[department = ‘CS’]” target = “annual_ report.xml” path = “//Patent[@Dept = ‘CS’]//Node()” priv = “VIEW”/> <policy-spec cred-expr = “//Professor[department = ‘CS’]” target = “annual_ report.xml” path = “//Patent[@Dept = ‘EE’] /Short-descr/Node() and //Patent [@Dept = ‘EE’]/authors” priv = “VIEW”/> <policy-spec cred-expr = - - - - <policy-spec cred-expr = - - -- </Policy-base> Explantaion: CS professors are entitled to access all the patents of their department. They are entitled to see only the short descriptions and authors of patents of the EE department

  19. Access Control Strategy • Subjects request access to XML documents under two modes: Browsing and authoring • With browsing access subject can read/navigate documents • Authoring access is needed to modify, delete, append documents • Access control module checks the policy based and applies policy specs • Views of the document are created based on credentials and policy specs • In case of conflict, least access privilege rule is enforced • Works for Push/Pull modes

  20. User Pull/Query Push/result X-Access X-Admin Admin Tools Credential base Policy base XML Documents System Architecture for Access Control

  21. Third-Party Architecture • The Owner is the producer of informationIt specifies access control policies • The Publisher is responsible for managing (a portion of) the Owner information and answering subject queries • Goal: Untrusted Publisher with respect to Authenticity and Completeness checking XML Source policy base Credential base SE-XML Owner Publisher Reply document credentials Query User/Subject

  22. RDF and Security • XML Security for the Syntax of RDF • Access control, Third party publishing, Specifying g policies and credentials • Securing RDF Graphs • UTD research (MS and PhD work in progress) • Securing semantics • Approach: Take semantic specifications in RDF and incorporate security • Security policies embedded into the semantics

  23. Security and Ontology • Ontologies used to specify security policies • Example: Use DAML + OIL to specify security policies • Choice between XML, RDF, Rules ML, DAML+OIL • Security for Ontologies • Access control on Ontologies • Give access to certain parts of the Ontology

  24. Security and Inferencing • Specify security policies in Rules ML • Inferencing is part of the semantic web; deduced information could be sensitive • Extend CWM to handle the inference and privacy problem • Extended Python program?

  25. Rules Processing User Interface Manager XML Database Design Tool Constraints during database design operation Constraint Manager Rules/ Constraints Update Processor: Constraints during update operation Query Processor: Constraints during query and release operations XML Document Manager XML Database

  26. Rule-Processing (Concluded) Interface to the Semantic Web Technology By W3C Inference Engine/ Rules Processor Policies Ontologies Rules XML, RDF Documents Web Pages, Databases Semantic Web Engine

  27. Security, Trust and Proof • Extend trust management and Trust negotiation techniques for semantic web • Trust Services, Trust negotiation (TN) • Applicability of KeyNote and Trust-X (U of Milan), TrustBuilder (UIUC) • Use proof to reason about security and trust • Is the semantic web secure? • Is the semantic web trustworthy? • Are there security/trust violations?

  28. Coalition Application Testbed: A Suggestion • Identify Coalition • Identify Coalition Example: A good starting point will be the Coalition experiments conduced under DARPA’s CoABS program that includes MBP (Master Battle Planner) and CAMPS (Consolidated Air Mobility Planning System) applications • Develop scenarios and determine the roles are of the coalition partners • Identify information to be accessed/shared and how the semantic web may be used by the coalition • Design Policies • Design policies (e.g., security, privacy, trust) for the coalition when accessing information resources • Implement Test Bed • Develop a test bed that uses ontologies for information integration and enforces the policies

  29. Vision for Dependable Semantic Web Core Semantic Web Technologies: Systems, Networks, Agents, AI, Machine Learning, Data Mining, Languages, Software Engineering, Information Integration Need research to bring together the above technologies Directions: Security/Trust/Privacy, Integrate sensor technologies, Pervasive computing, Social impact Domain specific semantic webs: DoD, Intelligence, Medical, Treasury,- - - • Some Challenges: Secure Semantic Interoperability; Secure Information Integration; Integrating Pervasive computing and sensors

More Related