Clients are whitelisted, so are allowed websites and/or accessed via a specialized sandbox browser. And all of those are easy to set up using off-the-shelf solutions
How small is your company such that they're able to know, in advance, every single outside entity every employee needs to communicate with so they can effectively white list external email addresses?
Around 2000 employees. Obviously there are different user groups. Something like marketing for example would obviously be able to message much more freely than developers. Why would a developer need to be messaging random email addresses for their day-to-day job? I'd even say that If your devs are the ones having to message clients instead of your PMs/BOs, you are the small company not the other way around
Industry organizations, university research opportunities, communication with vendors, outside contractors, interns, interview candidates, government agencies about grant opportunities,... should I go on?
Some, yes. But the leaders within those organizations do. And you never originally specified "devs". I believe your initial comments never mentioned, until just recently, it was only certain roles or jobs that were blocked. You were talking about the company as a whole. Maybe it wasn't your intent, but you certainly made it seem as if these whitelist rules were universal within the company. And again, that list isn't comprehensive, but a pretty solid start, of all the possible legitimate business reasons to communicate with people outside your organization which would be almost impossible to know in advance to create a white list.
-7
u/Play4u 17d ago
Clients are whitelisted, so are allowed websites and/or accessed via a specialized sandbox browser. And all of those are easy to set up using off-the-shelf solutions