Security best practices in Ruby on Rails

Introduction

Security best practices help keep your Rails app safe from hackers and mistakes. They protect user data and your app's trust.

When building a web app that handles user login and personal data

When accepting input from users like forms or URLs

When deploying your app to the internet

When adding new features that interact with databases or files

When updating Rails or gems to avoid security holes

Syntax

Ruby on Rails

# Example: Using strong parameters in a controller
params.require(:user).permit(:name, :email, :password)

Use strong parameters to allow only safe data from users.

Always validate and sanitize user input to avoid attacks.

Examples

Escape user data before showing it in HTML to stop bad scripts.

Ruby on Rails

# Prevent Cross-Site Scripting (XSS) by escaping output in views
<%= h @user.name %>

Encrypt data sent between users and your app to keep it private.

Ruby on Rails

# Use HTTPS by forcing SSL in production
config.force_ssl = true

Never build SQL queries by hand with user input; use Rails methods.

Ruby on Rails

# Protect against SQL Injection by using ActiveRecord queries
User.where(email: params[:email])

Stop attackers from tricking users into submitting unwanted requests.

Ruby on Rails

# Enable CSRF protection in ApplicationController
protect_from_forgery with: :exception

Sample Program

This controller safely handles user creation by using strong parameters and CSRF protection. It only allows specific fields and stops forged requests.

Ruby on Rails

class UsersController < ApplicationController
  protect_from_forgery with: :exception

  def create
    user_params = params.require(:user).permit(:name, :email, :password)
    @user = User.new(user_params)
    if @user.save
      redirect_to @user, notice: "User created safely!"
    else
      render :new
    end
  end
end

Important Notes

Always keep Rails and gems updated to get security fixes.

Use environment variables for secrets, not hard-coded values.

Test your app for security issues regularly using tools or audits.

Summary

Use strong parameters to control user input.

Enable CSRF protection to stop fake requests.

Escape output and use HTTPS to protect data.

Practice

1. Which Rails feature helps prevent unwanted or dangerous user input from being saved to the database?

easy

A. Strong Parameters

B. Active Record Callbacks

C. Action Mailer

D. Asset Pipeline

Solution

1. Step 1: Understand user input control

   Strong Parameters allow you to specify which attributes are allowed from user input, preventing mass assignment vulnerabilities.

2. Step 2: Identify the correct Rails feature

   Active Record Callbacks and others do not control input filtering; only Strong Parameters do.

3. Final Answer:

   Strong Parameters -> Option A

4. Quick Check:

   User input filtering = Strong Parameters [OK]

Hint: Strong Parameters filter user input safely [OK]

Common Mistakes:

• Confusing callbacks with input filtering
• Thinking Asset Pipeline handles security
• Assuming Action Mailer controls input

2. Which line correctly enables CSRF protection in a Rails controller?

easy

A. enable_csrf_protection!

B. protect_from_forgery with: :exception

C. csrf_protect true

D. use_csrf_protection = true

Solution

1. Step 1: Recall Rails CSRF protection syntax

   The correct method to enable CSRF protection is protect_from_forgery with: :exception in controllers.

2. Step 2: Check other options for validity

   Other options are not valid Rails syntax and will cause errors or have no effect.

3. Final Answer:

   protect_from_forgery with: :exception -> Option B

4. Quick Check:

   CSRF protection syntax = protect_from_forgery [OK]

Hint: Use protect_from_forgery with: :exception [OK]

Common Mistakes:

• Using non-existent methods for CSRF
• Forgetting to add CSRF protection
• Misnaming the method or options

3. Given this Rails view code:

<%= raw @user.name %>

What security risk exists if @user.name contains HTML tags?

medium

A. Cross-Site Scripting (XSS) attack

B. SQL Injection

C. Mass Assignment

D. Denial of Service

Solution

1. Step 1: Understand output escaping in Rails views

   Using <%= %> escapes HTML by default, but if raw HTML is inserted, it can cause XSS.

2. Step 2: Identify the risk of unescaped HTML in user input

   If @user.name contains HTML tags and is not escaped, it can run malicious scripts in the browser, causing XSS.

3. Final Answer:

   Cross-Site Scripting (XSS) attack -> Option A

4. Quick Check:

   Unescaped HTML in views = XSS risk [OK]

Hint: Unescaped user input risks XSS attacks [OK]

Common Mistakes:

• Confusing XSS with SQL Injection
• Assuming Rails never escapes output
• Ignoring HTML tags in user input

4. You see this code in a Rails controller:

params.require(:user).permit(:name, :email)

But users report they can update admin-only fields. What is the likely problem?

medium

A. CSRF protection is disabled

B. The controller action is missing

C. Strong Parameters are not used correctly

D. The database schema is incorrect

Solution

1. Step 1: Analyze the use of Strong Parameters

   The code shows permitted params, but if the controller does not use this filtered params hash for updating, mass assignment can happen.

2. Step 2: Identify why admin-only fields update

   If the controller uses unfiltered params or merges extra params, Strong Parameters are bypassed, causing security issues.

3. Final Answer:

   Strong Parameters are not used correctly -> Option C

4. Quick Check:

   Mass assignment issue = incorrect Strong Parameters use [OK]

Hint: Always use filtered params for updates [OK]

Common Mistakes:

• Assuming CSRF causes mass assignment
• Ignoring how params are passed to update
• Blaming database instead of controller code

5. You want to ensure all Rails app traffic is secure and user data is protected. Which combination of practices is best?

hard

A. Only use HTTPS and ignore CSRF and output escaping

B. Disable CSRF protection, use HTTP, and sanitize database inputs

C. Use HTTP, skip escaping output, and rely on user validation

D. Force HTTPS, enable CSRF protection, and escape all output

Solution

1. Step 1: Identify key security practices for web apps

   Forcing HTTPS encrypts data in transit, CSRF protection stops fake requests, and escaping output prevents XSS.

2. Step 2: Evaluate each option's security coverage

   Force HTTPS, enable CSRF protection, and escape all output covers all three essential protections. Others disable or ignore important protections, increasing risk.

3. Final Answer:

   Force HTTPS, enable CSRF protection, and escape all output -> Option D

4. Quick Check:

   HTTPS + CSRF + escaping = best security [OK]

Hint: Combine HTTPS, CSRF, and escaping for strong security [OK]

Common Mistakes:

• Ignoring CSRF protection importance
• Thinking HTTPS alone is enough
• Skipping output escaping