3 ms·
It seems like when this talks about "enabl[ing] teams to access private company resources", it means "access 3rd party cloud services that support IP whitelisti
by akerl_ 8y ago
It seems like when this talks about "enabl[ing] teams to access private company resources", it means "access 3rd party cloud services that support IP whitelisting"? For example, if I set up another service on the internet to only allow connections from the dedicated VPN server IP. But it wouldn't let a remote employee access a service running in the company's office LAN. Am I misreading that?
Additionally, what protections are in place to ensure Portal Cloud staff aren't monitoring the traffic or accessing a customer's "private company resources"?
- jeff393 8y agoYes, that's right. We're referring to IP whitelisting there. We're also adding (very shortly) site-to-site VPN connections, so users can link their AWS/GCP VPC or even a traditional office/datacenter LAN. Even with a VPN, any sensitive services should have their own auth and logging enabled. Requiring a VPN doesn't remove the need for other forms of security, but it does add a very effective layer of security. We also have a strong business incentive not to violate the trust of our customers. We're hoping to prove that we can be trusted over time, and to use technology to reduce the need for trust.