[Django] #26629: Login failures should be logged

[Django]

#26629: Login failures should be logged
-------------------------------------+-------------------------------------
Reporter: jacobian | Owner: nobody
Type: New | Status: new
feature |
Component: | Version: 1.9
contrib.auth | Keywords: login security
Severity: Normal | logigng
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Login failures [*] should emit logging messages. There are a couple of
good reasons for this:

- Many compliance regimes (all those deriving from NIST-800-53, so FISMA,
PCI, HIPAA, etc) require logging of failed login attempts.
- It'll makes integration with a SIEM easier out of the box.

[*] we may want to log successes, too, or have a configuration option or
somesuch. I tend to think successes are noise, but reasonable people
disagree on that point.

[One of a series of bugs from a discussion I had with @mallyvai about
improving the security of Django's admin - see
https://gist.github.com/mallyvai/bcb0bb827d6d53212879dff23cf15d03 for the
full list.]

--
Ticket URL: <https://code.djangoproject.com/ticket/26629>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#26629: Login failures should be logged
-------------------------------------+-------------------------------------
Reporter: jacobian | Owner: nobody

Type: New feature | Status: closed
Component: contrib.auth | Version: 1.9
Severity: Normal | Resolution: duplicate
Keywords: login security | Triage Stage:
logigng | Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by timgraham):

* status: new => closed
* resolution: => duplicate

Comment:

Duplicate of #20495. Feel free to continue the discussion there and reopen
if you feel my closing was in error.

--
Ticket URL: <https://code.djangoproject.com/ticket/26629#comment:1>

[Django]

#26629: Login failures should be logged
-------------------------------------+-------------------------------------
Reporter: jacobian | Owner: nobody

Type: New feature | Status: new

Component: contrib.auth | Version: 1.9
Severity: Normal | Resolution:

Keywords: login security | Triage Stage:
logigng | Unreviewed

Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by mallyvai):

* status: closed => new
* resolution: duplicate =>

Comment:

Unsure about correct process, but I reopened the original ticket. Should I
set that to New instead?

--
Ticket URL: <https://code.djangoproject.com/ticket/26629#comment:2>

[Django]

#26629: Login failures should be logged
-------------------------------------+-------------------------------------
Reporter: jacobian | Owner: nobody

Type: New feature | Status: closed
Component: contrib.auth | Version: 1.9
Severity: Normal | Resolution: duplicate

Keywords: login security | Triage Stage:
logigng | Unreviewed

Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by timgraham):

* status: new => closed
* resolution: => duplicate

Comment:

I replied on the other ticket.

--
Ticket URL: <https://code.djangoproject.com/ticket/26629#comment:3>