Difference between revisions of "Client Certificate"
From MgmtWiki
(→Context) |
(→Context) |
||
| Line 4: | Line 4: | ||
==Context== | ==Context== | ||
[[Mutual Authentication]] or mTLS is used in a version of TLS where both sides of the connection have certificates that are evaluated during the TLS handshake. | [[Mutual Authentication]] or mTLS is used in a version of TLS where both sides of the connection have certificates that are evaluated during the TLS handshake. | ||
| + | |||
| + | ==Problem== | ||
| + | |||
| + | Password-based security in many organizations is a problem. Sure, part of this stems from employees practicing poor password hygiene (such as creating weak passwords or sharing their credentials with colleagues). However, a large part of it comes from employers practicing poor access management. [https://www.keeper.io/hubfs/PDF/Password%20Malpractice%20Campaign/Workplace%20Password%20Malpractice%20Report%20-%202021.pdf Recent data from Keeper Security and Pollfish] shows that 32% of their 1,000 survey respondents say they’ve accessed accounts belonging to their former employers. | ||
==References== | ==References== | ||
Revision as of 17:42, 8 February 2023
Full Title or Meme
A Certificate that is created to identify the client in a client-server environment
Context
Mutual Authentication or mTLS is used in a version of TLS where both sides of the connection have certificates that are evaluated during the TLS handshake.
Problem
Password-based security in many organizations is a problem. Sure, part of this stems from employees practicing poor password hygiene (such as creating weak passwords or sharing their credentials with colleagues). However, a large part of it comes from employers practicing poor access management. Recent data from Keeper Security and Pollfish shows that 32% of their 1,000 survey respondents say they’ve accessed accounts belonging to their former employers.
