Security best practices in Laravel - Mini Project: Build & Apply

Security Best Practices in Laravel

📖 Scenario: You are building a simple Laravel web application that handles user registration and login. To keep user data safe, you need to apply basic security best practices in your code.

🎯 Goal: Learn how to implement essential security best practices in Laravel, including input validation, password hashing, and protection against common vulnerabilities.

📋 What You'll Learn

Create a user registration array with sample user data

Add a configuration variable for minimum password length

Hash the user password before saving

Use Laravel's built-in CSRF protection in a form

💡 Why This Matters

🌍 Real World

Web applications must protect user data and prevent attacks like CSRF and password theft. These practices help keep apps safe.

💼 Career

Understanding Laravel security basics is essential for backend developers to build secure and trustworthy applications.

1

Create User Data Array

Create an array called $userData with these exact entries: 'name' => 'John Doe', 'email' => '[e-mail]', and 'password' => 'secret123'.

Laravel

<?php
// Create the user data array
# Your code here

Hint

Use PHP array syntax with keys and values exactly as shown.

2

Add Password Length Configuration

Add a variable called $minPasswordLength and set it to 8 to define the minimum password length requirement.

Laravel

 'John Doe', 'email' => '[e-mail]', 'password' => 'secret123'];
// Define minimum password length
# Your code here

Hint

Just create a simple integer variable for the password length.

3

Hash the User Password

Use Laravel's Hash::make() method to hash the password in $userData['password'] and update it with the hashed value.

Laravel

 'John Doe', 'email' => '[e-mail]', 'password' => 'secret123'];
$minPasswordLength = 8;
// Hash the password using Hash::make()
# Your code here

Hint

Remember to import the Hash facade and then call Hash::make() on the password.

4

Add CSRF Protection to Form

In a Blade template, add the @csrf directive inside the <form> tag to enable Laravel's CSRF protection.

Laravel

 'John Doe', 'email' => '[e-mail]', 'password' => 'secret123'];
$minPasswordLength = 8;
$userData['password'] = Hash::make($userData['password']);

// Blade template form
?>
    
    # Your code here

Hint

Use the @csrf directive exactly inside the form tag.

Practice

1. Which Laravel feature helps protect your application from Cross-Site Request Forgery (CSRF) attacks?

easy

A. Storing passwords in plain text

B. Using raw SQL queries without bindings

C. CSRF tokens automatically added to forms

D. Disabling middleware in routes

Solution

1. Step 1: Understand CSRF attacks

   CSRF attacks trick users into submitting unwanted requests. Laravel uses tokens to prevent this.

2. Step 2: Identify Laravel's protection method

   Laravel automatically adds CSRF tokens to forms and verifies them on submission.

3. Final Answer:

   CSRF tokens automatically added to forms -> Option C

4. Quick Check:

   CSRF protection = CSRF tokens [OK]

Hint: CSRF protection means using tokens in forms [OK]

Common Mistakes:

• Thinking raw SQL protects against CSRF
• Disabling middleware removes security
• Storing passwords in plain text is unsafe

2. Which of the following is the correct way to hash a password before saving it in Laravel?

easy

A. $hashed = Hash::make($password);

B. $hashed = bcrypt($password);

C. $hashed = md5($password);

D. $hashed = base64_encode($password);

Solution

1. Step 1: Identify Laravel's recommended password hashing

   Laravel provides the Hash facade's make method for secure password hashing.

2. Step 2: Compare options

   $hashed = Hash::make($password); is the recommended and most flexible method. bcrypt() helper is valid but less flexible. md5 and base64_encode are insecure.

3. Final Answer:

   $hashed = Hash::make($password); -> Option A

4. Quick Check:

   Password hashing = Hash::make() [OK]

Hint: Use Hash::make() for password hashing in Laravel [OK]

Common Mistakes:

• Using insecure md5 or base64_encode
• Confusing Hash::make without import
• Saving passwords without hashing

3. Consider this Laravel route definition:

Route::middleware(['auth'])->group(function () {
    Route::get('/dashboard', function () {
        return 'Welcome to your dashboard';
    });
});

What will happen if a guest (not logged in) tries to access /dashboard?

medium

A. They will see the dashboard message

B. They will be redirected to the login page

C. They will get a 404 Not Found error

D. They will see a blank page

Solution

1. Step 1: Understand the 'auth' middleware

   The 'auth' middleware restricts access to authenticated users only.

2. Step 2: Behavior for guests

   If a guest tries to access a route with 'auth' middleware, Laravel redirects them to the login page.

3. Final Answer:

   They will be redirected to the login page -> Option B

4. Quick Check:

   Auth middleware redirects guests [OK]

Hint: Auth middleware redirects guests to login [OK]

Common Mistakes:

• Assuming guests see the dashboard
• Expecting 404 error instead of redirect
• Thinking middleware shows blank page

4. This Laravel controller method is intended to validate user input securely:

public function store(Request $request) {
    $data = $request->validate([
        'email' => 'required|email',
        'password' => 'required|min:8'
    ]);
    User::create($data);
}

What is the main security issue here?

medium

A. Passwords are not hashed before saving

B. Email validation rule is incorrect

C. Validation rules are missing CSRF token check

D. User::create() should be User::update()

Solution

1. Step 1: Check validation rules

   The validation correctly checks email and password format.

2. Step 2: Check password handling

   The password is saved directly without hashing, which is insecure.

3. Final Answer:

   Passwords are not hashed before saving -> Option A

4. Quick Check:

   Passwords must be hashed before saving [OK]

Hint: Always hash passwords before saving to database [OK]

Common Mistakes:

• Assuming validation hashes passwords
• Confusing CSRF with validation rules
• Thinking create() vs update() affects security here

5. You want to protect an API route in Laravel so only authenticated users with the role 'admin' can access it. Which is the best approach?

hard

A. Use 'auth' middleware and check role inside the controller method

B. Use 'guest' middleware and check role in middleware

C. No middleware needed; check role in the route definition

D. Use 'auth' middleware and create a custom middleware to check 'admin' role

Solution

1. Step 1: Understand middleware roles

   'auth' middleware ensures user is logged in; role checks require custom logic.

2. Step 2: Best practice for role checks

   Create a custom middleware to check if the authenticated user has 'admin' role, then apply both middlewares.

3. Final Answer:

   Use 'auth' middleware and create a custom middleware to check 'admin' role -> Option D

4. Quick Check:

   Combine auth + custom role middleware [OK]

Hint: Combine auth middleware with custom role middleware [OK]

Common Mistakes:

• Using 'guest' middleware for authenticated routes
• Checking roles only inside controller
• Skipping middleware for role checks