| Line 15: |
Line 15: |
| | | | |
| | == Trusted Root CA Folder == | | == Trusted Root CA Folder == |
| | + | === Early CA infrastructure === |
| | There were several early problems that led to the need for having multiple CAs in the client-side trusted root folder. | | There were several early problems that led to the need for having multiple CAs in the client-side trusted root folder. |
| | :* One of the main issues was that early CA infrastructure was centralized, and relied on a small number of large CAs to issue and manage digital certificates. This created a ''single point of failure'', as the compromise or failure of one of these large CAs could lead to widespread trust issues and security breaches. | | :* One of the main issues was that early CA infrastructure was centralized, and relied on a small number of large CAs to issue and manage digital certificates. This created a ''single point of failure'', as the compromise or failure of one of these large CAs could lead to widespread trust issues and security breaches. |
| Line 21: |
Line 22: |
| | Overall, early problems with centralized, non-transparent, and unscalable CA infrastructure led to the need for having multiple CAs in the trusted root folder to provide more flexibility, redundancy, and security in digital certificate infrastructure. | | Overall, early problems with centralized, non-transparent, and unscalable CA infrastructure led to the need for having multiple CAs in the trusted root folder to provide more flexibility, redundancy, and security in digital certificate infrastructure. |
| | | | |
| − | | + | === Benefits of Multiple Trusted Roots === |
| | There are several risks associated with having only one certificate in the trusted root folder of a PC: | | There are several risks associated with having only one certificate in the trusted root folder of a PC: |
| | # Single point of failure: Having only one CA in the trusted root folder can create a single point of failure. If that CA is compromised or becomes unavailable, the PC may be unable to establish secure connections with any servers or services that rely on that CA. | | # Single point of failure: Having only one CA in the trusted root folder can create a single point of failure. If that CA is compromised or becomes unavailable, the PC may be unable to establish secure connections with any servers or services that rely on that CA. |