Why Redis security matters - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set a password for Redis.

Redis

requirepass [1]

Drag options to blanks, or click blank then click option'

A6379

Blocalhost

Credis

Dmypassword

Attempts:

3 left

💡 Hint

Common Mistakes

Using the port number or hostname as password

Leaving password empty

Setting requirepass with a password protects Redis from unauthorized access.

2fill in blank

medium

Complete the command to connect to Redis with authentication.

Redis

redis-cli -a [1]

Drag options to blanks, or click blank then click option'

Amypassword

Blocalhost

C6379

Dauth

Attempts:

3 left

💡 Hint

Common Mistakes

Using hostname or port instead of password

Omitting the password

The -a option is used to provide the password when connecting to Redis.

3fill in blank

hard

Fix the error in the Redis config line to disable external access.

Redis

bind [1]

Drag options to blanks, or click blank then click option'

A0.0.0.0

Blocalhost

C127.0.0.1

D::

Attempts:

3 left

💡 Hint

Common Mistakes

Binding to all interfaces

Using hostname instead of IP

Binding Redis to 127.0.0.1 restricts access to the local machine only, improving security.

4fill in blank

hard

Fill both blanks to configure Redis to require password and bind only locally.

Redis

bind [1]
requirepass [2]

Drag options to blanks, or click blank then click option'

A127.0.0.1

Bmypassword

C0.0.0.0

Dpassword123

Attempts:

3 left

💡 Hint

Common Mistakes

Using public IP for bind

Leaving password blank

Binding to 127.0.0.1 restricts access to local machine and setting requirepass enforces authentication.

5fill in blank

hard

Fill all three blanks to create a Redis ACL user with password and limited commands.

Redis

ACL SETUSER [1] on >[2] ~* +[3]

Drag options to blanks, or click blank then click option'

Areadonly

Breadonlypass

Cget

Dallcommands

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'allcommands' instead of specific commands

Omitting password

Wrong user name

This command creates a user named readonly with password readonlypass and allows only the get command.

Practice

1. Why is it important to secure your Redis server?
redis stores data that could be sensitive. What is the main reason to protect it?

easy

A. To allow anyone to connect without restrictions

B. To make Redis run faster

C. To reduce the size of the database

D. To prevent unauthorized users from accessing or changing your data

Solution

1. Step 1: Understand Redis stores data

   Redis holds data that can be important or private, like user info or app settings.

2. Step 2: Identify the risk of no security

   If anyone can connect, they can read or change data, causing harm or data loss.

3. Final Answer:

   To prevent unauthorized users from accessing or changing your data -> Option D

4. Quick Check:

   Protect data = prevent unauthorized access [OK]

Hint: Think: Why lock a door? To keep strangers out [OK]

Common Mistakes:

• Confusing security with performance
• Thinking security reduces data size
• Believing open access is safe

2. Which of the following is the correct way to require a password for Redis connections in the configuration file?

easy

A. auth mypassword

B. password = mypassword

C. requirepass mypassword

D. set password mypassword

Solution

1. Step 1: Recall Redis config syntax for password

   Redis uses the directive requirepass followed by the password in its config file.

2. Step 2: Check each option

   Only requirepass mypassword matches Redis official syntax; others are invalid.

3. Final Answer:

   requirepass mypassword -> Option C

4. Quick Check:

   Redis password config = requirepass [OK]

Hint: Remember Redis uses 'requirepass' for passwords [OK]

Common Mistakes:

• Using 'password =' instead of 'requirepass'
• Trying commands like 'auth' in config file
• Confusing Redis commands with config directives

3. Given this Redis ACL command:
ACL SETUSER alice on >password123 ~* +@all
What does this command do?

medium

A. Deletes user 'alice' and disables all commands

B. Creates user 'alice' with password 'password123' and full access

C. Creates user 'alice' without password and no permissions

D. Creates user 'alice' with password 'password123' but no command access

Solution

1. Step 1: Break down the ACL command parts

   on enables the user, >password123 sets the password, ~* allows access to all keys, +@all grants all commands.

2. Step 2: Understand the combined effect

   User 'alice' is active, requires password 'password123', can access all keys and run all commands.

3. Final Answer:

   Creates user 'alice' with password 'password123' and full access -> Option B

4. Quick Check:

   ACL user with password and full rights = Creates user 'alice' with password 'password123' and full access [OK]

Hint: Look for '>password', '~*' keys, '+@all' commands [OK]

Common Mistakes:

• Thinking 'on' disables user
• Ignoring '~*' means all keys
• Assuming '+@all' denies commands

4. You wrote this Redis config line to require a password:
requirepass password123
But clients still connect without a password. What is the likely problem?

medium

A. The Redis server was not restarted after changing the config

B. The password must be set with 'setpass' instead of 'requirepass'

C. Redis does not support passwords

D. The password must be set in the client, not the server

Solution

1. Step 1: Understand Redis config changes need reload

   Changing requirepass requires restarting Redis or reloading config to take effect.

2. Step 2: Check other options

   The other options are incorrect: 'setpass' is not valid, Redis supports passwords, and password is server-side setting.

3. Final Answer:

   The Redis server was not restarted after changing the config -> Option A

4. Quick Check:

   Config changes need restart = The Redis server was not restarted after changing the config [OK]

Hint: Restart Redis after config changes to apply them [OK]

Common Mistakes:

• Thinking 'setpass' is a valid directive
• Believing Redis has no password support
• Trying to set password only on client side

5. You want to secure your Redis server so only trusted IP addresses can connect. Which approach is best to combine with password protection?

hard

A. Use firewall rules to allow only trusted IPs and enable Redis password

B. Disable password and rely only on IP filtering

C. Allow all IPs but change the Redis port number

D. Use Redis without password and no IP restrictions

Solution

1. Step 1: Understand network security layers

   Firewall rules limit which IPs can reach Redis, reducing attack surface.

2. Step 2: Combine with password protection

   Passwords protect data even if IP filtering fails or is bypassed.

3. Step 3: Evaluate other options

   Disabling password or relying only on port change is weak security.

4. Final Answer:

   Use firewall rules to allow only trusted IPs and enable Redis password -> Option A

5. Quick Check:

   Combine IP filtering + password = best security [OK]

Hint: Combine network and password security for best protection [OK]

Common Mistakes:

• Relying only on port obscurity
• Disabling password for convenience
• Ignoring network-level restrictions