Are intermediate certification authority certificates targets for man-in-the-middle attacks?

534695058_6e828578cf_o
As many of you may know Google recently detected a TLS/SSL certificate that was created by the Ministry of France and used as “a commercial device, on a private network, to inspect encrypted traffic with the knowledge of the end users.” In general there is no application on the public internet that would require such a certificate and the use of this type of intermediate certificate does create many security related problems such as “internet traffic routing, domain name resolution and the possibility of an unconstrained trusted intermediate CA certificate.”
That being said, there are still legitimate reasons why an enterprise, organization or government would need such a certificate. For example, in the financial market regulatory rules require that brokers have all of their communications recorded in order to oversee and regulate their activity. In this case the TLS/SSL certificate is providing a level of encryption to users within the portal but at the same time making such information available for oversight.  However instead of using a publically trusted Root CA and misusing the certificate, the enterprise, organization or government should use a privately trusted CA that is trusted only within the defined scope of that portal.
 You may be wondering that if it is easy enough to acquire a TLS/SSL certificate could hackers easily attain an unconstrained trusted intermediate CA certificate? The answer is no because of the standards and rules put into place by the CA/B baseline requirements. The CA/B requires that a TLS/SSL certificate can only be issued after there is confirmation from the domain owner.
Depending on the type of SSL certificate, confirmation is made by either responding to an email sent to the registered email address of the domain (DV certificates) or (for the more advanced validated certificates OV SSL Certificates & EV SSL Certificates) by not only contacting the domain owner by email/phone but by also requiring them to submit formal documents to prove the existence of their organization.
In closing SSL certificates are a cornerstone of internet and are sometimes required but should always be used for websites that transfer or have the potential to transfer personal data including but not limited to: User-names, passwords, SSN, Debit/Credit Cards, Pin #, Forms, Online Conversations, VOIP, Gateways, Portals, VPNs Etc. SSL does have vulnerabilities and most stem from the element of human error, which is why network administrators should ALWAYS properly store their private keys in a secure environment to avoid the potential of a data breach.
Source: SSLGURU.com
foto by openDemocracy via Flickr.com
Posted in secmash feed