DATA ACCESS CONTROL, MANAGEMENT DATA AND SECURITY (CIB125) PERTEMUAN 6

Slides:



Advertisements
Similar presentations
1 cs691 chow C. Edward Chow Confidentiality Policy CS691 – Chapter 5 of Matt Bishop.
Advertisements

Outline  Introduction  Background  Distributed DBMS Architecture  Distributed Database Design  Semantic Data Control ➠ View Management ➠ Data Security.
Relational Model dww-database system.
Distributed DBMSPage 6. 1© 1998 M. Tamer Özsu & Patrick Valduriez Outline Introduction Background Distributed DBMS Architecture Distributed Database Design.
Distributed DBMSPage © 1998 M. Tamer Özsu & Patrick Valduriez Outline Introduction Background Distributed DBMS Architecture Distributed Database.
Distributed DBMS © M. T. Özsu & P. Valduriez Ch.7/1 Outline Introduction Background Distributed Database Design Database Integration Semantic Data Control.
Jan. 2014Dr. Yangjun Chen ACS Database security and authorization (Ch. 22, 3 rd ed. – Ch. 23, 4 th ed. – Ch. 24, 6 th )
Relational Model The main reference of this presentation is the textbook and PPT from : Elmasri & Navathe, Fundamental of Database Systems, 4 th edition,
Relational Model Indra Budi Fakultas Ilmu Komputer UI 2 Essentials of Relational Approach The Relational Model of Data is Based on.
Access Control Methodologies
DDBMS Security - Bakul Gada.
Slide #5-1 Chapter 5: Confidentiality Policies Overview –What is a confidentiality model Bell-LaPadula Model –General idea –Informal description of rules.
Database Security - Farkas 1 Database Security and Privacy.
Distributed Database Design & Semantic Data Control
Security Fall 2006McFadyen ACS How do we protect the database from unauthorized access? Who can see employee salaries, student grades, … ? Who can.
CSCI 5707: Database Security Pusheng Zhang University of Minnesota March 2, 2004.
View n A single table derived from other tables which can be a base table or previously defined views n Virtual table: doesn’t exist physically n Limitation.
Distributed DBMS © M. T. Özsu & P. Valduriez Ch.7/1 Outline Introduction Background Distributed Database Design Database Integration Semantic Data Control.
ORACLE DATABASE SECURITY
Switch off your Mobiles Phones or Change Profile to Silent Mode.
Overview of Query Processing
Security+ All-In-One Edition Chapter 19 – Privilege Management Brian E. Brzezicki.
PMIT-6102 Advanced Database Systems By- Jesmin Akhter Assistant Professor, IIT, Jahangirnagar University.
Chapter No 4 Query optimization and Data Integrity & Security.
Academic Year 2014 Spring Academic Year 2014 Spring.
Database Management Systems, 2 nd Edition, R. Ramakrishnan and J. Gehrke1 Security Lecture 17.
Security Models Xinming Ou. Security Policy vs. Security Goals In a mandatory access control system, the system defines security policy to achieve security.
Database Security. Introduction to Database Security Issues (1) Threats to databases Loss of integrity Loss of availability Loss of confidentiality To.
Database Security Database System Implementation CSE 507 Some slides adapted from Navathe et. Al.
PREPARED BY: MS. ANGELA R.ICO & MS. AILEEN E. QUITNO (MSE-COE) COURSE TITLE: OPERATING SYSTEM PROF. GISELA MAY A. ALBANO PREPARED BY: MS. ANGELA R.ICO.
Lecture 2 Page 1 CS 236 Online Security Policies Security policies describe how a secure system should behave Policy says what should happen, not how you.
CS742 – Distributed & Parallel DBMSPage 3. 1M. Tamer Özsu Outline Introduction & architectural issues Data distribution  Distributed query processing.
Database Security Advanced Database Dr. AlaaEddin Almabhouh.
IST 210 Security. IST 210 Introduction to DB Security Secrecy: Users should not be able to see things they are not supposed to. E.g., A student can’t.
Chapter 5 : DataBase Security Lecture #1-Week 8 Dr.Khalid Dr. Mohannad Information Security CIT460 Information Security Dr.Khalid Dr. Mohannad 1.
Chapter 1 Database and Database Users
Database System Implementation CSE 507
Access Control Model SAM-5.
Outline Background Introduction Distributed DBMS Architecture
DISTRIBUTED DATABASE TOP DOWN & DESIGN PERTEMUAN 3
Database Security and Authorization
Computer Data Security & Privacy
DISTRIBUTED DATABASE ARCHITECTURE
Distributed Database Management Systems
Data and Applications Security Developments and Directions
DISTRIBUTED DATABASE BOTTOM UP & DESIGN PERTEMUAN 4
PROGRAM STUDI TEKNIK INFORMATIKA FAKULTAS ILMU KOMPUTER
ER Modeling Exercise Consider a set of courses, both at grad and undergrad level. Each course has at least one section. Each section is taught by only.
PROGRAM STUDI TEKNIK INFORMATIKA FAKULTAS ILMU KOMPUTER
OVERVIEW OF RELATIONAL DBMS PERTEMUAN 1 IR. NIZIRWAN ANWAR, MT
Executive Director and Endowed Chair
Outline Introduction Background Distributed DBMS Architecture
ETHICAL ISSUES IN INFORMATION TECHNOLOGY (CCI410) PERTEMUAN 7
Distributed Database Management Systems
DATABASE SECURITY For CSCL (BIM).
Overview of Database Security
Chapter 5: Confidentiality Policies
Access Control.
Data and Applications Security Developments and Directions
Data and Applications Security Developments and Directions
Data and Applications Security Developments and Directions
Data and Applications Security Developments and Directions
Distributed Database Management Systems
Data and Applications Security Developments and Directions
So What are Views and Triggers anyway?
Distributed Database Design
Distributed Database Management Systems
Data and Applications Security Developments and Directions
Data Independence Applications insulated from how data is structured and stored. Logical data independence: Protection from changes in logical structure.
Data and Applications Security Developments and Directions
Presentation transcript:

DATA ACCESS CONTROL, MANAGEMENT DATA AND SECURITY (CIB125) PERTEMUAN 6 IR. NIZIRWAN ANWAR, MT PROGRAM STUDI TEKNIK INFORMATIKA FAKULTAS ILMU KOMPUTER

Semantic Data Control Involves: View management Security control Integrity control Objective : Insure that authorized users perform correct operations on the database, contributing to the maintenance of the database integrity.

Query Modification View – virtual relation EMP ENO ENAME TITLE E1 J. Doe Elect. Eng View – virtual relation generated from base relation(s) by a query not stored as base relations Example : CREATE VIEW SYSAN(ENO,ENAME) AS SELECT ENO,ENAME FROM EMP WHERE TITLE= "Syst. Anal." E2 M. Smith Syst. Anal. E3 A. Lee Mech. Eng. E4 J. Miller Programmer E5 B. Casey Syst. Anal. E6 L. Chu Elect. Eng. E7 R. Davis Mech. Eng. E8 J. Jones Syst. Anal. ENO ENAME E2 M.Smith E5 B.Casey E8 J.Jones SYSAN

View Management Views can be manipulated as base relations Example : SELECT ENAME, PNO, RESP FROM SYSAN, ASG WHERE SYSAN.ENO = ASG.ENO

View Management To restrict access CREATE VIEW ESAME AS SELECT * FROM EMP E1, EMP E2 WHERE E1.TITLE = E2.TITLE AND E1.ENO = USER Query SELECT * FROM ESAME

Query Modification Queries expressed on views ; Queries expressed on base relations Example : SELECT ENAME, PNO, RESP FROM SYSAN, ASG WHERE SYSAN.ENO = ASG.ENO SELECT ENAME,PNO,RESP FROM EMP, ASG WHERE EMP.ENO = ASG.ENO AND TITLE = "Syst. Anal." ENAME PNO RESP M.Smith P1 Analyst M.Smith P2 Analyst B.Casey P3 Manager J.Jones P4 Manager

Data Security Data protection Prevents the physical content of data to be understood by unauthorized users Uses encryption/decryption techniques (Public key) Access control Only authorized users perform operations they are allowed to on database objects Discretionary access control (DAC) Long been provided by DBMS with authorization rules Multilevel access control (MAC) Increases security with security levels

Discretionary Access Control (DAC) Main actors Subjects (users, groups of users) who execute operations Operations (in queries or application programs) Objects, on which operations are performed Checking whether a subject may perform an op. on an object Authorization= (subject, op. type, object def.) Defined using GRANT OR REVOKE Centralized: one single user class (admin.) may grant or revoke Decentralized, with op. type GRANT More flexible but recursive revoking process which needs the hierarchy of grants

Multilevel Access Control Different security levels (clearances) Top Secret > Secret > Confidential > Unclassified Access controlled by 2 rules: No read up subject S is allowed to read an object of level L only if level(S) ≥ L Protect data from unauthorized disclosure, e.g. a subject with secret clearance cannot read top secret data No write down: subject S is allowed to write an object of level L only if level(S) ≤ L Protect data from unauthorized change, e.g. a subject with top secret clearance can only write top secret data but not secret data (which could then contain top secret data)

Latihan soal Jelaskan konsep fragmentation berdasarkan information requirements dan buat contoh sederhana pada masing approach di bawah ini Primary Horizontal Fragmentation (PHF) Derived Horizontal Fragmentation (DHF)