Data and Applications Security Developments and Directions

1. Data and Applications Security Developments and Directions Dr. Bhavani Thuraisingham The University of Texas at Dallas Secure Object Systems October 1, 2010

2. Outline • Background on object systems • Discretionary security • Multilevel security • Objects for modeling secure applications • Object Request Brokers • Secure Object Request Brokers • Secure frameworks • Secure Multimedia and Geospatial Systems

3. Concepts in Object Database Systems • Objects- every entity is an object • Example: Book, Film, Employee, Car • Class • Objects with common attributes are grouped into a class • Attributes or Instance Variables • Properties of an object class inherited by the object instances • Class Hierarchy • Parent-Child class hierarchy • Composite objects • Book object with paragraphs, sections etc. • Methods • Functions associated with a class

4. D1 D2 J1 Example Class Hierarchy ID Name Author Publisher Document Class Method2: Method1: Print-doc(ID) Print-doc-att(ID) Journal Subclass Book Subclass Volume # # of Chapters B1

5. Example Composite Object Composite Document Object Section 2 Object Section 1 Object Paragraph 1 Object Paragraph 2 Object

6. Security Issues • Access Control on Objects, Classes, Attributes etc. • Execute permissions on Methods • Multilevel Security • Security impact on class hierarchies • Security impact on composite hierarchies

7. Objects and Security Secure OODB Secure OODA Secure DOM Persistent Design and analysis Infrastructure data store Secure OOPL Secure Frameworks Programming Business objects language Secure OOT Technologies Secure OOM Unified Object Model is Evolving

8. Access Control

9. Access Control Hierarchies

10. Secure Object Relational Model

11. Policy Enforcement

12. Sample Systems

13. Multilevel Security

14. Some Security Properties • Security level of an instance must dominate the level of the class • Security level of a subclass must dominate the level of the superclass • Classifying associations between two objects • Method must execute at a level that dominates the level of the method

15. Multilevel Secure Object Relational Systems

16. Sample MLS Object Systems

17. Objects for Secure Applications

18. Object Modeling

19. Dynamic Model

20. Functional Model

21. UML and Policies

22. Distributed Object Management Systems • Integrates heterogeneous applications, systems and databases • Every node, database or application is an object • Connected through a Bus • Examples of Bus include • Object Request Brokers (Object Management Group) • Distributed Component Object Model (Microsoft)

23. Object-based Interoperability Server Client Object Object Object Request Broker Example Object Request Broker: Object Management Group’s (OMG) CORBA (Common Object Request Broker Architecture)

24. Java-based Servers Clients RMI Business Objects Javasoft’s RMI (Remote Method Invocation)

25. Objects and Security Secure OODB Secure OODA Secure DOM Persistent Design and analysis Infrastructure data store Secure OOPL Secure Frameworks Programming Business objects language Secure OOT Technologies Secure OOM Unified Object Model is Evolving

26. Secure Object Request Brokers

27. CORBA (Common Object Request Broker Architecture) Security • Security Service provides the following: • Confidentiality • Integrity • Accountability • Availability • URLs • http://www.javaolympus.com/J2SE/NETWORKING/CORBA/CORBASecurity.jsp • http://student.cosy.sbg.ac.at/~amayer/projects/corbasec/sec_overview.html • www.omg.org

28. OMG Security Specifications

29. CORBA (Common Object Request Broker Architecture) Security • Security Service provides the following: • Confidentiality • Integrity • Accountability • Availability • URLs • http://www.javaolympus.com/J2SE/NETWORKING/CORBA/CORBASecurity.jsp • http://student.cosy.sbg.ac.at/~amayer/projects/corbasec/sec_overview.html • www.omg.org

30. CORBA (Common Object Request Broker Architecture) Security - 2 • Identification and Authentication of Principles • Authorization and Access Control • Security Auditing • Security of communications • Administration of security information • Non repudiation

31. Dependable Object Request Brokers Technology provided by Project Navigation Display Consoles Data Analysis Programming Processor Data Links (14) Group (DAPG) & Sensors Refresh Channels Sensor Multi-Sensor Detections Tracks Integrate Security, Real-time and Fault Tolerance Computing Future Future Future App App App Data MSI Mgmt. App Data Xchg. Infrastructure Services Real Time Operating System Hardware

32. Secure Frameworks

33. Directions • Object Models • UML for Security applications is becoming common practice • Secure distributed object systems has gained popularity • Evolution into secure object-based middleware • Secure object-based languages • Integrating security and real-time for object systems • Distributed Objects • Security cannot be an afterthought for object-based interoperability • Use ORBs that have implemented security services • Trends are moving towards Java based interoperability and Enterprise Application Integration (EAI) • Examples of EAI products are Web Sphere (IBM) and Web Logic (BEA) • Security has to be incorporated into EAI products

34. Why Multimedia Data Management System? • Need persistent storage for managing large quantities of multimedia data • A Multimedia data manager manages multimedia data such as text, images, audio, animation, video • Extended by a Browser to produce a Hypermedia data management system • Heterogeneity with respect to data types • Numerous Applications • Entertainment, Defense and Intelligence, Telecommunications, Finance, Medical

35. Architectures:Loose Integration User Interface Module for Integrating Data Manager with File Manager Data Manager for Metadata Multimedia File Manager Multimedia Files Metadata

36. Architectures:Tight Integration User Interface MM-DBMS: Integrated data manager and file manager MultimediaDatabase

37. Data Model:Scenario Example: Object representation Object A2000 Frames 4/95 8/95 5/95 10/95 Object B 3000 Frames

38. Multimedia Data Access: Some approaches • Text data • Selection with index features • Methods: Full text scanning, Inverted files, Document clustering • Audio/Speech data • Pattern matching algorithms • Matching index features given for searching and ones available in the database • Image data • Identifying geometric boundaries, Identifying spatial relationships, Image clustering • Video data • Retrieval with metadata, Pattern matching with images

39. Metadata for Multimedia • Metadata may be annotations and stored in relations • I.e., Metadata from text, images, audio and video are extracted as stored as text • Text metadata may be converted to relations by tagging and extracting concepts • Metadata may be images of video data • E.g., certain frames may be captured as metadata • Multimedia data understanding • Extracting metadata from the multimedia data

40. Storage Methods • Single disk storage • Objects belonging to different media types in same disk • Multiple disk storage • Objects distributed across disks • Example: individual media types stored in different disks • I.e., audio in one disk and video in another • Need to synchronize for presentation (real-time techniques) • Multiple disks with striping • Distribute placement of media objects in different disks • Called disk striping

41. Security Issues • Access Control • Multilevel Security • Architecture • Secure Geospatial Information Systems

42. Access Control for Multimedia Databases • Access Control for Text, Images, Audio and Video • Granularity of Protection • Text • John has access to Chapters 1 and 2 but not to 3 and 4 • Images • John has access to portions of the image • Access control for pixels? • Video and Audio • John has access to Frames 1000 to 2000 • Jane has access only to scenes in US • Security constraints • Association based constraints • E.g., collections of images are classified

43. MLS Security

44. Example Security Architecture: Integrity Lock

45. Inference Control

46. Securing Geospatial Data • Geospatial images could be Digital Raster Images that store images as pixels or Digital Vector Images that store images as points, lines and polygons • GSAM: Geospatial Authorization Model specifies subjects, credentials, objects (e.g, points, lines, pixels etc.) and the access that subjects have to objects • Reference: Authorization Model for Geospatial Data; Atluri and Chun, IEEE Transactions on Dependable and Secure Computing, Volume 1, #4, October – December 2004. • Bhavani M. Thuraisingham, Gal Lavee, Elisa Bertino, Jianping Fan, Latifur Khan: Access control, confidentiality and privacy for video surveillance databases. SACMAT 2006: 1-10 • Details will be given in one of the lectures after the mid-term.

47. Secure Geospatial Data Management • Secure Geospatial data management • References: • Vijayalakshmi Atluri, Soon Ae Chun: An Authorization Model for Geospatial Data. IEEE Trans. Dependable Sec. Comput. 1(4): 238-254 (2004) • Elisa Bertino, Bhavani M. Thuraisingham, Michael Gertz, Maria Luisa Damiani: Security and privacy for geospatial data: concepts and research directions. SPRINGL 2008:6-19

48. Securing Geospatial Data • Geospatial images could be Digital Raster Images that store images as pixels or Digital Vector Images that store images as points, lines and polygons • GSAM: Geospatial Authorization Model specifies subjects, credentials, objects (e.g, points, lines, pixels etc.) and the access that subjects have to objects • Reference: Authorization Model for Geospatial Data; Atluri and Chun, IEEE Transactions on Dependable and Secure Computing, Volume 1, #4, October – December 2004.

49. Framework for Geospatial Data Security (Joint with UCDavis and Purdue U.)

50. Example of several GIS repositories and GIS themes/layers for Northern California (Gertz, Bertino, Thuraisingham) Assume a single GIS data repository that manages information about parcels (being the basic units of geography for local government) and cadastre, including land use and zoning, environmental areas, and municipal utility services. Such type of repository is typically used by public sector staff to assist property owners and to support emergency, fire, and police operations. The latter type of usage includes identifying property structures and owners. Parcel maps in particular can be useful to do damage assessment after a disaster.