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/tls_client_auth

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.

TLS Client Authentication overview

TLS Client Authentication, also known as two-way TLS authentication, consists of both browser and server sending their respective TLS certificates during the TLS handshake process. The server validates the client certificate and extracts the subject values to determine which user the certificate validates.

TLS Client Authentication appropriate use cases

TLS Client Authentication is appropriate when: access should be limited to a single computer/browser; users are comfortable with or supported in installing TLS certificates; the website requires extra security; or the website is for an intranet. It is generally not appropriate for widely and publicly available websites with average users, such as Facebook.

TLS Client Authentication with enterprise proxy SSL/TLS decryption

If the client is behind an enterprise proxy that performs SSL/TLS decryption, certificate authentication will break unless the site is allowed on the proxy.

Give your agent this brain