IT360 Lab 10 Database Security
DUE: April 9, 2010, BEFORE start of lab
This lab is a collection of database security concepts. You will see how to give others access to your data, ensure that passwords are encrypted, and use session variables for secure access to your web site. Open a document and call it yourlastname_Lab10.txt. You will place all your answers to the lab questions in this document.
As a database user, you currently have a username (mxxxxxx), password, and you have the rights (permissions) to a particular database (mxxxxxx) where you can create tables, insert into them, etc. Assume now that you are a database administrator, and you are the one giving permissions to users to use the database. For security reasons, you should restrict access to your database as much as possible, and only give permissions that are really needed in order to accomplish the task. We'll accomplish this through the use of the SQL GRANT statement.
Now, let's take a look at this statement line-by-line. The first line, GRANT <permissions>, allows us to specify the specific permissions we are granting. These can be either table-level permissions (such as SELECT, INSERT, UPDATE and DELETE) or database permissions (such as CREATE TABLE, DROP TABLE, ALTER DATABASE, GRANT, etc). More than one permissions can be granted in a single GRANT statement, but table-level permissions and database-level permissions may not be combined in a single statement.
The second line, ON <table>, is used to specify the affected table for table-level permissions. Use the format database.table(s). This line is omitted if we are granting database-level permissions. The third line specifies the user that is being granted permissions.
Try it out by Granting SELECT on your songs table to a partner.
1. What does the GRANT statement look like?
2. When they log into MySQL after this statement is invoked, what has changed?
3. What happens when they run a SELECT statement on the table?
4. What happens when they try to INSERT a new song into the database?
Part 2 Application Security: Protecting Passwords
SHA Hashing: Modify userPage.php downloaded from the course calendar to add an “add user” button. When clicked, the “addUser” function in user.inc.php should be invoked.
Add a line in addUser function in user.inc.php to encrypt the password received by using the php function sha1( ), which returns the calculated sha1 hash of $str
pstring sha1 ( string $str )
Now modify the “validate” function in user.inc.php to check against this new sha1 value. Check your MySQL database and see that the passwords are no longer saved in the clear.
5. How does this change the response to a user’s question: I forgot my password, can you tell me what it is?”
Part 3 Application Security: Session Variables
Remember the song website we started to create in class. I added to it code that allows users to log on to vote for their favorite song. Only valid users should be able to see the list of songs, but try to access the songPage.php without logging in (without going to userPage.php first).
Correct the file songPage.php to ensure that only valid users (ie. those who have logged in properly and have had the appropriate session variable set) will be able to see the page content.
Extra credit: Secure Sockets Layer: Many of us have begun to use online banking. Go to the homepage for Navy Federal Credit Union at http://www.navyfcu.org. Note that the text boxes on the left are similar to the login screen that you created in a previous lab and project. Click on the “Security” link. Use any resource you would like and research how the server and client communicate during the session set up process for SSL (Chapter 18 in the “PHP and MySQL Web Development” book might help).
Finally: Make sure you incorporate these “best practices” into your project. This means adding the appropriate test cases for SQL injects, checking session variables before page displays and saving all passwords as hashed values. We will not be using SSL for this course, but in the real world, you would also make sure to use SSL for appropriate secure transactions (ie, logins and passing of account information).
Turn in (due before start of lab on April 9, 2010):