[Recommended]Database Security EXPERT ONLY

Database Security EXPERT ONLY 1) Create an OLS policy that will accomplish the following: a. The policy is named OLS, with a column_name of ZZ…

Database Security EXPERT ONLY
1) Create an OLS policy that will accomplish the following:
a. The policy is named OLS, with a column_name of ZZ with READ_CONTROL;
b. The Security Levels allowed in the policy are as required to implement the hierarchical levels in the above table (i.e., Levels of U, C, S, and TS)
c. The Data Labels are as required to implement the policy for the above table (Data Labels of U, C, S, and TS); e.g., the data label 100 for unclassified. That the Users (all of the users; i.e., ADAMS, BAKER, CHUCK, DONNER) are created as indicated in the above table and given the DAC rights necessary to access the above table (e.g., Create User ADAMS identified by A; Grant Create Session to ADAMS, Grant Select on Employee to ADAMS);
d. That the Users have the MAC rights as indicated in the above table (the Level for ADAMS is U, the Level of BAKER is C, the Level for CHUCK is S, the Level for DONNER is TS
e. That the OLS policy created is applied to the Above table (i.e., the OLS policy OLS is applied to the EMPLOYEE table. (NOTE: You can do steps a-e above before or after you create the Employee table. But you have to have the Employee table before you do f. I recommend that you create the table but DON’T insert the records in the table until the policy is applied to the table. When you create table DO NOT create the attribute ZZ. Create that table with the attributes as follows: SSN, Name, Salary, DN. The reason for this is that you cannot insert the records in the table with the labels until after you apply the label policy to the table. If you do create the records in the table before you apply the label policy none of the rows will have labels. When you apply the policy to the table another attribute will be added to the table, the ZZ attribute! Now you can insert the records (ANOTHER HINT; WHEN YOU INSERT THE ATTRIBUTE REMEMBER THAT THE LEVEL IS INSERTED BY ITS NUMBER, e.g, when you create the Unclassified level, U, you gave it a data tag of 100 — CREATE_LABEL(‘OLS’, 100, ‘U’); you insert it with the value 100; INSERT INTO EMPLOYEE VALUES (5, ‘ELF’, 40000, ‘C500’, 100);
2) After all parts of 1 are completed; insert the 4 rows indicated above into the above table AND connect in turn as ADAMS, BAKER, CHUCK, AND DONNER DO A SELECT ON THE EMPLOYEE TABLE. (REMBER IF YOU CREATE THE EMPLOYEE TABLE AS db668a09 and are referencing the table as ADAMS you would Select * from db668a09.Employee; When you do this you should get one record for ADAMS, 2 records for BAKER, 3 for CHUCK and 4 for DONNER. Each User sees the records at his level and of all the levels below.
Example
1) SQL> connect adams/a
2) Connected.
3) SQL> select * from michael.employee;
4)
5) SSN NAME SALARY DN ZZ
6) ———- —— ———- —- ———-
7) 1 ADAMS 20000 C100 100
8)
9) SQL> connect baker/b
10) Connected.
11) SQL> select * from michael.employee;
12)
13) SSN NAME SALARY DN ZZ
14) ———- —— ———- —- ———-
15) 1 ADAMS 20000 C100 100
16) 2 BAKER 45000 C200 200
attachment
Lab3Part2.doc
attachment
Session9.1.ppt

The post Database Security EXPERT ONLY appeared first on ExpertCustomWritings.
Assignment status: Solved by our experts

>>>Click here to get this paper written at the best price. 100% Custom, 0% plagiarism.<<<

Leave a Reply

Your email address will not be published. Required fields are marked *