It's great that Google wants to move more sites to https, and I'm in support of this, but it also creates challenges for security vendors such as myself. Curre

It's great that Google wants to move more sites to https, and I'm in support of this, but it also creates challenges for security vendors such as myself. Currently DNSFilter and others Man in the Middle traffic destined for sites our customers have decided to block. This works great for http, but not https, as certificate warnings are presented. The standard work around is arguably less secure: adding a third-party CA to all end-points. This can still present problems with HSTS and certificate pinning. I'd like to work with Google to create a standard where vendors can either be on a whitelist or have new recognized SSL cert fields, not to MITM traffic, but just to present users with a friendlier message explaining whats happening, and providing a separate https:// https:// url to visit for information from the vendor about the block. Implementing such a standard in browsers would further increase user security, and provide a viable method for filtering on guest networks where there is no end-point access.