Difference between revisions of "Enterprise Certificate Authority"
From MgmtWiki
(→Context) |
(→Context) |
||
| Line 3: | Line 3: | ||
==Context== | ==Context== | ||
| − | Typically, an [[Enterprise Certificate Authority]] operates via [[Client Certificate]]s that are issued to a digital [[Identifier]] that is issued to an [[Entity]] that has some means to control access to a protected [[Private Key]] that is used for Authentication. | + | * Typically, an [[Enterprise Certificate Authority]] operates via [[Client Certificate]]s that are issued to a digital [[Identifier]] that is issued to an [[Entity]] that has some means to control access to a protected [[Private Key]] that is used for Authentication. |
| + | * The most common form of [[Authentication]] is via [[Client Certificate]]s that bind the [[Entity]] [[Identifier]] with a [[Client Certificate]] that is used in a TCP connection using [[Mutual TLS]] to carry the proof of possession, not only of the key of the server, but also of the key of the Client. | ||
==References== | ==References== | ||
[[Category: Trust]] | [[Category: Trust]] | ||
Revision as of 15:24, 8 February 2023
Full Title or Meme
Any Certificate Authority that is designed to apply to people, natural or otherwise, that are known to the Enterprise.
Context
- Typically, an Enterprise Certificate Authority operates via Client Certificates that are issued to a digital Identifier that is issued to an Entity that has some means to control access to a protected Private Key that is used for Authentication.
- The most common form of Authentication is via Client Certificates that bind the Entity Identifier with a Client Certificate that is used in a TCP connection using Mutual TLS to carry the proof of possession, not only of the key of the server, but also of the key of the Client.
