1 / 13

Example: http://www.oreilly.com/catalog/orasec/chapter/ch07.html

Designing Security. Example: http://www.oreilly.com/catalog/orasec/chapter/ch07.html. Database Security Plan. Security Models. One Matrix per Database Access Matrix Model: Harrison-Ruzzo-Ullman Authorized state: Q = (S, O, A) Conditions (dependent) Data Time Context History.

zudora
Download Presentation

Example: http://www.oreilly.com/catalog/orasec/chapter/ch07.html

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. Designing Security Example: http://www.oreilly.com/catalog/orasec/chapter/ch07.html Database Security Plan

  2. Security Models One Matrix per Database • Access Matrix Model: Harrison-Ruzzo-Ullman • Authorized state: Q = (S, O, A) • Conditions (dependent) • Data • Time • Context • History Subjects Objects

  3. Matrix

  4. More Matrix

  5. CIA • All Databases are concerned with: • Confidentiality • Integrity • Availability However, for one organization, one of these may stand out more.

  6. MAC: Bell-La Padula O5 S2 O4 O3 S3 S1 O2 O6 O1 NO Read up, No write Down High Secure Flow of Information write read read Sensitivity of objects Trust of subjects write(if no read access to higher sensitivity data) write write read Low read Source: Charles Pfleeger in Security in Computing, 2nd ed.Prentice-Hall PTR 1996

  7. Multilevel Security • Information has different classifications • Users have different security clearances • Purpose: separate data based on its classification • Mandatory Access Control (MAC): security enforced by system and not by the user. • Polyinstantiation: multiple rows with same PK. Instances distinguished by security level.

  8. Example Multilevel Relation TS > S > C> U

  9. Problem with Multilevel Security • It is really multiple instantiations of single-level DBMS, which strongly degrades performance. • Examples: Trusted Oracle, DB2 for z/OS, Informix OnLine/Secure, Sybase secure system

  10. Oracle Label Security: • simulates multilevel db. • Adds a field for each row to store the row’s sensitive label. • Access is granted (or denied) comparing user’s identity and security clearance label with row’s sensitive label. • More flexible. Can be used with VPD.

  11. End of Lecture End Of Today’s Lecture.

More Related