django-secure¶
Warning
This project was merged into Django 1.8. It does not provide any additional checks beyond those included in Django 1.8+, so there is no reason to use it with Django 1.8+. Since Django 1.8 is now the lowest supported Django version, this project is now unsupported and un-maintained.
Helping you remember to do the stupid little things to improve your Django site’s security.
Inspired by Mozilla’s Secure Coding Guidelines, and intended for sites that are entirely or mostly served over SSL (which should include anything with user logins).
Quickstart¶
Dependencies¶
Tested with Django 1.4 through trunk, and Python 2.6, 2.7, 3.2, and 3.3. Quite likely works with older versions of both, though; it’s not very complicated.
Installation¶
Install from PyPI with pip
:
pip install django-secure
or get the in-development version:
pip install django-secure==dev
Usage¶
- Add
"djangosecure"
to yourINSTALLED_APPS
setting. - Add
"djangosecure.middleware.SecurityMiddleware"
to yourMIDDLEWARE_CLASSES
setting (where depends on your other middlewares, but near the beginning of the list is probably a good choice). - Set the
SECURE_SSL_REDIRECT
setting toTrue
if all non-SSL requests should be permanently redirected to SSL. - Set the
SECURE_HSTS_SECONDS
setting to an integer number of seconds andSECURE_HSTS_INCLUDE_SUBDOMAINS
toTrue
, if you want to use HTTP Strict Transport Security. - Set the
SECURE_FRAME_DENY
setting toTrue
, if you want to prevent framing of your pages and protect them from clickjacking. - Set the
SECURE_CONTENT_TYPE_NOSNIFF
setting toTrue
, if you want to prevent the browser from guessing asset content types. - Set the
SECURE_BROWSER_XSS_FILTER
setting toTrue
, if you want to enable the browser’s XSS filtering protections. - Set
SESSION_COOKIE_SECURE
andSESSION_COOKIE_HTTPONLY
toTrue
if you are usingdjango.contrib.sessions
. These settings are not part ofdjango-secure
, but they should be used if running a secure site, and thechecksecure
management command will check their values. - Ensure that you’re using a long, random and unique
SECRET_KEY
. - Run
python manage.py checksecure
to verify that your settings are properly configured for serving a secure SSL site.
Warning
If checksecure
gives you the all-clear, all it means is that you’re now
taking advantage of a small selection of easy security wins. That’s great,
but it doesn’t mean your site or your codebase is secure: only a competent
security audit can tell you that.