Security and Authorization

Chapter 21

Database Management Systems, 3ed, R. Ramakrishnan and J. Gehrke

1

Introduction to DB Security

Secrecy: Users should not be able to see things they are not supposed to.

E.g., A student can‟t see other students‟ grades.

Integrity: Users should not be able to modify things they are not supposed to.

E.g., Only instructors can assign grades.

Availability: Users should be able to see and modify things they are allowed to.

Database Management Systems, 3ed, R. Ramakrishnan and J. Gehrke

2

 Two main mechanisms at the DBMS level:    Discretionary access control Mandatory access control Database Management Systems.  A security mechanism allows us to enforce a chosen security policy. 3ed. Gehrke 3 . Ramakrishnan and J. R.Access Controls A security policy specifies who is authorized to do what.

3ed.   DMBS keeps track of who subsequently gains and loses privileges.  Creator of a table or a view automatically gets all privileges on it. and mechanisms for giving users privileges (and revoking privileges). and ensures that only requests from users who have the necessary privileges (at the time the request is issued) are allowed. Gehrke . R. 4 Database Management Systems.Discretionary Access Control Based on the concept of access rights or privileges for objects (tables and views). Ramakrishnan and J.

REFERENCES (col-name): Can define foreign keys (in other tables) that refer to this column. DELETE: Can delete tuples. 3ed. INSERT(col-name): Can insert tuples with non-null or non- default values in this column.    INSERT means same right with respect to all columns. 5 Database Management Systems. ALTER. Gehrke . R.   If a user has a privilege with the GRANT OPTION. Ramakrishnan and J.GRANT Command GRANT privileges ON object TO users [WITH GRANT OPTION]  The following privileges can be specified:   SELECT: Can read all columns (including those added later via ALTER TABLE command). can pass privilege on to other users (with or without passing on the GRANT OPTION). and DROP. Only owner can execute CREATE.

R. Database Management Systems. GRANT SELECT ON ActiveSailors TO Guppy.  GRANT DELETE ON Sailors TO Yuppy WITH GRANT OPTION  Yuppy can delete tuples.GRANT and REVOKE of Privileges  GRANT INSERT. Gehrke 6 . GRANT UPDATE (rating) ON Sailors TO Dustin  Dustin can update (only) the rating field of Sailors tuples. it is    also revoked from all users who got it solely from X. Ramakrishnan and J. SELECT ON Sailors TO Horatio  Horatio can query Sailors or insert tuples into it. 3ed. and also authorize others to do so. Yuppy  This does NOT allow the „uppies to query Sailors directly! REVOKE: When a privilege is revoked from X.

so do users who were granted that privilege on the view!  Database Management Systems. (s)he loses the privilege on the view as well. Ramakrishnan and J. 3ed. Gehrke 7 . R. the view is dropped!  If the creator of a view loses a privilege held with the grant option on an underlying table.GRANT/REVOKE on Views If the creator of a view loses the SELECT privilege on an underlying table.

 Together with GRANT/REVOKE commands. 3ed.  Database Management Systems. but not Sailors or Reserves. views are a very powerful access control tool. we can find sailors who have a reservation. Creator of view has a privilege on the view if (s)he has the privilege on all underlying tables. R. Ramakrishnan and J.  Given ActiveSailors.Views and Security  Views can be used to present necessary information (or a summary). but not the bid‟s of boats that have been reserved. while hiding details in underlying relation(s). Gehrke 8 .

Role-Based Authorization In SQL-92.     Roles can then be granted to users and to other roles. 9 Database Management Systems. R. 3ed. privileges are assigned to roles. Ramakrishnan and J. Illustrates how standards often catch up with “de facto” standards embodied in popular systems. which can denote a single user or a group of users.  In SQL:1999 (and in many current systems). privileges are actually assigned to authorization ids. Gehrke . Reflects how real organizations work.

3ed. Gehrke . (How?)  Then grant access to that view accordingly. (Too many view creations and look-ups. though this can be hidden under a good UI Performance is unacceptable if we need to define field-granularity access frequently. Ramakrishnan and J. but:    Clumsy to specify.Security to the Level of a Field! Can create a view that only returns one field of one tuple.  Allows for arbitrary granularity of control. R.) 10 Database Management Systems.

11 Database Management Systems. and not some rogue site spoofing you (to steal such information)? How can he be sure that sensitive information is not “sniffed” while it is being sent over the network to you?  Encryption is a technique used to address these issues. passwordbased schemes are usually adequate.  When DB must be accessed from a secure location. trust is hard to achieve. Ramakrishnan and J. Gehrke . R.  For access over an external network.Internet-Oriented Security  Key Issues: User authentication and trust.  If someone with Sam‟s credit card wants to buy from you. 3ed. how can you be sure it is not someone who stole his card?  How can Sam be sure that the screen for entering his credit card information is indeed yours.

encryption key) = encrypted data  Decrypt(encrypted data. R.  DES. decryption key) = original data  Without decryption key. Gehrke 12 . 3ed. AES has 128-bit (optionally. the encrypted data is meaningless gibberish  Encryption key = decryption key. all authorized users know decryption key (a weakness). 192-bit or 256-bit) key  User‟s public encryption key: Known to all  Decryption key: Known only to this user  Used in RSA scheme (Turing Award!)  Symmetric Encryption:  Public-Key Encryption: Each user has two keys: Database Management Systems. used since 1977. Ramakrishnan and J.Encryption  “Masks” data for secure transmission or storage  Encrypt(data. has 56-bit key.

distinct prime numbers Encryption: Choose a random number 1 < e < L that is relatively prime to (p-1) * (q-1)  Encrypted data S = I e mod L  d * e = 1 mod ((p-1) * (q-1))  We can then show that I = S d mod L  Decryption key d: Chosen so that  It turns out that the roles of e and d can be reversed. Ramakrishnan and J. say 1024-bit. R.RSA Public-Key Encryption    Let the data be an integer I Choose a large (>> I) integer L = p * q  p. 3ed. Gehrke 13 . q are large. so they are simply called the public and private keys Database Management Systems.

3ed. amazon.Certifying Servers: SSL. Amazon. and sends it to Amazon.  Verisign‟s public key is known to all browsers. and be confident that it is genuine. only Amazon can decipher the order. encrypted with Verisign‟s private key. Sam‟s browser will encrypt his order using it..g. which can therefore decrypt the certificate and obtain Amazon‟s public key. say.  Amazon contracts with. Verisign. and a trusted server. Gehrke 14 ..  All subsequent msgs between the browser and Amazon are encoded using symmetric encryption (e.g. But how can Sam (or his browser) know that the public key for Amazon is genuine? The SSL protocol covers this. which is more efficient than public-key encryption. public-key>  This certificate is stored in encrypted form. SET  If Amazon distributes their public key. to issue a certificate <Verisign.  So. Database Management Systems. e. since no one else has Amazon‟s private key. Sam. Visa.  The browser then generates a temporary session key. R.com. DES). Ramakrishnan and J. encodes it using Amazon‟s public key.   What if Sam doesn‟t trust Amazon with his credit card information?  Secure Electronic Transaction protocol: 3-way communication between Amazon. known only to Verisign.

3ed.  Done after SSL is used to establish a session key..e. Gehrke 15 . ask Sam to log into his Amazon account.Authenticating Users  Amazon can simply use password authentication. then encrypts the result using Amazon‟s public key. and then decrypts the result using Sam‟s public key. i. Database Management Systems. so that the transmission of the password is secure!  Amazon is still at risk if Sam‟s card is stolen and his password is hacked. no one can forge Sam‟s order. which yields the original order!  Exploits interchangeability of public/private keys for encryption/decryption  Now. Ramakrishnan and J. Business risk …  Digital Signatures:  Sam encrypts the order using his private key.  Amazon decrypts the msg with their private key. R. and Sam cannot claim that someone else forged the order.

Versions of some DBMSs do support it.g. Rules based on security classes and clearances govern who can read/write which objects. military) applications. Database Management Systems. Each subject (user or user program) is assigned a clearance for a security class. Gehrke 16 . 3ed. R. used for specialized (e.  Most commercial systems do not support mandatory access control. Ramakrishnan and J.Mandatory Access Control  Based on system-wide policies that cannot be changed by individual users.    Each DB object is assigned a security class..

e. 3ed..  The modification of the code is beyond the DBMSs control. Database Management Systems.Why Mandatory Control?  Discretionary control has some flaws. but it can try and prevent the use of the database as a channel for secret information. the Trojan horse problem:    Dick creates Horsie and gives INSERT privileges to Justin (who doesn‟t know about this).g. Dick modifes the code of an application program used by Justin to additionally write some secret data to table Horsie. R. Justin can see the secret info. Now. Gehrke 17 . Ramakrishnan and J.

user programs)  Security classes:   Top secret (TS). views. confidential (C).g. users. Ramakrishnan and J..   Database Management Systems. secret (S).Bell-LaPadula Model Objects (e. tables. Gehrke . 3ed. R.g.. tuples)  Subjects (e. unclassified (U): TS > S> C > U Subject S can read object O only if class(S) >= class(O) (Simple Security Property) Subject S can write object O only if class(S) <= class(O) (*-Property) 18  Each object and subject is assigned a class.

Justin has class S. R. 3ed.Intuition   Idea is to ensure that information can never flow from a higher to a lower security level. C. has Dick‟s clearance.  The mandatory access control rules are applied in addition to any discretionary controls that are in effect. Justin‟s application has his clearance. Gehrke . 19 Database Management Systems. If Dick has security class C. the program cannot write into table Horsie. E. and the secret table has class S:    Dick‟s table. So. Ramakrishnan and J.g.. Horsie. S.

a user with U will see no rows.Pasta. 3ed. Gehrke . 20 Database Management Systems.C>:    Allowing insertion violates key constraint Disallowing insertion tells user that there is another object with key 101 that has a class > C! Problem resolved by treating class field as part of key. R.  If user with C tries to insert <101. Ramakrishnan and J.Multilevel Relations bid 101 102  bname Salsa Pinto color Red Brown class S C Users with S and TS clearance will see both rows. a user with C will only see the 2nd row.Blue.

. but allows only aggregate queries (e. R. for some N.g. 3ed. I can ask “How many sailors are older than X?” for different values of X until I get the answer 1.  Idea: Insist that each query must involve at least N rows.g. rather than Joe‟s age). If I know Joe is the oldest sailor. Ramakrishnan and J. Will this work? (No!) 21 Database Management Systems..Statistical DB Security Statistical DB: Contains information about individuals. Gehrke .  New problem: It may be possible to infer some secret information!   E. average age. this allows me to infer Joe‟s age.

 Next. Gehrke 22 .  S1-S2 is Joe‟s age!  Database Management Systems. ask “What is the sum of ages of sailors older than X?” Let result be S1.Why Minimum N is Not Enough By asking “How many sailors older than X?” until the system rejects the query. 3ed. R. Ramakrishnan and J. that are older than X. plus my age?” Let result be S2.  Next. including Joe. ask “What is sum of ages of sailors other than Joe who are older than X. let X=55 at this point. can identify a set of N sailors.

integrity.  Designs security policy. maintains an audit trail.  Two main approaches to DBMS security: discretionary and mandatory access control. 3ed. Gehrke .Summary   Three main security objectives: secrecy. R. DB admin is responsible for overall security. but often.   Discretionary control based on notion of privileges. 23 Database Management Systems. individual information can be inferred. or history of users‟ accesses to DB. Ramakrishnan and J. Mandatory control based on notion of security classes. availability.  Statistical DBs try to protect individual data by supporting only aggregate queries.