new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

OWASP Cheat Sheets · all subjects

authentication/logging

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Log and monitor all authentication failures

Enable logging and monitoring of authentication functions to detect attacks and failures on a real-time basis. Ensure that all failures, password failures, and account lockouts are logged and reviewed.

Email logging and monitoring best practices

Log verification attempts and failures. Monitor password reset activity and detect abnormal patterns such as high-frequency requests. Avoid logging full email addresses; mask or pseudonymize them where logging is necessary using formats like j***@example.com. Never log verification, reset, or authentication tokens or full verification/reset URLs. Treat email addresses and related identifiers in logs as personal or sensitive data and restrict access accordingly.

Login attempt logging with user context

Log all login attempts (successful and failed) with sufficient user context: Log.Information(String.Format("User: {0}, Successfully Logged in", model.Email)) for successful logins and Log.Information(String.Format("User: {0}, Incorrect Password", model.Email)) for failed attempts.

Give your agent this brain