<div>
<div class="content wysiwyg-content">
Here's how I think it works. Tell me if I'm wrong.<br />
<br />

<div class="bullet">
I go to amazon.com for the first time and buy some swim goggles. Amazon's site directs my browser to the certificate authority (CA), my browser pulls the Amazon certificate, and stores it in Windows Cert Manger.
</div>
<div class="bullet">
I navigate to a client's site for the first time via Citrix. At some point during the process I again retrieve a certificate from a CA, and store it in the Windows Cert Manager.
</div>
<div class="bullet">
Any time my Windows machine is involved in a SSL/TLS handshake, I'll eventually pull a certificate and store it in the Windows Cert Manager. 
</div>
<br />
Is this accurate? All my digital certificates, whether they're obtained through Chrome, Firefox, IE, or another third-party tool, eventually end up in the common repository, Windows Cert Manager? <br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2015/11_w47/1017541/2015-11-15_17h26_10.png" target="_blank" title="Cert Manager (22 KB)"><img alt="Cert Manager" class="file-block lazyload" style="max-width: 640px;" data-src="https://filedb.experts-exchange.com/incoming/2015/11_w47/1017541/2015-11-15_17h26_10.png" /></a>
</div>
</div>


2015-11-15_17h26_10.png

Here's how I think it works. Tell me if I'm wrong.

I go to amazon.com for the first time and buy some swim goggles. Amazon's site directs my browser to the certificate authority (CA), my browser pulls the Amazon certificate, and stores it in Windows Cert Manger.
I navigate to a client's site for the first time via Citrix. At some point during the process I again retrieve a certificate from a CA, and store it in the Windows Cert Manager.
Any time my Windows machine is involved in a SSL/TLS handshake, I'll eventually pull a certificate and store it in the Windows Cert Manager. 

Is this accurate? All my digital certificates, whether they're obtained through Chrome, Firefox, IE, or another third-party tool, eventually end up in the common repository, Windows Cert Manager? 



Windows - Common repository for digital certificates?

HTTPS is a protocol for secure communication over a computer network which is widely used on the Internet. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security (TLS) or its predecessor, Secure Sockets Layer (SSL). The main motivation for HTTPS is authentication of the visited website and to protect the privacy and integrity of the exchanged data. HTTPS is widely used for protecting page authenticity on all types of websites, securing accounts and keeping user communications, identity and web browsing private.

SSL / HTTPS

Encryption is the process of encoding messages or information in such a way that only authorized parties can read it. In an encryption scheme, the intended communication information or message, referred to as plaintext, is encrypted using an encryption algorithm, generating ciphertext that can only be read if decrypted. For technical reasons, an encryption scheme usually uses a pseudo-random encryption key generated by an algorithm. An authorized recipient can easily decrypt the message with the key provided by the originator to recipients, but not to unauthorized interceptors.

Encryption

Security is the protection of information systems from theft or damage to the hardware, the software, and the information on them, as well as from disruption or misdirection of the services they provide. The main goal of security is protecting assets, and an asset is anything of value and worthy of protection.  Information Security is a discipline of protecting information assets from threats through safeguards to achieve the objectives of confidentiality, integrity, and availability or CIA for short. On the other hand, disclosure, alteration, and disruption (DAD) compromise the security objectives.