1. Voice Over IP Security and Secure Semantic Web Dr. Bhavani Thuraisingham The University of Texas at Dallas November 15, 2005

2. Outline l PART I: - Voice over IP (VoIP) Security l PART II - Secure Semantic Web for VoIP Applications

3. VoIP Security: Concepts l Overview of VoIP l VoIP Security Issues l Reference: - NIST Report on VoIP Security - Secure Voice Over IP: Developments and Directions l Technical Report, The University of Texas at Dallas, To appear l Authors: Bhavani Thuraisingham, Ramya Ramamurthy and Siddhartha Gandhi

4. VoIP: Overview l Voice over Internet Protocol (VoIP) technology in general refers to the set of software and hardware standards that enable “voice” to be transported, with the help of the Internet Protocol (IP). l Apart from IP, VoIP also uses Real-Time Protocol (RTP), to ensure that the packets are delivered in a timely fashion l It is the assembling of voice into IP data. This data can be transmitted over an IP network to an addressable destination. l This means sending voice information in digital form in discrete packets rather than in the traditional circuit- committed protocols of the public switched telephone network

5. VoIP: Overview - II l Advantages: - It avoids the tolls charged by ordinary telephone service. VoIP phone bills are typically cheaper than traditional phone bills. - VoIP includes greater flexibility l Disadvantages - VoIP should not be installed without careful consideration of security problem introduced. - Sound quality and reliability are some other weak points of this technology; Although the quality service of VoIP is improving, it still cannot match that of PSTN. - Initial setup cost - Although there are low cost and even no-cost ways to transmit voice over IP, a company serious about VoIP will have to invest heavily in one or more VoIP devices.

6. VoIP: Protocols l H323 - Audio CODECs; Video CODECs; H.225 RAS; H.225 call signaling; H.245 Call Signaling; H.245 Control Signaling; Real-time Transfer Protocols; Real-time Control Protocol (RTCP) - Protocols for voice, video and data conferencing over packet switched networks such as Internet l Session Initiated protocols (SIP) - SIP Components: User Agent and Network Server - Standards for setting up sessions between clients l MGCP Media Gateway Control protocol - Eliminates complex processor intense IP Telephony devices

7. VoIP: Security l With VoIP the two main assets that need to be protected, are data and voice. l Unlike telephone lines, where the voice traffic is not always encrypted, except by certain security-sensitive organizations, the voice and data that are sent through VoIP needs to be encrypted always. l This is mainly because the voice and data go across the internet, where anyone can capture the packets meant for someone else. l Layers of defenses are needed to protect the voice calls because the dynamic nature of VoIP network parameters creates potential security vulnerabilities. l Some of the commonly used security measures on data networks include: firewalls, encryption, gateways

8. VoIP: Security - II l Appropriate network architecture has to be developed so as to keep the voice and data networks separate. l There should be access control and strong authentication at the voice gateway. l Introduction of the above also requires organizations to find a way to carry voice traffic through them. l This may sometimes bring performance problems. l A way to reduce the performance problems upon introducing firewalls, such as application-level gateways is to use Internet protocol security (IP sec) virtual private network at the router or gateway.

9. VoIP: Security - III l Need to assess, manage and mitigate risks that arise when VoIP is implemented. l Special considerations should be given to certain emergency services like 911; As VoIP is packet-switched, 911 automatic location services are not available with VoIP in some cases. l Organizations need to ensure that physical controls are in place to prevent access to VoIP network components. l Organizations should have sufficient backup power systems availability at the VoIP network switch and desktop. l VoIP systems incorporate an array of security features and protocols. l The WiFi Protected Access (WPA) security protocol should be deployed by organizations that intend allowing wireless access to their VoIP network.

10. VoIP: Security – Application Attacks l By spoofing a user’s identity, a potential attacker can cause an attack known as the Denial-of-Service in SIP-based VoIP networks. - A denial-of-service attack can use up the entire resources by exhausting the IP addresses of the server in a VoIP network l Man-in-the-middle attacks are possible by an intruder thereby modifying the original communication between the calling and called party. l An attacker with the local access to the VoIP network may overhear the network traffic and interpret the voice conversations taking place between the two parties. l An attacker can masquerade as a valid user and use the VoIP network to make free long distance calls.

11. VoIP: Security – Denaila of Seervice (DoS) Attacks l A denial-of-service attack is basically an attack on any IP network that causes a loss of service to its users. l There are basically three types of this attack. - Consumption of the computational resources, such as disk space, bandwidth etc - Interference with the physical network components. - Corruption of configuration information. l The network can be attacked by flooding the network with bogus packets, thereby not letting legitimate traffic to flow. l If the DoS is conducted in a huge and complex network, the entire network connectivity may have to be compromised by incorrectly configured network.

12. VoIP: Security – Solutions to Denial of Service (DoS) Attacks l Change the IP address of the end machine. - This is possible only if there is a single target machine. The new address can be updated in the internal servers. - This method is not quite possible, if the target involves many machines. l A firewall can stop a limited amount of DoS attacks. - A firewall can filter out attacks aimed at exploits in the OS l Filtering. - There might a specific signature to the traffic; examination of these captured packets may reveal the possibility of an attack. Once its known that, an attack would have been possible, one might temporarily block all the traffic from that source. - This might lead to blocking some of the “real” and legitimate packets. This is the major drawback of the filtering method.

13. VoIP: Security – Solutions to Denaila of Seervice (DoS) Attacks l Change the IP address of the end machine. - This is possible only if there is a single target machine. The new address can be updated in the internal DNS servers. - This method is not quite possible, if the target involves many machines. l A firewall can stop a limited amount of DoS attacks. - A firewall can filter out attacks aimed at exploits in the OS l Another technique is filtering. - There might a specific signature to the traffic; examination of these captured packets may e reveal the possibility of an attack. Once its known that an attack would have been possible, one might temporarily block all the traffic from that source. - This might lead to blocking some of the “real” and legitimate packets. This is the major drawback of the filtering method.

14. Security in SIP l Authentication and Authorization - Authentication and Authorization is handled in SIP either on request-by-request basis or challenge/response pairs. - SIP provides a standard challenge based authentication mechanism for authentication. - Any time the proxy server or the user Agent receives a request it may challenge the client for its credentials. - The client may provide its credentials to the proxy server before it receives the authentication required message from the proxy server but not after that. - Framework of SIP authentication closely resembles that of HTTP. l Solutions for - Tampering message bodies, Tearing down messages, Denial of service, Registration hijacking, Impersonating a server

15. Summary and Directions l VoIP is the way for communicating voice l Security is critical l Both access control and malicious corruption including denial of service threats have to be investigated l SIP security is critical l Security for VoIP and also SIP is in the initial stages l Need to manage the Voice Information

16. Secure Semantic Web: Overview l 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 Applications = Web Database Management + Web Services + Information Integration + Multimedia/Voice SEMANTIC WEB must support VoIP and be SECURE

17. Layered Architecture for Dependable Semantic Web 0 Some Challenges: Security and Privacy cut across all layers; Integration of Services; Composability XML, XML Schemas Rules/Query Logic, Proof and Trust SECURITYSECURITY Other Services RDF, Ontologies TCP/IP/HTTP/SSL PRIVACYPRIVACY 0 Adapted from Tim Berners Lee’s description of the Semantic Web

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

19. Aspects of XML Security l Controlling access to XML documents - Granularity of access: parts of documents, entire documents l Specifying policies and credentials in XML l Third party publication of XML documents l Encryption (www.w3c.org)www.w3c.org l How can we secure VoiceML?

20. Specifying User Credentials in XML Alice Brown University of X CS Security John James University of X CS Senior

21. Specifying Security Policies in XML <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 = - - - - 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 Policies for VoiceML?

22. Access Control Strategy l 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 l Access control module checks the policy based and applies policy specs l Views of the document are created based on credentials and policy specs l In case of conflict, least access privilege rule is enforced l Works for Push/Pull modes

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

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

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

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

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

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

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

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

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

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

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

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

35. Web Database Management l Database access through the web - JDBC and related technologies l Query, indexing and transaction management - E.g., New transaction models for E-commerce applications - Index strategies for unstructured data l Query languages and data models - XML has become the standard document interchange language l Managing XML databases on the web - XML-QL, Extensions to XML, Query and Indexing strategies l Managing multimedia and voice data - Indexing and query strategies

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

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

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

39. Secure Web Service Architecture Confidentiality, Authenticity, Integrity Service requestor Service provider UDDI Query BusinessEntity BusinessService BindingTemplate BusinessService tModel PublisherAssertion

40. Vision for Dependable Semantic Web for VoIP Core Semantic Web Technologies: Systems, Networks, Multimedia, 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,- - -