All the data we have on our customers sits in our data-lake, which is hosted by one of our suppliers. Currently the security is such that a limited number of users has (limited) access to the database each with their user-name and password. In addition there is IP whitelisting, so authorized users can only log in to the db if they are coming from one of two IP addresses originating in our office.
Our company no longer uses VPN. As a consequence we only access this DB from the office not when working from home or from one of our suppliers.
The simplest/cheapest way to allow working from outside the office would be to ask the supplier to whitelist the range of IP addresses used by Symantec (= software security product that routes traffic through its proxies), because when we log in to our network from the outside we get one of these addresses. But the upshot would be that every Symantec customer could potentially log into our DB, provided they somehow got hold of a user-name password combination. Someone intent on breaking in would only need to:
- Guess the user names (a combination of first-name and last-name)
- Get Symantec or ask someone our guest WiFi password and sit on our lawn using our wifi
- Somehow get the password
Only step 3 is really hard.
If we got an extra server with a static (public) IP address and only allowed logging into the DB for users coming from this server, we would have an extra layer of security. Am i correct in thinking this would be a good way of securing our data while making working from outside the office possible?
How do i convince management that whitelisting the entire Symantec IP range is dangerous, because it is dangerous, right? Have there been breaches of this kind?
I'd really like to know what the best practices are for such cases and why.
Related question: Why would DB with URL access be less secured than without such access?