SASKiwi is correct that there are plenty of security nuances to consider.
However, consider this: SAS offers a SAS OnDemand for Academics offering, where subscribers use their local install of SAS EG to connect to a SAS environment hosted by SAS, over the Internet. I often offer this as proof that such a thing can be done successfully.
Believe me, our own IT security team made sure that was an Okay Thing To Do.
SAS EG talks to SAS via TCP using ports that you designate in your configuration. At a minimum, the ports you have to allow on a firewall are:
- one for the SAS Metadata Server (by default, 8561 -- but you may change it)
- one for launching a SAS Workspace -the object spawner listener (by default, 8591 - but you may change it).
If you need access to Stored Process servers, additional ports may be necessary. Same for OLAP servers.
You can also use SAS/Secure to encrypt all communications between the SAS EG client and the SAS servers.
Chris