Why access control protects data in MySQL

Introduction

Access control keeps data safe by letting only the right people see or change it.

When you want to stop strangers from reading private information.

When only certain workers should update company records.

When you want to track who can add or delete data.

When you need to follow rules about data privacy.

When you want to prevent accidental changes by users.

Syntax

MySQL

GRANT privileges ON database.table TO 'user'@'host';
REVOKE privileges ON database.table FROM 'user'@'host';

Use GRANT to give permissions like SELECT, INSERT, UPDATE, DELETE.

Use REVOKE to remove permissions when no longer needed.

Examples

Gives user 'alice' permission to read data from the customers table.

MySQL

GRANT SELECT ON mydb.customers TO 'alice'@'localhost';

Removes permission for user 'bob' to add new orders.

MySQL

REVOKE INSERT ON mydb.orders FROM 'bob'@'localhost';

Gives 'carol' full access to all tables in the mydb database from any host.

MySQL

GRANT ALL PRIVILEGES ON mydb.* TO 'carol'@'%';

Sample Program

This creates a database and table, grants read-only access to 'testuser', and shows the permissions.

MySQL

CREATE DATABASE IF NOT EXISTS mydb;
USE mydb;
CREATE TABLE IF NOT EXISTS customers (
  id INT PRIMARY KEY,
  name VARCHAR(50)
);
GRANT SELECT ON mydb.customers TO 'testuser'@'localhost';
SHOW GRANTS FOR 'testuser'@'localhost';

Important Notes

Always give the least permissions needed to keep data safe.

Access control helps prevent mistakes and attacks on your data.

Summary

Access control limits who can see or change data.

Use GRANT and REVOKE to manage permissions.

Proper access control keeps data safe and trustworthy.

Practice

1. Why is access control important in a MySQL database?

easy

A. It limits who can view or change data, protecting it from unauthorized access.

B. It speeds up query execution by caching results.

C. It automatically backs up the database daily.

D. It formats the data for better display on websites.

Solution

1. Step 1: Understand the purpose of access control

   Access control restricts database access to authorized users only.

2. Step 2: Identify the benefit of restricting access

   By limiting who can view or modify data, it protects data from unauthorized changes or leaks.

3. Final Answer:

   It limits who can view or change data, protecting it from unauthorized access. -> Option A

4. Quick Check:

   Access control = Protects data [OK]

Hint: Access control means who can do what with data [OK]

Common Mistakes:

• Confusing access control with performance features
• Thinking access control handles backups
• Believing access control formats data display

2. Which MySQL command is used to give a user permission to access a database?

easy

A. SELECT

B. REVOKE

C. GRANT

D. DELETE

Solution

1. Step 1: Recall MySQL commands for permissions

   GRANT is used to give permissions; REVOKE removes them.

2. Step 2: Identify the command that grants access

   GRANT assigns privileges to users to access or modify data.

3. Final Answer:

   GRANT -> Option C

4. Quick Check:

   GRANT = Give permission [OK]

Hint: GRANT gives access, REVOKE removes it [OK]

Common Mistakes:

• Confusing GRANT with REVOKE
• Choosing data manipulation commands like SELECT or DELETE
• Thinking SELECT grants permissions

3. Given the commands:
GRANT SELECT ON employees TO 'user1'@'localhost';
REVOKE INSERT ON employees FROM 'user1'@'localhost';
What can 'user1' do on the employees table?

medium

A. No permissions at all

B. Only select (read) data from employees

C. Both select and insert data

D. Insert new data but cannot read data

Solution

1. Step 1: Analyze the GRANT command

   GRANT SELECT allows user1 to read data from employees table.

2. Step 2: Analyze the REVOKE command

   REVOKE INSERT removes insert permission, so user1 cannot add data.

3. Final Answer:

   Only select (read) data from employees -> Option B

4. Quick Check:

   GRANT SELECT + REVOKE INSERT = Read only [OK]

Hint: GRANT adds, REVOKE removes permissions [OK]

Common Mistakes:

• Assuming REVOKE removes all permissions
• Thinking user1 can insert data
• Confusing SELECT with INSERT permission

4. A database admin runs:
GRANT SELECT ON sales TO 'user2'@'%';
REVOKE SELECT ON sales FROM 'user2'@'%';
But user2 can still read the sales table. What is the likely problem?

medium

A. User2 has SELECT permission from another host or user entry.

B. The REVOKE command syntax is incorrect.

C. MySQL does not support REVOKE for SELECT.

D. User2 needs to restart the database to update permissions.

Solution

1. Step 1: Understand permission scope in MySQL

   Permissions are granted per user and host combination.

2. Step 2: Identify why REVOKE may not work as expected

   If user2 has another entry with SELECT permission from a different host, that permission remains.

3. Final Answer:

   User2 has SELECT permission from another host or user entry. -> Option A

4. Quick Check:

   Multiple user entries can override REVOKE [OK]

Hint: Check all user@host entries for permissions [OK]

Common Mistakes:

• Assuming REVOKE syntax is wrong without checking user entries
• Believing REVOKE is unsupported for SELECT
• Thinking a database restart is needed for permission changes

5. You want to ensure only the HR team can update employee salaries in MySQL. Which approach best protects this sensitive data?

hard

A. Grant all permissions to everyone and rely on application checks.

B. Allow all users to SELECT and UPDATE salaries for transparency.

C. Do not use any access control and trust users to behave.

D. Grant UPDATE permission on salaries table only to HR users, revoke from others.

Solution

1. Step 1: Identify the need for restricted update access

   Only HR should modify salaries to protect sensitive data.

2. Step 2: Apply access control best practice

   Grant UPDATE permission only to HR users and revoke from others to enforce this.

3. Final Answer:

   Grant UPDATE permission on salaries table only to HR users, revoke from others. -> Option D

4. Quick Check:

   Restrict update rights to protect sensitive data [OK]

Hint: Limit update rights to trusted users only [OK]

Common Mistakes:

• Giving update rights to all users
• Relying only on application-level checks
• Ignoring access control for sensitive tables