SECRET_KEY and security settings in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the SECRET_KEY in a Django project?

The SECRET_KEY is a secret value used by Django to provide cryptographic signing. It helps protect data like session cookies and password reset tokens from being tampered with.

beginner

Why should the SECRET_KEY never be shared or exposed publicly?

If the SECRET_KEY is exposed, attackers can forge session cookies or tokens, leading to security breaches like user impersonation or data leaks.

intermediate

Name two important security settings in Django besides SECRET_KEY.

1. DEBUG: Should be set to False in production to avoid showing sensitive error details.
2. ALLOWED_HOSTS: Lists the host/domain names your Django site can serve to prevent HTTP Host header attacks.

beginner

What is the risk of setting DEBUG = True in a production environment?

With DEBUG = True, detailed error pages with sensitive information are shown to users, which can help attackers find vulnerabilities.

intermediate

How can you keep your SECRET_KEY safe when sharing your Django project code?

You can store the SECRET_KEY outside your code, for example in environment variables or separate config files not included in version control, so it is not shared publicly.

What is the main use of Django's SECRET_KEY?

A To sign cookies and tokens securely

B To connect to the database

C To set the website title

D To configure static files

The SECRET_KEY is used to cryptographically sign cookies and tokens to prevent tampering.

Which setting should be False in production to avoid exposing sensitive info?

A ALLOWED_HOSTS

B DEBUG

C INSTALLED_APPS

D STATIC_URL

DEBUG should be False in production to prevent detailed error pages from showing.

What does the ALLOWED_HOSTS setting do?

A Stores the secret key

B Enables debug mode

C Lists allowed domain names for the site

D Defines database connections

ALLOWED_HOSTS restricts which host/domain names the Django app can serve.

What is a good practice to keep your SECRET_KEY safe?

A Use a simple string like 'password'

B Hardcode it in your public code

C Share it on GitHub

D Store it in environment variables

Storing the SECRET_KEY in environment variables keeps it out of public code and safer.

What could happen if your SECRET_KEY is leaked?

A Attackers can forge session cookies

B Your database will be deleted

C Your website will load slower

D Your static files won't load

Leaking the SECRET_KEY allows attackers to create fake session cookies and impersonate users.

Explain why the SECRET_KEY is critical for Django security and how to protect it.

Think about what happens if someone can fake your cookies or tokens.

Describe the role of DEBUG and ALLOWED_HOSTS settings in securing a Django app.

Consider what happens if error details are shown or if any host can access your app.

Practice

1. What is the main purpose of the SECRET_KEY in a Django project?

easy

A. To define the database connection string

B. To secure sessions and cryptographic signing

C. To list allowed hosts for the app

D. To enable debug mode during development

Solution

1. Step 1: Understand the role of SECRET_KEY

   The SECRET_KEY is used by Django to provide cryptographic signing, which secures sessions and other data.

2. Step 2: Differentiate from other settings

   Database connection strings, allowed hosts, and debug mode serve different purposes unrelated to cryptographic security.

3. Final Answer:

   To secure sessions and cryptographic signing -> Option B

4. Quick Check:

   SECRET_KEY secures sessions = B [OK]

Hint: SECRET_KEY protects data and sessions, not database or hosts [OK]

Common Mistakes:

• Confusing SECRET_KEY with database settings
• Thinking SECRET_KEY controls allowed hosts
• Assuming SECRET_KEY enables debug mode

2. Which of the following is the correct way to set a SECRET_KEY in Django's settings.py?

easy

A. SECRET_KEY = 'a-very-long-random-string'

B. SECRET_KEY = None

C. SECRET_KEY = True

D. SECRET_KEY = 1234567890

Solution

1. Step 1: Check the type of SECRET_KEY

   The SECRET_KEY must be a long, random string enclosed in quotes (a string).

2. Step 2: Evaluate each option

   SECRET_KEY = 1234567890 is a number, not a string. SECRET_KEY = True is a boolean. SECRET_KEY = None is None. Only SECRET_KEY = 'a-very-long-random-string' is a proper string.

3. Final Answer:

   SECRET_KEY = 'a-very-long-random-string' -> Option A

4. Quick Check:

   SECRET_KEY must be a string = D [OK]

Hint: SECRET_KEY must be a string, not number or boolean [OK]

Common Mistakes:

• Setting SECRET_KEY as a number without quotes
• Using boolean or null instead of a string
• Using a short or guessable string

3. Given this settings.py snippet:

DEBUG = False
ALLOWED_HOSTS = ['example.com']
SECRET_KEY = 'mysecretkey'

What happens if a request comes from malicious.com?

medium

A. Django will crash with a server error

B. Django will accept the request and serve the page

C. Django will reject the request with a 400 Bad Request error

D. Django will redirect to example.com automatically

Solution

1. Step 1: Understand ALLOWED_HOSTS role

   When DEBUG is false, Django only accepts requests from hosts listed in ALLOWED_HOSTS.

2. Step 2: Check the request host

   The request is from malicious.com, which is not in ALLOWED_HOSTS, so Django rejects it with a 400 error.

3. Final Answer:

   Django will reject the request with a 400 Bad Request error -> Option C

4. Quick Check:

   Request host not allowed = 400 error = C [OK]

Hint: Requests from hosts not in ALLOWED_HOSTS get 400 error [OK]

Common Mistakes:

• Thinking Django accepts all hosts when DEBUG is false
• Assuming Django crashes on disallowed hosts
• Believing Django redirects disallowed hosts

4. You set DEBUG = false but forgot to add your domain to ALLOWED_HOSTS. What error will you most likely see when accessing your site?

medium

A. No error, site loads normally

B. TemplateDoesNotExist error

C. Database connection error

D. DisallowedHost error

Solution

1. Step 1: Understand ALLOWED_HOSTS enforcement

   When DEBUG is false, Django checks if the request host is in ALLOWED_HOSTS. If not, it raises a DisallowedHost error.

2. Step 2: Identify the error from missing domain

   Since the domain is missing from ALLOWED_HOSTS, Django raises DisallowedHost.

3. Final Answer:

   DisallowedHost error -> Option D

4. Quick Check:

   Missing domain in ALLOWED_HOSTS = DisallowedHost error = A [OK]

Hint: Missing domain in ALLOWED_HOSTS causes DisallowedHost error [OK]

Common Mistakes:

• Confusing DisallowedHost with template or database errors
• Assuming site loads without ALLOWED_HOSTS set
• Thinking DEBUG controls DisallowedHost error

5. You want to improve your Django app security. Which combination of settings is best practice for production?

hard

A. DEBUG = False, SECRET_KEY = 'a-long-random-string', ALLOWED_HOSTS = ['yourdomain.com']

B. DEBUG = True, SECRET_KEY = 'shortkey', ALLOWED_HOSTS = ['*']

C. DEBUG = False, SECRET_KEY = '', ALLOWED_HOSTS = []

D. DEBUG = True, SECRET_KEY = 'a-long-random-string', ALLOWED_HOSTS = []

Solution

1. Step 1: Understand production security needs

   In production, DEBUG must be False to avoid exposing sensitive info. SECRET_KEY must be long and random. ALLOWED_HOSTS should list your domain to restrict access.

2. Step 2: Evaluate each option

   DEBUG = True, SECRET_KEY = 'shortkey', ALLOWED_HOSTS = ['*'] has DEBUG = True and weak SECRET_KEY, unsafe. DEBUG = False, SECRET_KEY = '', ALLOWED_HOSTS = [] has empty SECRET_KEY and ALLOWED_HOSTS, insecure. DEBUG = True, SECRET_KEY = 'a-long-random-string', ALLOWED_HOSTS = [] has DEBUG = True and empty ALLOWED_HOSTS, unsafe. Only DEBUG = False, SECRET_KEY = 'a-long-random-string', ALLOWED_HOSTS = ['yourdomain.com'] meets all best practices.

3. Final Answer:

   DEBUG = False, SECRET_KEY = 'a-long-random-string', ALLOWED_HOSTS = ['yourdomain.com'] -> Option A

4. Quick Check:

   Production needs DEBUG false, strong SECRET_KEY, correct ALLOWED_HOSTS = A [OK]

Hint: Production: DEBUG false, strong SECRET_KEY, restrict ALLOWED_HOSTS [OK]

Common Mistakes:

• Leaving DEBUG true in production
• Using short or empty SECRET_KEY
• Allowing all hosts with ALLOWED_HOSTS = ['*']