Hi,
I don’t get why you need a squid box for that purpose. If you have the private key you could end the traffic on like nginx and just forward it to saas, while doing that you could log the traffic as you want.
Best
Logan
On Fri, Jul 13, 2018 at 5:34 PM Krystyna Niesiołowska <krystyna.niesiolowska@xxxxxxxxxx> wrote:
_______________________________________________Hi All,
In my company, the HR uses an outsourced SaaS (on a unique public IP) configured with a commercial SSL certificate (i.e. I have both the private and the public key) accessed by our employees via a subdomain of our company domain (saas.company.com) . Unfortunately, we cannot control the data being transferred by the HR people and because of the GDPR the board wants to be able to get alerts if anyone tries to transfer personal data to the cloud + a general channel to check against any data exfiltration.My idea is to set to route all traffic going to sass.company.com via a box running Squid with SSL interception. I would like to install the same cert as the one used with the SaaS. This is to avoid the need of installing any additional certs on use's' machines. Unfortunately, I cannot find an option to set Squid with a single commercial cert instead of a CA (commonly used to intercept generate individual certs for all of the SSL traffic).Does anybody have any suggestions on the viable setup?
Best wishes,
Kristin
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
